[release-5.0] OCPBUGS-114877: move empty CRIOCredentialProviderConfig CR to run-level 0000_10 by openshift-cherrypick-robot · Pull Request #3019 · openshift/api

openshift-cherrypick-robot · 2026-08-28T19:14:47Z

This is an automated cherry-pick of #3011

/assign sdodson

…l 0000_10 The empty CRIOCredentialProviderConfig CR shipped at run-level 0000_05 while its CRD ships at 0000_10. Under the CVO's strict update-path ordering, a run-level acts as a barrier: the CVO will not advance to 0000_10 until 0000_05 completes. Because the feature gate is now enabled in Default, on an upgrade into the first release that introduces this CRD the CVO attempts to create the CR at 0000_05 before the CRD exists at 0000_10, the create fails, 0000_05 never completes, and the update deadlocks (self-managed-high-availability, Default). Move the empty CR up to run-level 0000_10 so it sorts after its CRD within the same run-level (CRD operatorOrdering 01 before CR 02), mirroring the existing node.cr precedent. Pure rename; no schema change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> rh-pre-commit.version: 2.4.0 rh-pre-commit.check-secrets: ENABLED

Walk payload-manifests/crds and payload-command/empty-resources; for every empty CR whose CRD is shipped in this repo, assert the CRD is applied before the CR under CVO ordering (bootstrap-required, a lower run-level, or the same run-level with a filename that byte-sorts first, matching the CVO's LC_ALL=C sort). This guards against the OCPBUGS-99266 class of deadlock where a CR sorts ahead of its CRD. The test parses manifests with k8s.io/apimachinery/pkg/util/yaml.NewYAMLReader (correctly handling multi-document files and "---" inside scalars) and accepts both .yaml and .yml files. The test's helper structs are not CRD API types, so extend the existing kubeapilinter exemption in .golangci.yaml from payload-command/*.go (files directly under the directory) to payload-command/ so it also covers the ordering/ subpackage; otherwise kubeapilinter flags the YAML-parsing structs and its nokind rule renames the Kind field and breaks the build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> rh-pre-commit.version: 2.4.0 rh-pre-commit.check-secrets: ENABLED

openshift-merge-bot · 2026-08-28T19:14:49Z

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

coderabbitai · 2026-08-28T19:14:54Z

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 YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: fee08ea1-6454-43ef-aad6-c765e54fefdf

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.}

openshift-ci · 2026-08-28T19:14:57Z

Hello @openshift-cherrypick-robot! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

openshift-ci-robot · 2026-08-28T19:15:56Z

@openshift-cherrypick-robot: Jira Issue OCPBUGS-99266 has been cloned as Jira Issue OCPBUGS-114877. Will retitle bug to link to clone.
/retitle [release-5.0] OCPBUGS-114877: move empty CRIOCredentialProviderConfig CR to run-level 0000_10

Details

In response to this:

This is an automated cherry-pick of #3011

/assign sdodson

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-robot · 2026-08-28T19:16:05Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-114877, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #3011

/assign sdodson

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.

sdodson · 2026-08-28T19:23:25Z

/lgtm
/label approved
/verified by CI
/jira refresh

openshift-ci-robot · 2026-08-28T19:23:37Z

@sdodson: This PR has been marked as verified by CI.

Details

In response to this:

/lgtm
/label approved
/verified by CI
/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.

openshift-merge-bot · 2026-08-28T19:23:38Z

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-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change

openshift-ci-robot · 2026-08-28T19:23:40Z

@sdodson: This pull request references Jira Issue OCPBUGS-114877, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/lgtm
/label approved
/verified by CI
/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.

openshift-ci · 2026-08-28T19:23:46Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sdodson
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

OWNERS

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

openshift-ci · 2026-08-28T23:21:09Z

@openshift-cherrypick-robot: 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/e2e-aws-ovn-techpreview	`2604afa`	link	true	`/test e2e-aws-ovn-techpreview`

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.

sdodson added 2 commits August 28, 2026 19:14

openshift-cherrypick-robot assigned sdodson Aug 28, 2026

openshift-cherrypick-robot mentioned this pull request Aug 28, 2026

OCPBUGS-99266: move empty CRIOCredentialProviderConfig CR to run-level 0000_10 #3011

Merged

openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Aug 28, 2026

openshift-ci Bot requested review from JoelSpeed and everettraven August 28, 2026 19:15

openshift-ci Bot changed the title ~~[release-5.0] OCPBUGS-99266: move empty CRIOCredentialProviderConfig CR to run-level 0000_10~~ [release-5.0] OCPBUGS-114877: move empty CRIOCredentialProviderConfig CR to run-level 0000_10 Aug 28, 2026

openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Aug 28, 2026

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 28, 2026

openshift-ci Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels Aug 28, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 28, 2026

openshift-ci Bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 28, 2026

Navigation Menu

Uh oh!

[release-5.0] OCPBUGS-114877: move empty CRIOCredentialProviderConfig CR to run-level 0000_10 - #3019

[release-5.0] OCPBUGS-114877: move empty CRIOCredentialProviderConfig CR to run-level 0000_10#3019
openshift-cherrypick-robot wants to merge 2 commits into
openshift:release-5.0from
openshift-cherrypick-robot:cherry-pick-3011-to-release-5.0

openshift-cherrypick-robot commented Aug 28, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 28, 2026

Uh oh!

coderabbitai Bot commented Aug 28, 2026

Review skipped

Uh oh!

openshift-ci Bot commented Aug 28, 2026

Uh oh!

openshift-ci-robot commented Aug 28, 2026

Uh oh!

openshift-ci-robot commented Aug 28, 2026

Uh oh!

sdodson commented Aug 28, 2026

Uh oh!

openshift-ci-robot commented Aug 28, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 28, 2026

Uh oh!

openshift-ci-robot commented Aug 28, 2026

Uh oh!

openshift-ci Bot commented Aug 28, 2026

Uh oh!

openshift-ci Bot commented Aug 28, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

openshift-cherrypick-robot commented Aug 28, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 28, 2026

Uh oh!

coderabbitai Bot commented Aug 28, 2026

Review skipped

Uh oh!

openshift-ci Bot commented Aug 28, 2026

Uh oh!

openshift-ci-robot commented Aug 28, 2026

Uh oh!

openshift-ci-robot commented Aug 28, 2026

Uh oh!

sdodson commented Aug 28, 2026

Uh oh!

openshift-ci-robot commented Aug 28, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 28, 2026

Uh oh!

openshift-ci-robot commented Aug 28, 2026

Uh oh!

openshift-ci Bot commented Aug 28, 2026

Uh oh!

openshift-ci Bot commented Aug 28, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants