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
*: switch to v3.2.0 Ignition configs instead of v3.1.0 #2248
Conversation
62e4225
to
2ab63df
Compare
/retest |
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.
Mainly concerned about the MCS parts.
If every spec bump involves this level of churn that's a bit unfortunate but, solving that seems hard without reworking the API.
@@ -283,8 +283,8 @@ func detectSpecVersionFromAcceptHeader(acceptHeader string) (*semver.Version, er | |||
|
|||
for _, header := range headers { | |||
if header.MIMESubtype == "vnd.coreos.ignition+json" && header.SemVer != nil { | |||
if !header.SemVer.LessThan(*v3_1) && header.SemVer.LessThan(*semver.New("4.0.0")) { | |||
return v3_1, nil | |||
if !header.SemVer.LessThan(*v3_2) && header.SemVer.LessThan(*semver.New("4.0.0")) { |
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.
In both the API and the tests we need to also continue to handle 3.1 right?
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.
Ah yep, that was an oversight. I've got coreos/ign-converter#19 up to add v32tov31
down-translation. After that merges I'll bump the ign-converter
vendor again & update to check for v3_1
semver, down-translate in server/api
& add tests for 3.1.0
in server/api_test
.
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.
Ok, I think I've addressed this.
I've added back support for v3_1
headers, added 3.2.0
-> 3.1.0
translation, and re-added unit tests in pkg/server/api_test
.
Ignition was already bumped to version 2.7.0 but nothing was actually referencing the v3_2 configs to pull them in.
/approve |
Hmm not sure what went wrong with that e2e-aws run; installer ran fine but then this failed which seems like something in CI glue:
|
/retest |
1 similar comment
/retest |
throwing a hold while i review /hold |
Also okd-e2e is currently red and it looks like rhel7 is flaky, so you don't have to retest @arithx ill confirm we can skip the rhel7 one and deal with that later. |
@kikisdeliveryservice in light of your hold, have you had a chance to review? The update to spec is needed for finalizing complex disks (confirmed by @bgilbert via Slack) I looked over the code, and nothing stands out. |
/retest |
I believe @yuqi-zhang is looking it over too, wanted to give MCO team the opp to review this as it's non-trivial. |
@yuqi-zhang PTAL |
Did some testing for this, upgraded fine, and all generated configs are on 3.2, applied 2.2 config looks fine, scaling node looks fine /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arithx, cgwalters, darkmuggle, yuqi-zhang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Will let @kikisdeliveryservice cancel the hold when comfortable |
will lift hold once jerry's q above is addressed. |
Q as a consumer of ignition : are you planning on chaining parsers? bc as you can see moving forward with future versions this is going to cause a mess... |
/hold cancel |
@kikisdeliveryservice We chained parsers in spec 2.x but removed that functionality for spec 3. I agree that we should think about adding it back. |
/retest |
1 similar comment
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
this is fully approved and made the deadline, e2e is still hitting some well documented ci resource issues:
which are still being worked on by admins... |
/retest Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
- What I did
Switch the underlying Ignition spec 3 configs to use the
3.2.0
types (and update the underlying translation for spec 3 configs to uptranslate into 3.2.0).- How to verify it
Spec 3 configs should remain working. Additionally new config fields that are only present in the Ignition 3.2.0 spec (see here for a list of new features to the 3.2.0 spec) can be specified.
- Description for the changelog
vendor commit: Bump
ign-converter
to pick upv32tov2x
translation packages & pull in spec 3.2.0 Ignition packagesother commit: update the
ign3types
import to use theconfig/v3_2/types
package instead ofconfig/v3_1/types