Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.17] OCPBUGS-39558: Filter out shallowly UpdateEffectNone errors from a MultipleErrors message in the Failing condition #1114

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1050

/assign DavidHurta

…erVersionStatus

This commit will add additional testing regarding setting the Failing
condition using the `updateClusterVersionStatus` function. This is to
ensure no functionality is lost upon new changes.
…n MultipleErrors in Failing condition

Various errors get propagated to users, such as the summarized task
graph error. For example, in the form of the message in the Failing
condition. However, update errors set with the update effect of
UpdateEffectNone can confuse users, as these primarily informing
messages get displayed together with valid update errors that heavily
impact the update. This can result in a message such as:

{
  "lastTransitionTime": "2023-06-20T13:40:12Z",
  "message": "Multiple errors are preventing progress:\n* Cluster
  operator authentication is updating versions\n* Could not update
  customresourcedefinition \"alertingrules.monitoring.openshift.io\"
  (512 of 993): the object is invalid, possibly due to local cluster
  configuration",
  "reason": "MultipleErrors",
  "status": "True",
  "type": "Failing"
}

The Failing condition is not true because of the UpdateEffectNone
error ("Cluster operator authentication is updating versions"), but
its message still gets displayed.

This commit makes sure that update errors that do not heavily affect
the update will be removed from the MultipleErrors error in the Failing
condition message to an extent.

The filtered out errors from the message will still be displayed in the
logs and in other places, such as the ReconciliationIssues condition.

The original code handles correctly situations where the status failure
is an UpdateEffectNone error. The new changes leave such errors be. In
case the MultipleErrors error contains only UpdateEffectNone errors, the
error is unchanged to keep the original logic unchanged and keep the
commit simple. The goal of this commit is to remove unimportant messages
from MultipleErrors errors that contain valid messages in the Failing
condition.

The current code contains an override to set the Failing condition
when history is empty or the CVO is reconciling. This commit will keep
this logic functional. This means the filtering is only applied
when history is not empty and the CVO is not reconciling the payload.
Due to the introduced filtering of UpdateError errors before setting the
Failing condition, it is needed to update the TestCVO_ParallelError
test, as its errors are getting rightfully filtered due to their
UpdateEffect being None. This commit is utilizing this chance to
update the UpdateEffect of one of the errors to test the filtering here
as well.
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-15200 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.17] OCPBUGS-39558: Filter out shallowly UpdateEffectNone errors from a MultipleErrors message in the Failing condition

In response to this:

This is an automated cherry-pick of #1050

/assign DavidHurta

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 changed the title [release-4.17] OCPBUGS-15200: Filter out shallowly UpdateEffectNone errors from a MultipleErrors message in the Failing condition [release-4.17] OCPBUGS-39558: Filter out shallowly UpdateEffectNone errors from a MultipleErrors message in the Failing condition Nov 26, 2024
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Nov 26, 2024
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-39558, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-15200 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-15200 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
  • bug has dependents

Requesting review from QA contact:
/cc @dis016

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

In response to this:

This is an automated cherry-pick of #1050

/assign DavidHurta

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.

@DavidHurta
Copy link
Contributor

/test e2e-hypershift

@DavidHurta
Copy link
Contributor

DavidHurta commented Nov 27, 2024

This is not the first time I see a NTOMachineConfigRolloutTest test to fail (failure not relevant to its PR). I suspect some issues with the test. Let me investigate.

@DavidHurta
Copy link
Contributor

DavidHurta commented Nov 27, 2024

Follow up on #1114 (comment)
There were recent updates to the test logic (openshift/hypershift#4973). The tests being flaky and exceeding their timeout is being tracked at https://issues.redhat.com/browse/OCPBUGS-43824.

@DavidHurta
Copy link
Contributor

/test e2e-hypershift
A last attempt.

@DavidHurta
Copy link
Contributor

/override ci/prow/e2e-hypershift

The CI seems to be flaky. The changes from the PR only filter messages propagated to the ClusterVersion Failing condition. The failing CI is not relevant to the PR.

There were three runs:

  • 1st: Failed on TestCreateClusterProxy/ValidateHostedCluster; TestNodePool/HostedCluster0/Main/TestNTOMachineConfigAppliedInPlace passed
  • 2nd: Failed on TestNodePool/HostedCluster0/Main/TestNTOMachineConfigAppliedInPlace; TestCreateClusterProxy/ValidateHostedCluster passed
  • 3rd: Failed to create the cluster

Copy link
Contributor

openshift-ci bot commented Nov 28, 2024

@DavidHurta: DavidHurta unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers.

In response to this:

/override ci/prow/e2e-hypershift

The CI seems to be flaky. The changes from the PR only filter messages propagated to the ClusterVersion Failing condition. The failing CI is not relevant to the PR.

There were three runs:

  • 1st: Failed on TestCreateClusterProxy/ValidateHostedCluster; TestNodePool/HostedCluster0/Main/TestNTOMachineConfigAppliedInPlace passed
  • 2nd: Failed on TestNodePool/HostedCluster0/Main/TestNTOMachineConfigAppliedInPlace; TestCreateClusterProxy/ValidateHostedCluster passed
  • 3rd: Failed to create the cluster

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.

@DavidHurta
Copy link
Contributor

The 4.17 branch has my older username Davoska in the OWNERS file.

@petr-muller
Copy link
Member

/override ci/prow/e2e-hypershift

Copy link
Contributor

openshift-ci bot commented Nov 28, 2024

@petr-muller: Overrode contexts on behalf of petr-muller: ci/prow/e2e-hypershift

In response to this:

/override ci/prow/e2e-hypershift

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.

Copy link
Member

@petr-muller petr-muller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Nov 29, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 29, 2024
Copy link
Contributor

openshift-ci bot commented Nov 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

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 Nov 29, 2024
@dis016
Copy link

dis016 commented Dec 5, 2024

Install a 4.17 Cluster and degrade the CO authentication

[root@preserve-dis016-centos9 cloud-user]# oc get clusterversion 
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.17.0-0.nightly-2024-12-03-082523   True        False         41m     Cluster version is 4.17.0-0.nightly-2024-12-03-082523
[root@preserve-dis016-centos9 cloud-user]# vi oauth.yaml 
[root@preserve-dis016-centos9 cloud-user]# 
[root@preserve-dis016-centos9 cloud-user]# 
[root@preserve-dis016-centos9 cloud-user]# 
[root@preserve-dis016-centos9 cloud-user]# oc get clusterversion 
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.17.0-0.nightly-2024-12-03-082523   True        False         43m     Cluster version is 4.17.0-0.nightly-2024-12-03-082523
[root@preserve-dis016-centos9 cloud-user]# cat oauth.yaml 
apiVersion: config.openshift.io/v1
kind: OAuth
metadata:
  name: cluster
spec:
  identityProviders:
  - name: oidcidp 
    mappingMethod: claim 
    type: OpenID
    openID:
      clientID: test
      clientSecret: 
        name: test
      claims: 
        preferredUsername:
        - preferred_username
        name:
        - name
        email:
        - email
      issuer: https://www.idp-issuer.example.com
[root@preserve-dis016-centos9 cloud-user]# oc apply -f oauth.yaml 
Warning: resource oauths/cluster is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by oc apply. oc apply should only be used on resources created declaratively by either oc create --save-config or oc apply. The missing annotation will be patched automatically.
oauth.config.openshift.io/cluster configured
[root@preserve-dis016-centos9 cloud-user]# oc get co authentication 
NAME             VERSION                              AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
authentication   4.17.0-0.nightly-2024-12-03-082523   True        False         True       46m     OAuthServerConfigObservationDegraded: failed to apply IDP oidcidp config: dial tcp: lookup www.idp-issuer.example.com on 172.30.0.10:53: no such host
[root@preserve-dis016-centos9 cloud-user]#

Create a custom policy to prohibit the CVO from updating the openshift-samples operator deployment.

[root@preserve-dis016-centos9 cloud-user]# cat policy.yaml 
apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingAdmissionPolicy
metadata:
  name: example
spec:
  matchConstraints:
    namespaceSelector: {}
    objectSelector: {}
    resourceRules:
      - operations:
          - CREATE
          - UPDATE
        apiGroups:
          - apps
        apiVersions:
          - v1
        resources:
          - deployments
        scope: '*'
    matchPolicy: Equivalent
  validations:
    - expression: object.spec.replicas < 0
  failurePolicy: Fail
---
apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingAdmissionPolicyBinding
metadata:
  name: example
spec:
  policyName: example
  matchResources:
    namespaceSelector:
      matchLabels:
        kubernetes.io/metadata.name: openshift-cluster-samples-operator
    objectSelector: {}
    matchPolicy: Equivalent
  validationActions:
    - Deny
[root@preserve-dis016-centos9 cloud-user]# oc apply -f policy.yaml 
validatingadmissionpolicy.admissionregistration.k8s.io/example created
validatingadmissionpolicybinding.admissionregistration.k8s.io/example created
[root@preserve-dis016-centos9 cloud-user]# 

Trigger an upgrade to version which contains the changes

[root@preserve-dis016-centos9 cloud-user]# oc adm upgrade --to-image=registry.build09.ci.openshift.org/ci-ln-lw2iwj2/release@sha256:e24e504b6c582a8003f244e339f7a0d31382af068f26943feed919e93821933c  --allow-explicit-upgrade --force --allow-upgrade-with-warnings
warning: The requested upgrade image is not one of the available updates. You have used --allow-explicit-upgrade for the update to proceed anyway
warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
warning: --allow-upgrade-with-warnings is bypassing: the cluster is experiencing an error reconciling "4.17.0-0.nightly-2024-12-03-082523":

  Reason: ClusterOperatorDegraded
  Message: Cluster operator authentication is degraded
Requested update to release image registry.build09.ci.openshift.org/ci-ln-lw2iwj2/release@sha256:e24e504b6c582a8003f244e339f7a0d31382af068f26943feed919e93821933c
[root@preserve-dis016-centos9 cloud-user]# 

Upgrade is triggered and CVO is throwing new error after sometime.

[root@preserve-dis016-centos9 cloud-user]# while true; do oc adm upgrade; oc get clusterversion version -o json | jq '.status.conditions[] | select (.type=="Failing")' ; sleep 60; done 
info: An upgrade is in progress. Working towards 4.17.0-0.test-2024-12-05-050616-ci-ln-lw2iwj2-latest: 132 of 901 done (14% complete), waiting on kube-controller-manager, kube-scheduler

Upgradeable=False

  Reason: PoolUpdating
  Message: Cluster operator machine-config should not be upgraded between minor versions: One or more machine config pools are updating, please see `oc get mcp` for further details

warning: Cannot display available updates:
  Reason: NoChannel
  Message: The update channel has not been configured.

{
  "lastTransitionTime": "2024-12-05T06:25:45Z",
  "status": "False",
  "type": "Failing"
}
...
...

Failing=True:

  Reason: MultipleErrors
  Message: Multiple errors are preventing progress:
  * Cluster operator authentication is degraded
  * Could not update deployment "openshift-cluster-samples-operator/cluster-samples-operator" (490 of 901): the object is invalid, possibly due to local cluster configuration

info: An upgrade is in progress. Unable to apply 4.17.0-0.test-2024-12-05-050616-ci-ln-lw2iwj2-latest: an unknown error has occurred: MultipleErrors

warning: Cannot display available updates:
  Reason: NoChannel
  Message: The update channel has not been configured.

{
  "lastTransitionTime": "2024-12-05T06:52:30Z",
  "message": "Multiple errors are preventing progress:\n* Cluster operator authentication is degraded\n* Could not update deployment \"openshift-cluster-samples-operator/cluster-samples-operator\" (490 of 901): the object is invalid, possibly due to local cluster configuration",
  "reason": "MultipleErrors",
  "status": "True",
  "type": "Failing"
}

check the CVO logs to be sure that message was filtered as expected.

[root@preserve-dis016-centos9 cloud-user]# oc logs deploy/cluster-version-operator -n openshift-cluster-version | grep Filtered -A 6
I1205 06:54:30.281537       1 status.go:308] Filtered failure message changed from 'Multiple errors are preventing progress:
* Cluster operator authentication is degraded
* Cluster operators monitoring, openshift-apiserver are updating versions
* Could not update deployment "openshift-cluster-samples-operator/cluster-samples-operator" (490 of 901): the object is invalid, possibly due to local cluster configuration' to 'Multiple errors are preventing progress:
* Cluster operator authentication is degraded
* Could not update deployment "openshift-cluster-samples-operator/cluster-samples-operator" (490 of 901): the object is invalid, possibly due to local cluster configuration'
I1205 06:54:30.281590       1 cvo.go:659] Finished syncing cluster version "openshift-cluster-version/version" (306.571µs)
[root@preserve-dis016-centos9 cloud-user]# 

After un-degrading the CO authentication. error should change from Multiple errors to UpdatePayloadResourceInvalid

[root@preserve-dis016-centos9 cloud-user]# oc get co authentication 
NAME             VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
authentication   4.17.0-0.test-2024-12-05-050616-ci-ln-lw2iwj2-latest   True        False         True       85m     OAuthServerConfigObservationDegraded: failed to apply IDP oidcidp config: dial tcp: lookup www.idp-issuer.example.com on 172.30.0.10:53: no such host
[root@preserve-dis016-centos9 cloud-user]# cat oauth.yaml 
apiVersion: config.openshift.io/v1
kind: OAuth
metadata:
  name: cluster
spec: {}
[root@preserve-dis016-centos9 cloud-user]# oc apply -f oauth.yaml 
oauth.config.openshift.io/cluster configured
[root@preserve-dis016-centos9 cloud-user]# 
[root@preserve-dis016-centos9 cloud-user]# oc get co authentication 
NAME             VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
authentication   4.17.0-0.test-2024-12-05-050616-ci-ln-lw2iwj2-latest   True        False         False      85m     
[root@preserve-dis016-centos9 cloud-user]# 

 
[root@preserve-dis016-centos9 cloud-user]# oc get clusterversion version -o json | jq '.status.conditions[] | select (.type=="Failing")'
{
  "lastTransitionTime": "2024-12-05T06:59:30Z",
  "message": "Could not update deployment \"openshift-cluster-samples-operator/cluster-samples-operator\" (490 of 901): the object is invalid, possibly due to local cluster configuration",
  "reason": "UpdatePayloadResourceInvalid",
  "status": "True",
  "type": "Failing"
}
[root@preserve-dis016-centos9 cloud-user]# oc adm upgrade 
Failing=True:

  Reason: UpdatePayloadResourceInvalid
  Message: Could not update deployment "openshift-cluster-samples-operator/cluster-samples-operator" (490 of 901): the object is invalid, possibly due to local cluster configuration

info: An upgrade is in progress. Unable to apply 4.17.0-0.test-2024-12-05-050616-ci-ln-lw2iwj2-latest: an unknown error has occurred: MultipleErrors

warning: Cannot display available updates:
  Reason: NoChannel
  Message: The update channel has not been configured.

[root@preserve-dis016-centos9 cloud-user]#

Delete the created policies

[root@preserve-dis016-centos9 cloud-user]# oc get ValidatingAdmissionPolicy
NAME                                VALIDATIONS   PARAMKIND                               AGE
example                             1             <unset>                                 40m
machine-configuration-guards        1             <unset>                                 104m
managed-bootimages-platform-check   1             config.openshift.io/v1/Infrastructure   104m
mcn-guards                          2             <unset>                                 104m
[root@preserve-dis016-centos9 cloud-user]# oc delete ValidatingAdmissionPolicy/example
validatingadmissionpolicy.admissionregistration.k8s.io "example" deleted
[root@preserve-dis016-centos9 cloud-user]# oc get ValidatingAdmissionPolicyBinding
NAME                                        POLICYNAME                          PARAMREF    AGE
example                                     example                             <unset>     40m
machine-configuration-guards-binding        machine-configuration-guards        <unset>     104m
managed-bootimages-platform-check-binding   managed-bootimages-platform-check   */cluster   104m
mcn-guards-binding                          mcn-guards                          <unset>     104m
[root@preserve-dis016-centos9 cloud-user]# oc delete ValidatingAdmissionPolicyBinding/example 
validatingadmissionpolicybinding.admissionregistration.k8s.io "example" deleted
[root@preserve-dis016-centos9 cloud-user]#

Upgrade should proceed without errors


[root@preserve-dis016-centos9 cloud-user]# while true; do oc adm upgrade; oc get clusterversion version -o json | jq '.status.conditions[] | select (.type=="Failing")' ; sleep 60; done 
Failing=True:

  Reason: UpdatePayloadResourceInvalid
  Message: Could not update deployment "openshift-cluster-samples-operator/cluster-samples-operator" (490 of 901): the object is invalid, possibly due to local cluster configuration

info: An upgrade is in progress. Unable to apply 4.17.0-0.test-2024-12-05-050616-ci-ln-lw2iwj2-latest: an unknown error has occurred: MultipleErrors

warning: Cannot display available updates:
  Reason: NoChannel
  Message: The update channel has not been configured.

{
  "lastTransitionTime": "2024-12-05T06:59:30Z",
  "message": "Could not update deployment \"openshift-cluster-samples-operator/cluster-samples-operator\" (490 of 901): the object is invalid, possibly due to local cluster configuration",
  "reason": "UpdatePayloadResourceInvalid",
  "status": "True",
  "type": "Failing"
}
...
info: An upgrade is in progress. Working towards 4.17.0-0.test-2024-12-05-050616-ci-ln-lw2iwj2-latest: 708 of 901 done (78% complete), waiting on monitoring

warning: Cannot display available updates:
  Reason: NoChannel
  Message: The update channel has not been configured.

{
  "lastTransitionTime": "2024-12-05T07:04:00Z",
  "status": "False",
  "type": "Failing"
}
...

Cluster version is 4.17.0-0.test-2024-12-05-050616-ci-ln-lw2iwj2-latest

Upgradeable=False

  Reason: PoolUpdating
  Message: Cluster operator machine-config should not be upgraded between minor versions: One or more machine config pools are updating, please see `oc get mcp` for further details

warning: Cannot display available updates:
  Reason: NoChannel
  Message: The update channel has not been configured.

{
  "lastTransitionTime": "2024-12-05T07:23:22Z",
  "status": "False",
  "type": "Failing"
}

@dis016
Copy link

dis016 commented Dec 5, 2024

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Dec 5, 2024
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-39558, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-15200 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-15200 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
  • bug has dependents

Requesting review from QA contact:
/cc @dis016

In response to this:

This is an automated cherry-pick of #1050

/assign DavidHurta

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.

@DavidHurta
Copy link
Contributor

@jiajliu, PTAL regarding the cherry-pick-approved label 🙌

@jiajliu
Copy link

jiajliu commented Dec 12, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Dec 12, 2024
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 5ce4d27 and 2 for PR HEAD 7e71284 in total

1 similar comment
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 5ce4d27 and 2 for PR HEAD 7e71284 in total

Copy link
Contributor

openshift-ci bot commented Dec 12, 2024

@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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit bc60dbd into openshift:release-4.17 Dec 12, 2024
12 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-39558: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-39558 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #1050

/assign DavidHurta

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: cluster-version-operator
This PR has been included in build cluster-version-operator-container-v4.17.0-202412120834.p0.gbc60dbd.assembly.stream.el9.
All builds following this will include this PR.

@DavidHurta
Copy link
Contributor

/cherry-pick release-4.16

@openshift-cherrypick-robot
Copy link
Author

@DavidHurta: new pull request created: #1128

In response to this:

/cherry-pick release-4.16

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants