-
Notifications
You must be signed in to change notification settings - Fork 19
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
fix(edgeclusters.sh): Workaround BZ 2073197 issue with signatures on containers #353
Conversation
/LGTM |
maybe we should instead change the quay.io/ztpfw/pipeline:latest image.
|
Could you please add more info to the PR description? It would be useful to know how that BZ affects us, why it affects us, and what the contents of the override in this PR are. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
b3e71cb
to
84f2b0d
Compare
Same failure in 'deploy-metallb' as 'main' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's curious that the CI job is being re-triggered.
regarding the issue with metallb and mirror, in the afternoons I don't know why we're getting this kinds of "retries" with some images...but this is something temporal The PR is LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
🎉 This PR is included in version 1.9.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
Override for BZ 2073197 to override permissions https://bugzilla.redhat.com/show_bug.cgi?id=2073197#c19
Related: openshift/machine-config-operator#1349
Apparently, by mistake, a change in RHCOS image does try to verify signatures for the images, which are not currently mirrored or even provided, and this causes an issue.
There's an upstream issue listed to get this solved, but as a workaround we're disabling verification in Edge clusters via an ignition file and might in addition require a change in the installer image being used until RHCOS has the changes reverted and the related tooling is updated to mirror signatures, etc.