Skip to content

Ignition spec 3 update for cluster-launch-installer-upi-e2e#10534

Closed
travier wants to merge 1 commit intoopenshift:masterfrom
travier:ign3
Closed

Ignition spec 3 update for cluster-launch-installer-upi-e2e#10534
travier wants to merge 1 commit intoopenshift:masterfrom
travier:ign3

Conversation

@travier
Copy link
Copy Markdown
Member

@travier travier commented Jul 29, 2020

See openshift/installer#3871.

This is required starting with RHCOS 4.6.

@runcom
Copy link
Copy Markdown
Member

runcom commented Jul 29, 2020

@abhinavdahiya @danehans ptal

@travier
Copy link
Copy Markdown
Member Author

travier commented Jul 29, 2020

Please be aware that I have just performed the Ignition config conversion and I do not know the full implication this has on the CI (if this may break older non spec 3 jobs, etc.).

@travier
Copy link
Copy Markdown
Member Author

travier commented Jul 29, 2020

This may also probably require a split into multiple PRs.

@LorbusChris
Copy link
Copy Markdown
Contributor

@travier any reason not go with spec 3.1.0? Installer will be using that everywhere.

@cgwalters
Copy link
Copy Markdown
Member

Right, we can't just mass convert because many of these configs are part of templates/steps which get reused for older branches too.

@cgwalters
Copy link
Copy Markdown
Member

Perhaps the simplest thing is to check whether the target release is ≥ 4.6 and if so, download and use ign-convert to upconvert from spec2x.

@travier
Copy link
Copy Markdown
Member Author

travier commented Jul 29, 2020

@travier any reason not go with spec 3.1.0? Installer will be using that everywhere.

No reason, will update.

Comment thread clusters/build-clusters/01_cluster/machine_config/99-debug-ssh.yaml Outdated
@travier
Copy link
Copy Markdown
Member Author

travier commented Jul 29, 2020

Perhaps the simplest thing is to check whether the target release is ≥ 4.6 and if so, download and use ign-convert to upconvert from spec2x.

I would say do the reverse? Down-convert from spec 3 when needed? Will try to look into that.

@travier
Copy link
Copy Markdown
Member Author

travier commented Jul 29, 2020

This still requires a check for cluster version. Marking as draft.

@travier travier changed the title Ignition spec 3.0.0 related updates WIP: Ignition spec 3.0.0 related updates Jul 29, 2020
@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 29, 2020
@LorbusChris
Copy link
Copy Markdown
Contributor

I think all the empty fields can be dropped entirely from the json with spec 3

@LorbusChris
Copy link
Copy Markdown
Contributor

Looks like this has been fixed?

@travier travier force-pushed the ign3 branch 2 times, most recently from 2d6bcfd to dbf8f32 Compare September 24, 2020 10:14
@travier
Copy link
Copy Markdown
Member Author

travier commented Sep 24, 2020

The aws/proxy case has been ported to Fedora CoreOS thus to spec 3. The cluster-launch-installer-upi-e2e hasn't been updated yet. Updated with only this one.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@travier: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/openshift/installer/master/e2e-aws-proxy 4e601e006b8461164c48000f370133775642bb14 link /test pj-rehearse
ci/prow/ci-testgrid-allow-list 4e601e006b8461164c48000f370133775642bb14 link /test ci-testgrid-allow-list
ci/rehearse/openshift/cluster-image-registry-operator/master/e2e-vsphere dbf8f32421eba061f78041593744e4b2a23ac0f8 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-upi dbf8f32421eba061f78041593744e4b2a23ac0f8 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-azure-upi dbf8f32421eba061f78041593744e4b2a23ac0f8 link /test pj-rehearse
ci/rehearse/openshift/installer/release-4.3/e2e-gcp-upi dbf8f32421eba061f78041593744e4b2a23ac0f8 link /test pj-rehearse
ci/prow/pj-rehearse dbf8f32421eba061f78041593744e4b2a23ac0f8 link /test pj-rehearse

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-merge-robot
Copy link
Copy Markdown
Contributor

@travier: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/secret-generator-config-valid dbf8f32421eba061f78041593744e4b2a23ac0f8 link /test secret-generator-config-valid

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-bot
Copy link
Copy Markdown
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 9, 2021
@openshift-bot
Copy link
Copy Markdown
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 11, 2021
@travier
Copy link
Copy Markdown
Member Author

travier commented Mar 11, 2021

/remove-lifecycle rotten

@openshift-ci-robot openshift-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Mar 11, 2021
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: travier
To complete the pull request process, please assign mandre after the PR has been reviewed.
You can assign the PR to them by writing /assign @mandre in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@travier travier changed the title WIP: Ignition spec 3.0.0 related updates Ignition spec 3.0.0 update for cluster-launch-installer-upi-e2e Mar 11, 2021
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 11, 2021
@travier travier changed the title Ignition spec 3.0.0 update for cluster-launch-installer-upi-e2e Ignition spec 3 update for cluster-launch-installer-upi-e2e Mar 11, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 8, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: travier
To complete the pull request process, please assign mandre after the PR has been reviewed.
You can assign the PR to them by writing /assign @mandre in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

{
"ignition": {
"config": {},
"config": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I think all the empty fields can be dropped here as ignition uses a parser implementation that allows for that

Other than that, I think this change should go in

@jhixson74
Copy link
Copy Markdown
Member

/uncc

@openshift-ci openshift-ci Bot removed the request for review from jhixson74 July 8, 2021 01:23
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 9, 2021

@travier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/openshift/installer/master/e2e-aws-upi 24e6e6c link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-azure-upi 24e6e6c link /test pj-rehearse
ci/prow/pj-rehearse 24e6e6c link /test pj-rehearse
ci/prow/openshift-image-mirror-mappings 24e6e6c link /test openshift-image-mirror-mappings

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-bot
Copy link
Copy Markdown
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 27, 2021
@openshift-bot
Copy link
Copy Markdown
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 11, 2022
@openshift-bot
Copy link
Copy Markdown
Contributor

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci Bot closed this Feb 18, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 18, 2022

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

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

Labels

lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants