-
Notifications
You must be signed in to change notification settings - Fork 462
Make OKD/SCOS Dockerfile regexes match again after rhel-coreos image name change
#3597
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
Make OKD/SCOS Dockerfile regexes match again after rhel-coreos image name change
#3597
Conversation
Last minute change in openshift#3496 resulted in the number being removed from the end of the `rhel-coros-8/9` image, it is now just simply in there as `rhel-coreos`, and as a result the regex that was scraping out the extensions images (because fcos/scos dont' ship them) no longer works. This adjusts the sed command in the Dockerfile so it matches again now that the number is missing, and the extensions are properly removed.
|
Skipping CI for Draft Pull Request. |
|
/test okd-scos-images |
|
Yep, looks like that fixed it. |
yuqi-zhang
left a comment
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
|
Shouldn't block this, but the OKD-SCOS upgrade job sees it too: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/3597/pull-ci-openshift-machine-config-operator-master-okd-scos-e2e-gcp-ovn-upgrade/1633652495685259264 Is that a different manifestation? Or is it because the previous one doesn't have it when it tries to install and old one for upgrade? |
Yep, I think that's it. Looking at what it was doing, the MCO it's using from the And that image does still contain the extensions references: But the one it builds from this PR (that it's going to try to upgrade to) is successful. I mean that's maybe a fair assumption that the current image available is sane (as long as....er...nobody bypassed CI to get it in there 😄 ) |
|
Thanks for so quickly fixing this up! Should this also be included in the PR in which we make the same changes to the release-4.13 branch? |
Yes, it should. If we don't, we'll have the same issues there. |
|
well this definitely didn't break that test |
|
/test e2e-aws-ovn-upgrade |
|
/test e2e-aws-ovn-upgrade |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, jkyros, yuqi-zhang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
The e2e-aws-ovn-upgrade job failed on apiserver disruption. But a release image got built, so I'm inclined to add an |
|
Agree, this isn't affecting the disruption. No objection. |
|
/override ci/prow/e2e-aws-ovn-upgrade |
|
@cgwalters: Overrode contexts on behalf of cgwalters: ci/prow/e2e-aws-ovn-upgrade DetailsIn response to this:
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/test-infra repository. |
|
@jkyros: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
We broke OKD, SCOS and the required okd-scos-images test when #3596 merged because our regexes no longer matched without the number.
This can go in with something else, we just need to fix it 😄