[release-4.22] AGENT-1583: post-feature promotion (NoRegistryClusterInstall) openshift/api dependencies bump

[pawanpinjarkar]

Update the api and client-go version to the same version from openshift/machine-config-operator#6418 to be in sync with other code bases.

[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: automatic mode

[openshift-ci-robot]

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

Update the api and client-go version to the same version from openshift/machine-config-operator#6418 to be in sync with other code bases.

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: 5e1b5e7d-7f47-4ce0-99a9-c76f34b7f548

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

---

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

[pawanpinjarkar]

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

[redhat-chai-bot]

/override ci/prow/verify-deps

Automated triage: This failure appears unrelated to the PR changes.

Rationale: verify-deps failed while downloading the unchanged github.com/distribution/distribution/v3@v3.0.0-20230530204932-ba46c769b3d1 module from proxy.golang.org, which returned an HTTP/2 INTERNAL_ERROR. The same run's companion go-verify-deps check independently failed on a different unchanged module with the same proxy stream error, indicating an external module-proxy failure rather than dependency drift introduced by this PR.

Evidence:

• PR changes are limited to github.com/openshift/api, github.com/openshift/client-go, and generated/vendored API files; distribution/v3 remains at the same version in base and head.
• ci/prow/verify-deps failed on proxy.golang.org stream error stream ID 997; INTERNAL_ERROR; received from peer while make verify-deps was resolving imports.
• ci/prow/go-verify-deps failed on github.com/k8snetworkplumbingwg/network-attachment-definition-client@v1.6.0 with the same proxy.golang.org HTTP/2 INTERNAL_ERROR pattern.
• ci/prow/lint, ci/prow/unit, and CodeRabbit passed; no build06 outage overlapped this run.

If you disagree with this assessment, /retest ci/prow/verify-deps to re-run the job.

---

AI-generated. Review for accuracy.

[openshift-ci]

@redhat-chai-bot: Overrode contexts on behalf of redhat-chai-bot: ci/prow/verify-deps

Details

In response to this:

/override ci/prow/verify-deps

Automated triage: This failure appears unrelated to the PR changes.

Rationale: verify-deps failed while downloading the unchanged github.com/distribution/distribution/v3@v3.0.0-20230530204932-ba46c769b3d1 module from proxy.golang.org, which returned an HTTP/2 INTERNAL_ERROR. The same run's companion go-verify-deps check independently failed on a different unchanged module with the same proxy stream error, indicating an external module-proxy failure rather than dependency drift introduced by this PR.

Evidence:

• PR changes are limited to github.com/openshift/api, github.com/openshift/client-go, and generated/vendored API files; distribution/v3 remains at the same version in base and head.
• ci/prow/verify-deps failed on proxy.golang.org stream error stream ID 997; INTERNAL_ERROR; received from peer while make verify-deps was resolving imports.
• ci/prow/go-verify-deps failed on github.com/k8snetworkplumbingwg/network-attachment-definition-client@v1.6.0 with the same proxy.golang.org HTTP/2 INTERNAL_ERROR pattern.
• ci/prow/lint, ci/prow/unit, and CodeRabbit passed; no build06 outage overlapped this run.

If you disagree with this assessment, /retest ci/prow/verify-deps to re-run the job.

---

AI-generated. Review for accuracy.

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.

[pawanpinjarkar]

/verified later @pawanpinjarkar

[openshift-ci-robot]

@pawanpinjarkar: This PR has been marked to be verified later by @pawanpinjarkar.

Details

In response to this:

/verified later @pawanpinjarkar

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.

[pawanpinjarkar]

/cc @neisw

[neisw]

/test go-verify-deps

[neisw]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neisw, 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:

• OWNERS [neisw]

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

[neisw]

/pipeline required

[openshift-merge-bot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[redhat-chai-bot]

/override ci/prow/e2e-aws-csi

Automated triage: This failure appears unrelated to the PR changes.

Rationale: The job failed before cluster provisioning or CSI test execution, while building the shared tools-openstack cache image. The build failed because DNS could not resolve the internal service base-openstack-4-22.ocp.svc, not because of a source or test failure.

Evidence:

• PR [release-4.22] AGENT-1583: post-feature promotion (NoRegistryClusterInstall) openshift/api dependencies bump #31565 is limited to openshift/api and openshift/client-go dependency bumps plus generated/vendor API updates; it does not change the CI build configuration or tools-openstack image.
• The log reports curl: (6) Could not resolve host: base-openstack-4-22.ocp.svc, followed by DockerBuildFailed and executing_graph:step_failed:building_cache_image.
• The three sibling AWS e2e contexts launched in the same build01 wave failed with the identical tools-openstack-amd64 DNS signature, while unit, lint, verify, images, and dependency verification checks passed.
• The same base-openstack-4-22.ocp.svc DNS signature was observed in a prior CI incident; no cluster provisioning or CSI tests ran in this job.

If you disagree with this assessment, /retest ci/prow/e2e-aws-csi to re-run the job.

---

AI-generated. Review for accuracy.

[openshift-ci]

@redhat-chai-bot: Overrode contexts on behalf of redhat-chai-bot: ci/prow/e2e-aws-csi

Details

In response to this:

/override ci/prow/e2e-aws-csi

Automated triage: This failure appears unrelated to the PR changes.

Rationale: The job failed before cluster provisioning or CSI test execution, while building the shared tools-openstack cache image. The build failed because DNS could not resolve the internal service base-openstack-4-22.ocp.svc, not because of a source or test failure.

Evidence:

• PR [release-4.22] AGENT-1583: post-feature promotion (NoRegistryClusterInstall) openshift/api dependencies bump #31565 is limited to openshift/api and openshift/client-go dependency bumps plus generated/vendor API updates; it does not change the CI build configuration or tools-openstack image.
• The log reports curl: (6) Could not resolve host: base-openstack-4-22.ocp.svc, followed by DockerBuildFailed and executing_graph:step_failed:building_cache_image.
• The three sibling AWS e2e contexts launched in the same build01 wave failed with the identical tools-openstack-amd64 DNS signature, while unit, lint, verify, images, and dependency verification checks passed.
• The same base-openstack-4-22.ocp.svc DNS signature was observed in a prior CI incident; no cluster provisioning or CSI tests ran in this job.

If you disagree with this assessment, /retest ci/prow/e2e-aws-csi to re-run the job.

---

AI-generated. Review for accuracy.

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.

[pawanpinjarkar]

/retest-required

[pawanpinjarkar]

@zaneb Please manually add the jira/valid-bug label.

[pawanpinjarkar]

/assign @zaneb

[openshift-ci]

@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-aws-ovn-fips	58fce5f	link	true	/test e2e-aws-ovn-fips
ci/prow/e2e-aws-csi	58fce5f	link	true	/test e2e-aws-csi
ci/prow/verify-deps	58fce5f	link	true	/test verify-deps

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.