Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[rhcos-4.16] mantle/platform/aws: handle missing details fields #3964

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #3959

/assign marmijo

Possibly something changed on the AWS side, but we're seeing what looks
like `SnapshotTaskDetail` structs coming back with some of the fields
empty. Gracefully handle this case.
Copy link

openshift-ci bot commented Nov 21, 2024

Hi @openshift-cherrypick-robot. Thanks for your PR.

I'm waiting for a coreos member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@marmijo
Copy link
Member

marmijo commented Nov 21, 2024

/ok-to-test

It doesn't work properly against these rhcos- branches anyway. Let's
just limit the testing to building the container and running check
and unittest tests.
@dustymabe
Copy link
Member

CI is failing but it shouldn't be running anything other than build and unit tests because of the second commit here, which i suspect is not getting picked up because this PR was submitted by a bot. I'll force merge this.

@dustymabe dustymabe merged commit ca699e7 into coreos:rhcos-4.16 Nov 26, 2024
4 of 5 checks passed
@marmijo
Copy link
Member

marmijo commented Nov 26, 2024

Ah, sorry. I thought got merged along with #3965.
#3965 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants