Skip to content

[release-4.22] AGENT-1547: Backport NoRegistryClusterInstall feature to release-4.22#738

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
pawanpinjarkar:cherrypick-719-4.22
Jul 17, 2026
Merged

[release-4.22] AGENT-1547: Backport NoRegistryClusterInstall feature to release-4.22#738
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
pawanpinjarkar:cherrypick-719-4.22

Conversation

@pawanpinjarkar

Copy link
Copy Markdown
Contributor

This patch is part of the NoRegistryClusterInstall feature backport to 4.22. It contains the following PR:
#719

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 15, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 15, 2026

Copy link
Copy Markdown

@pawanpinjarkar: This pull request references AGENT-1547 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:

This patch is part of the NoRegistryClusterInstall feature backport to 4.22. It contains the following PR:
#719

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.

@openshift-ci
openshift-ci Bot requested review from romfreiman and rwsu July 15, 2026 21:27
@openshift-ci

openshift-ci Bot commented Jul 15, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pawanpinjarkar

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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 15, 2026
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/depends on openshift/api#2930

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 15, 2026
@openshift-ci

openshift-ci Bot commented Jul 15, 2026

Copy link
Copy Markdown

@pawanpinjarkar: 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/prow/e2e-agent-compact-ipv4-iso-no-registry 6ea417d link false /test e2e-agent-compact-ipv4-iso-no-registry
ci/prow/e2e-sno-dualstack-dhcp 6ea417d link false /test e2e-sno-dualstack-dhcp

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.

@bfournie

Copy link
Copy Markdown
Contributor

@pawanpinjarkar I think you can remove the hold

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/hold cancel as openshift/api#2930 is merged

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 17, 2026
@bfournie

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 17, 2026
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-merge-bot
openshift-merge-bot Bot merged commit 89060e1 into openshift:release-4.22 Jul 17, 2026
5 of 7 checks passed
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants