[release-4.9] [release 4.10] Bug 2109399: openshift-apiserver pods never going NotReady

[openshift-cherrypick-robot]

This is an automated cherry-pick of #501

/assign sanchezl

[openshift-ci]

@openshift-cherrypick-robot: Bugzilla bug 2109235 has been cloned as Bugzilla bug 2109399. Retitling PR to link against new bug.
/retitle [release-4.9] [release 4.10] Bug 2109399: openshift-apiserver pods never going NotReady

In response to this:

[release-4.9] [release 4.10] Bug 2109235: openshift-apiserver pods never going NotReady

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/test-infra repository.

[openshift-ci]

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2109399, which is invalid:

• expected dependent Bugzilla bug 2109235 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead

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

In response to this:

[release-4.9] [release 4.10] Bug 2109399: openshift-apiserver pods never going NotReady

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/test-infra repository.

[openshift-ci]

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[sanchezl]

/bugzilla refresh

[openshift-ci]

@sanchezl: This pull request references Bugzilla bug 2109399, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.9.z) matches configured target release for branch (4.9.z)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 2109235 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 2109235 targets the "4.10.z" release, which is one of the valid target releases: 4.10.0, 4.10.z
• bug has dependents

Requesting review from QA contact:
/cc @gangwgr

In response to this:

/bugzilla 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 kubernetes/test-infra repository.

[sanchezl]

1. If the Bugzilla associated with the PR has the "FastFix" keyword, the subjective assessment on the issue has already been done and a customer is impacted. These PRs should be prioritized for merge.
   • verified
   • does not apply
2. The bug has significant impact either through severity, reduction in supportability, or number of users affected.
   • verified
   • does not apply
3. For branches that are in the Maintenance lifecycle phase:
   • The bug is a critical fix, no reasonable workaround exists, and a recommendation for upgrade has been ruled out, or
   • The bug is a security related bug
   • Branch not in maintenance mode yet (current release + previous release for 90 days after current GA; everything older is in maintenance)
4. The severity field of the bug must be set to accurately reflect criticality.
   • verified
5. The PR was created with the cherry-pick bot OR the PR’s description is well formed with user-focused release notes that state the bug number, impact, cause, and resolution. Where appropriate, it should also contain information about how a user can identify whether a particular cluster is affected.
   • verified

[mfojtik]

/lgtm
/approve

[mfojtik]

@openshift/openshift-patch-managers, a customer is waiting for this fix to be delivered in 4.9.z as soon as possible.

[sdodson]

@mfojtik Can you try to lgtm and approve again? Once that's done it should just be waiting on QE to add cherry-pick-approved I don't mind adding lgtm and approved labels by proxy based on your earlier comment, but I'm curious why the bot ignored you since you're in OWNERS

[mfojtik]

/lgtm
/approve

[mfojtik]

adding labels by hand as the bot seems to be lagging.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mfojtik, openshift-cherrypick-robot

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mfojtik]

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

[wangke19]

/label cherry-pick-approved

[openshift-ci]

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

• openshift/cluster-openshift-apiserver-operator#502

Bugzilla bug 2109399 has been moved to the MODIFIED state.

In response to this:

[release-4.9] [release 4.10] Bug 2109399: openshift-apiserver pods never going NotReady

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/test-infra repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-openshift-apiserver-operator-container-v4.9.0-202311250023.p0.g3b9b828.assembly.stream for distgit ose-cluster-openshift-apiserver-operator.
All builds following this will include this PR.