OTA-1542 sync rhel update for chainupgrade&cpou steps

[jiajliu]

follow up #65369

/cc nobody

[openshift-ci]

@jiajliu: GitHub didn't allow me to request PR reviews from the following users: nobody.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

follow up #65369

/cc nobody

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.

[jiajliu]

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-4.14-cpou-upgrade-from-4.12-azure-ipi-workers-rhel8-f28 periodic-ci-openshift-openshift-tests-private-release-4.18-amd64-nightly-4.18-cpou-upgrade-from-4.16-vsphere-upi-encrypt-f28

[openshift-ci-robot]

@jiajliu: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@jiajliu: 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-aws-ipsec-4.16-nightly-x86-loaded-upgrade-from-4.15-loaded-upgrade-415to416-24nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-metal-4.18-nightly-multi-cpou-loaded-upgrade-from-4.16-loaded-upgrade-multi-416to418-3nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.16-nightly-x86-cpou-loaded-upgrade-from-4.14-loaded-upgrade-414to416-24nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.16-nightly-x86-cpou-loaded-upgrade-from-4.14-loaded-upgrade-414to416-120nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.16-nightly-x86-cpou-loaded-upgrade-from-4.14-loaded-upgrade-ipsec-414to416-120nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.14-nightly-x86-cpou-loaded-upgrade-from-4.12-loaded-upgrade-412to414-24nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.14-nightly-x86-cpou-loaded-upgrade-from-4.12-loaded-upgrade-412to414-120nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.14-nightly-x86-cpou-loaded-upgrade-from-4.12-loaded-upgrade-ipsec-412to414-120nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.18-nightly-x86-cpou-loaded-upgrade-from-4.16-loaded-upgrade-416to418-24nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.18-nightly-x86-cpou-loaded-upgrade-from-4.16-loaded-upgrade-416to418-120nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.18-nightly-x86-cpou-loaded-upgrade-from-4.16-loaded-upgrade-ipsec-416to418-120nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.19-nightly-x86-cpou-loaded-upgrade-from-4.17-loaded-upgrade-417to419-24nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.19-nightly-x86-cpou-loaded-upgrade-from-4.17-loaded-upgrade-417to419-120nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.19-nightly-x86-cpou-loaded-upgrade-from-4.17-loaded-upgrade-ipsec-417to419-120nodes	openshift-eng/ocp-qe-perfscale-ci	presubmit	Registry content changed
pull-ci-redhat-chaos-prow-scripts-main-4.18-nightly-x86-cpou-upgrade-4.16-loaded-upgrade-416to418-aws	redhat-chaos/prow-scripts	presubmit	Registry content changed
pull-ci-redhat-chaos-prow-scripts-main-4.18-nightly-x86-cpou-upgrade-4.16-loaded-upgrade-416to418-gcp	redhat-chaos/prow-scripts	presubmit	Registry content changed
periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.14-nightly-x86-cpou-loaded-upgrade-from-4.12-loaded-upgrade-ipsec-412to414-24nodes	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.17-amd64-nightly-4.17-upgrade-from-stable-4.16-vsphere-ipi-proxy-workers-rhel8-f28	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.14-multi-nightly-4.14-upgrade-from-stable-4.14-aws-ipi-ingress-lbtype-nlb-arm-f60	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.17-multi-nightly-4.17-upgrade-from-stable-4.16-azure-ipi-usertags-sa-encryption-arm-f28	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.15-multi-nightly-4.15-upgrade-from-stable-4.14-azure-ipi-ovn-ipsec-azurefile-csi-arm-f28	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.18-amd64-nightly-4.18-upgrade-from-stable-4.18-baremetalds-ipi-ovn-ipv4-fips-f60	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.19-amd64-nightly-4.19-upgrade-from-stable-4.19-ibmcloud-ipi-tp-f28	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.17-amd64-nightly-4.17-upgrade-from-stable-4.17-ibmcloud-ipi-private-byo-kms-f60	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.17-amd64-nightly-4.17-upgrade-from-stable-4.16-gcp-ipi-mini-perm-custom-type-f28	N/A	periodic	Registry content changed

A total of 1797 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

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.

[jiajliu]

There is not chainupgrade/cpou jobs with rhel worker through 4.19+, run regression tests on old paths:

1. 4.12-4.14 cpou with rhel worker

• rhel worker found and upgrade skipped in cucushift-chainupgrade-toimage
• rhel worker found and skip mcp status check in cucushift-upgrade-cpou-unpause-worker-mcp

2. 4.16-4.18 cpou without rhel worker

• no rhel worker found in cucushift-chainupgrade-toimage
• mcp status check is executed in cucushift-upgrade-cpou-unpause-worker-mcp

cc @jianlinliu @gpei to review, thanks.
btw, the rhel worker upgrade in 4.12-4.14 jobs failed, is any any known issue on it?

[openshift-ci]

@jiajliu: The following test 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/periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-4.14-cpou-upgrade-from-4.12-azure-ipi-workers-rhel8-f28	8f7093a	link	unknown	/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-4.14-cpou-upgrade-from-4.12-azure-ipi-workers-rhel8-f28

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.

[jianlinliu]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jiajliu, jianlinliu

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:

• ci-operator/step-registry/cucushift/chainupgrade/toimage/OWNERS [jiajliu,jianlinliu]
• ci-operator/step-registry/cucushift/upgrade/cpou/unpause-worker-mcp/OWNERS [jiajliu,jianlinliu]
• ci-operator/step-registry/cucushift/upgrade/rhel-worker/OWNERS [jiajliu,jianlinliu]

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

[jianlinliu]

the rhel worker upgrade in 4.12-4.14 jobs failed

Seem like when updating the 1st rhel worker, kubelet service failed to work, I did not see any useful log from the log, @gpei do you have any idea on this ?

[gpei]

the rhel worker upgrade in 4.12-4.14 jobs failed

Seem like when updating the 1st rhel worker, kubelet service failed to work, I did not see any useful log from the log, @gpei do you have any idea on this ?

yeah, I guess it would be a bug for RHEL worker upgrade from 4.12 to 4.13/4.14, the kubelet service can't be started after the update. I had a check on existing 4.13 to 4.14 upgrade jobs with RHEL workers, it's still working. I can try to reproduce this later today.

[jiajliu]

/pj-rehearse ack

[openshift-ci-robot]

@jiajliu: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.