[release-4.22]AGENT-1548: Backport NoRegistryClusterInstall feature to release-4.22

[bfournie]

Backport the following PRs:
#5765
#5721
#6003
#6041
#6070
#5988
#5841
#6100
#6109
#6146
#6145
#6159
#6280

- What I did

- How to verify it

- Description for the changelog

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@bfournie: This pull request references AGENT-1500 which is a valid jira issue.

Details

In response to this:

Backport the following PRs:
#5765
#5721
#6003
#6041
#6070
#5988
#5841
#6100
#6109
#6146
#6145
#6159
#6280

- What I did

- How to verify it

- Description for the changelog

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 openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 51ef5107-8e9c-4ffe-b045-7aff932f9446

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci-robot]

@bfournie: This pull request references AGENT-1548 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Backport the following PRs:
#5765
#5721
#6003
#6041
#6070
#5988
#5841
#6100
#6109
#6146
#6145
#6159
#6280

- What I did

- How to verify it

- Description for the changelog

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 openshift-eng/jira-lifecycle-plugin repository.

[bfournie]

/jira refresh

[openshift-ci-robot]

@bfournie: This pull request references AGENT-1548 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[bfournie]

/test unit

[bfournie]

/test unit
Looks like a flake unrelated to the changes.

[bfournie]

/test unit

[bfournie]

/test unit

[bfournie]

/test ?

[bfournie]

/test e2e-agent-compact-ipv4-iso-no-registry

[bfournie]

/test e2e-agent-compact-ipv4-iso-no-registry

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-upgrade
/test e2e-gcp-op-ocl-part1
/test e2e-gcp-op-ocl-part2
/test e2e-gcp-op-part1
/test e2e-gcp-op-part2
/test e2e-gcp-op-single-node
/test e2e-hypershift

[pawanpinjarkar]

/retitle [release-4.22]AGENT-1548: Backport NoRegistryClusterInstall feature to release-4.22

[bfournie]

/retest-required

[ptalgulk01]

Deployed this jobs

• 4.22-aws-1of3: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-aws-mco-fips-proxy-longduration-1of3/2081725692298399744
• 4.22-aws-2of3: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-aws-mco-fips-proxy-longduration-2of3/2081725739681452032
• 4.22-aws-3of3: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-aws-mco-fips-proxy-longduration-3of3/2081725787471351808
• 4.22-vsphere-1of2: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-vsphere-mco-tp-longduration-1of2/2081725834556608512
• 4.22-vsphere-2of2: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-vsphere-mco-tp-longduration-2of2/2081725881910300672

[yuqi-zhang]

Logically seems fine - I think this is only "missing" #6119 - would probably be nice to have.

If both core MCO tests are fine, and it's passing your install job, this should be safe to merge

[andfasano]

/lgtm

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-upgrade
/test e2e-gcp-op-ocl-part1
/test e2e-gcp-op-ocl-part2
/test e2e-gcp-op-part1
/test e2e-gcp-op-part2
/test e2e-gcp-op-single-node
/test e2e-hypershift

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano, bfournie, yuqi-zhang

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:

• OWNERS [yuqi-zhang]

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

[bfournie]

Logically seems fine - I think this is only "missing" #6119 - would probably be nice to have.

If both core MCO tests are fine, and it's passing your install job, this should be safe to merge

Good idea, added #6119. Would you be able to add the backport-risk-assessed label and also set the jira/valid-bug since this is using an SBAR and not OCPBUGS? Thanks.

[bfournie]

/test e2e-agent-compact-ipv4-iso-no-registry

[bfournie]

@ptalgulk01 I updated the PR so those jobs may need to be deployed again. Thank you.

[bfournie]

/test e2e-agent-compact-ipv4-iso-no-registry

[ptalgulk01]

new deployed job
Job: aws-fips-longduration-1of3
URL: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-aws-mco-fips-proxy-longduration-1of3/2082034792009830400
Job: aws-fips-longduration-2of3
URL: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-aws-mco-fips-proxy-longduration-2of3/2082034804135563264
Job: aws-fips-longduration-3of3
URL: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-aws-mco-fips-proxy-longduration-3of3/2082034812469645312
Job: vsphere-tp-longduration-1of2
URL: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-vsphere-mco-tp-longduration-1of2/2082034827795632128
Job: vsphere-tp-longduration-2of2
URL: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-vsphere-mco-tp-longduration-2of2/2082034842433753088

[andfasano]

Logically seems fine - I think this is only "missing" #6119 - would probably be nice to have.
If both core MCO tests are fine, and it's passing your install job, this should be safe to merge

Good idea, added #6119. Would you be able to add the backport-risk-assessed label and also set the jira/valid-bug since this is using an SBAR and not OCPBUGS? Thanks.

cc @yuqi-zhang

[bfournie]

/verified by ci/prow/e2e-agent-compact-ipv4-iso-no-registry

[openshift-ci-robot]

@bfournie: This PR has been marked as verified by ci/prow/e2e-agent-compact-ipv4-iso-no-registry.

Details

In response to this:

/verified by ci/prow/e2e-agent-compact-ipv4-iso-no-registry

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 openshift-eng/jira-lifecycle-plugin repository.

[bfournie]

/test unit

[zaneb]

Manually adding valid-bug as this is subject to an approved SBAR.

[openshift-ci]

@bfournie: 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/prow/unit	eb98061	link	true	/test unit

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.