Skip to content

Add deploy-sno-reconfig-ipv6 test job for jetlag#76604

Draft
mcornea wants to merge 2 commits intoopenshift:mainfrom
mcornea:jetlag-deploy-sno-reconfig-ipv6
Draft

Add deploy-sno-reconfig-ipv6 test job for jetlag#76604
mcornea wants to merge 2 commits intoopenshift:mainfrom
mcornea:jetlag-deploy-sno-reconfig-ipv6

Conversation

@mcornea
Copy link
Contributor

@mcornea mcornea commented Mar 20, 2026

Summary

Add a test job that verifies the assisted-service pod properly picks up configuration changes when redeploying on the same bastion. The job:

  1. Deploys SNO with standard IPv4 configuration
  2. Reconfigures all.yml for single-stack IPv6 with setup_bastion_registry: true and use_bastion_registry: true
  3. Re-runs setup-bastion.yml + sno-deploy.yml without cleaning up containers
  4. Verifies the IPv6 deployment succeeds (assisted-service pod picks up new config)

This tests the fix in redhat-performance/jetlag#787.

Changes

  • ref YAML: Add REDEPLOY_IPV6 env var (default false)
  • commands script: After initial deploy, if REDEPLOY_IPV6=true, append IPv6 network config + setup_bastion_registry: true + use_bastion_registry: true to all.yml and redeploy without clean-resources.sh
  • test config: Add deploy-sno-reconfig-ipv6 test entry with JETLAG_PR: "787"

After jetlag PR merges

Remove JETLAG_PR: "787" from the test entry and keep the job as a permanent regression test.

Test plan

  • /test deploy-sno-reconfig-ipv6 — verifies the full IPv4→IPv6 reconfig path

Add a test job that deploys SNO with IPv4, then reconfigures for
single-stack IPv6 with bastion registry and redeploys on the same
bastion without cleaning up. This tests that the assisted-service
pod properly picks up configuration changes on redeploy.

New env var REDEPLOY_IPV6 controls the reconfig behavior.
Uses JETLAG_PR=787 to test the companion jetlag fix.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci openshift-ci bot requested review from capolrik and rsevilla87 March 20, 2026 13:19
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 20, 2026
Run make ci-operator-config and make jobs to update generated files.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 20, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mcornea

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

The pull request process is described 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

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@mcornea: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-rhoso-x86-weekly-compact-6nodes openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-4.19-nightly-x86-daily-virt-6nodes openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-4.19-nightly-x86-weekly-6nodes openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-4.19-nightly-x86-deploy-6nodes openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-4.19-nightly-x86-deploy-sno openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-4.19-nightly-x86-netperf-external-sno openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-telco-x86-rds-core openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-telco-x86-regulus-cpt openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-telco-x86-regulus-jetlag openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-x86-deploy-hmno openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-x86-deploy-vmno openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-x86-deploy-vmno-private openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-selfsched-x86-self-sched-jetlag openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-selfsched-x86-self-sched-node-density openshift-eng/ocp-qe-perfscale-ci presubmit Registry content changed
pull-ci-cloud-bulldozer-e2e-benchmarking-master-e2e-rds-core-mno cloud-bulldozer/e2e-benchmarking presubmit Registry content changed
pull-ci-cloud-bulldozer-e2e-benchmarking-master-e2e-vm-density-single-node cloud-bulldozer/e2e-benchmarking presubmit Registry content changed
pull-ci-redhat-performance-jetlag-main-deploy-sno redhat-performance/jetlag presubmit Registry content changed
pull-ci-redhat-performance-jetlag-main-deploy-sno-private redhat-performance/jetlag presubmit Registry content changed
pull-ci-redhat-performance-jetlag-main-deploy-sno-private-bond redhat-performance/jetlag presubmit Registry content changed
pull-ci-redhat-performance-jetlag-main-deploy-mno redhat-performance/jetlag presubmit Registry content changed
pull-ci-redhat-performance-jetlag-main-deploy-mno-private redhat-performance/jetlag presubmit Registry content changed
pull-ci-redhat-performance-jetlag-main-deploy-mno-private-bond redhat-performance/jetlag presubmit Registry content changed
pull-ci-redhat-performance-jetlag-main-deploy-cmno redhat-performance/jetlag presubmit Registry content changed
pull-ci-redhat-performance-jetlag-main-deploy-cmno-private redhat-performance/jetlag presubmit Registry content changed
pull-ci-redhat-performance-jetlag-main-deploy-cmno-private-bond redhat-performance/jetlag presubmit Registry content changed

A total of 40 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
The following jobs are not rehearsable without the network-access-rehearsals-ok, and approved labels present on this PR. This is due to the restrict_network_access field being set to false. The network-access-rehearsals-ok label can be added by any openshift org member other than the PR's author by commenting: /pj-rehearse network-access-allowed:

Test name
pull-ci-redhat-performance-jetlag-main-deploy-sno-reconfig-ipv6
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@mcornea mcornea marked this pull request as draft March 20, 2026 13:38
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 20, 2026
@mcornea
Copy link
Contributor Author

mcornea commented Mar 20, 2026

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 20, 2026

@mcornea: all tests passed!

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

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants