-
Notifications
You must be signed in to change notification settings - Fork 462
WIP: Pick last non-empty OSImageURL #228
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
Conversation
|
Makes sense at first glance. /assign @ashcrow |
|
@cgwalters |
|
Looks sane to me. (Though yeah, this does look like "first non-empty"). |
|
/test e2e-aws |
This is part of the "enabling OSImageURL" merges sanely. Still testing this.
ea0f160 to
39842c6
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cgwalters If they are not already assigned, you can assign the PR to them by writing 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 |
|
Rebased and some fixups landed, but I still haven't really tested this in anger since master installer is broken. |
|
case: /cc @crawford |
|
We're going to need to allow the OS to be overridden, but we should make a stink when it happens. Users will inevitably find this and blow their foot off six months down the road when their cluster updates but the OS doesn't. What is the best way to surface that information? Can we propagate it up via the ClusterOperator CR? |
|
FWIW I am testing this out via |
|
OK here's my reboot loop that's confusing me now: |
|
Must be |
|
@cgwalters I ran into this exact problem I think a few days ago!! The only logs I still have are the following but I was getting errors even tho the currentConfig was definitely NOT the desiredConfig. |
|
Where is root.go which throws the message "Already at target pivot; exiting..." because I can't find it when I search the codebase? |
|
The more I think about it, the more I don't like having We'll do something else in #183 |
Today each MC will contain both an Ignition fragment and an `osImageURL`. Define "merging" as using the first non-empty `osImageURL` so we don't have to be very picky about ordering. This is a smaller version of openshift#228 Prep for: openshift#273
Bug 1804763: add imagestream for oauthproxy image
This is part of the "enabling OSImageURL" merges sanely.
Still testing this.