OCPBUGS-15200: Filter out shallowly `UpdateEffectNone` errors from a `MultipleErrors` message in the Failing condition #1050

Davoska · 2024-06-03T14:08:13Z

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 PR makes sure that update errors that do not heavily affect
the update will be removed from the Failing condition message to an
extent.

This pull request references https://issues.redhat.com/browse/OCPBUGS-15200

openshift-ci-robot · 2024-06-03T14:09:38Z

@Davoska: This pull request references Jira Issue OCPBUGS-15200, which is invalid:

expected the bug to target the "4.17.0" version, but no target version was set

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.

In response to this:

The summarized task graph error gets propagated to users. 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 informing messages get displayed together with valid update errors impacting 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 have an effect on the update will not get propagated further. Thus improving the user experience. However, they will still be shown in the logs to help with more precise debugging.

This pull request references https://issues.redhat.com/browse/OCPBUGS-15200

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.

Davoska · 2024-06-03T14:11:13Z

/jira refresh

openshift-ci-robot · 2024-06-03T14:11:21Z

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

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.17.0) matches configured target version for branch (4.17.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jiajliu

In response to this:

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

Davoska · 2024-06-03T14:13:26Z

I would like to test this on a live cluster (edit: and fix the failing CI). Thus, I am putting this PR on hold for the time being.

/hold

Davoska · 2024-06-03T14:15:32Z

/uncc LalatenduMohanty
/cc @wking

petr-muller · 2024-06-03T15:12:40Z

Approach SGTM 👍

petr-muller · 2024-06-03T15:24:56Z

I have not looked at the code closely yet but one piece to check for possible interaction is #1041 which renders all reconciliation problems (including the UpdateEffectNone ones) for external consumption, as a pseudo-api.

If possible we'd like to keep UpdateEffectNone errors there, if possible. I think filtering them out on the producer side would hide them from ReconciliationIssues?

Davoska · 2024-06-04T13:25:29Z

/hold

I am re-working the PR.

openshift-ci-robot · 2024-06-11T19:11:24Z

@Davoska: This pull request references Jira Issue OCPBUGS-15200, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.17.0) matches configured target version for branch (4.17.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @dis016

In response to this:

TBD

This pull request references https://issues.redhat.com/browse/OCPBUGS-15200

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.

pkg/cvo/cvo_scenarios_test.go

pkg/cvo/status.go

petr-muller

approach lgtm, some code readability nits + what Trevor says ;)

pkg/cvo/status.go

petr-muller · 2024-07-29T12:03:41Z

All jobs have

 Terminal error: nonretryable error: no build client found for cluster "build01".

/test all

pkg/cvo/cvo_scenarios_test.go

Davoska · 2024-08-05T15:49:26Z

/unhold

However, I would initiate the QE pre-merge testing after the PR is approved and lgtm-ed. The code touches a few sensitive places, and there is a possibility for more new changes after code reviews.

pkg/cvo/status.go

hongkailiu

ONLY a couple of NITs.

pkg/cvo/status.go

pkg/cvo/status_test.go

pkg/cvo/status.go

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

Davoska · 2024-08-09T16:52:29Z

/retest

Davoska · 2024-08-11T19:21:16Z

/retest

Davoska · 2024-08-12T14:16:53Z

/retest

hongkailiu · 2024-08-12T17:53:22Z

/lgtm

/hold
In case you want others to take a look.

openshift-ci · 2024-08-12T17:54:53Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Davoska, hongkailiu

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~~ [Davoska]

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

Davoska · 2024-08-14T11:24:12Z

/override ci/prow/e2e-hypershift

The PR doesn't affect functionally the CVO. The PR only modifies the Failing condition inside a ClusterVersion resource.
Also, the failing runs are not consistent. TestNodePoolReplaceUpgrade timed out, TestNTOMachineConfigAppliedInPlace desired number of nodes a pool should maintain is not equal to actual, two teardowns [1, 2] did not complete in time. The job seems to be flaky currently, and the failed runs should not be caused by the PR.

/override ci/prow/e2e-agnostic-ovn-upgrade-out-of-change
Same reasoning as above. The failed runs should not be caused by the PR changes, and the job seems to be flaky currently as well. [bz-etcd][invariant] alert/etcdHighCommitDurations should not be at or above, [sig-network-edge] disruption/service-load-balancer-with-pdb connection/new should be available throughout the test are somewhat consistent across the last 4 runs; however not explainable by the PR changes.

openshift-ci · 2024-08-14T11:24:33Z

@Davoska: Overrode contexts on behalf of Davoska: ci/prow/e2e-agnostic-ovn-upgrade-out-of-change, ci/prow/e2e-hypershift

In response to this:

/override ci/prow/e2e-hypershift

The PR doesn't affect functionally the CVO. The PR only modifies the Failing condition inside a ClusterVersion resource.
Also, the failing runs are not consistent. TestNodePoolReplaceUpgrade timed out, TestNTOMachineConfigAppliedInPlace desired number of nodes a pool should maintain is not equal to actual, two teardowns [1, 2] did not complete in time. The job seems to be flaky currently, and the failed runs should not be caused by the PR.

/override ci/prow/e2e-agnostic-ovn-upgrade-out-of-change
Same reasoning as above. The failed runs should not be caused by the PR changes, and the job seems to be flaky currently as well. [bz-etcd][invariant] alert/etcdHighCommitDurations should not be at or above, [sig-network-edge] disruption/service-load-balancer-with-pdb connection/new should be available throughout the test are somewhat consistent across the last 4 runs; however not explainable by the PR changes.

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.

openshift-ci · 2024-08-14T11:24:38Z

@Davoska: 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.

Davoska · 2024-08-14T11:29:41Z

/unhold
The pull request is ready for pre-merge testing, @dis016 👍

Testing the PR might be a little bit interesting/tricky.

The PR's goal is to remove unimportant messages from the Failing condition that has the reason MultipleErrors while in an update.

More precisely, the PR should remove Cluster operator <NAME> is updating versions, and Cluster operators <NAMES> are updating versions' messages from the Failing condition during an update, as of the moment.

These messages show up in the Failing condition only when another more serious issue is present as well.

This means an update must be in progress, the CVO must have issues progressing with an update, and some cluster operators are also updating at the moment.

Launching an update may be not enough to catch the new changes, as the update might go without problems. In my previous testing, I have permanently set a cluster operator to be always degraded. The CVO eventually got to the run-level of the said operator and declared an error Cluster operator authentication is degraded while also the CVO was waiting for other COs to update their versions. Originally, the CVO would set the Failing condition to MultipleErrors and would show all information. With this PR, the CVO only set the Failing condition to show the degraded operator. You might need to do something similar. Make an operator degraded as well? Break the cluster in a different manner? Update to a version with an invalid release manifest? Feel free to reach out 🙌

dis016 · 2024-08-23T07:35:13Z

Test Scenario: Make a CO(authentication) degraded.

Original Failure: Reason: MultipleErrors; Message: Multiple issues: CO A is degraded, CO B is updating versions

Install a 4.17 cluster and degrade the Cluster operator authentication.

NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.17.0-0.test-2024-08-22-131833-ci-ln-ntyc4tb-latest   True        False         99m     Cluster version is 4.17.0-0.test-2024-08-22-131833-ci-ln-ntyc4tb-latest
%
% 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 
 % 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
 %  oc get co authentication
NAME             VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
authentication   4.17.0-0.test-2024-08-22-131833-ci-ln-ntyc4tb-latest   True        False         True       103m    OAuthServerConfigObservationDegraded: failed to apply IDP oidcidp config: dial tcp: lookup www.idp-issuer.example.com on 172.30.0.10:53: no such host
%

Trigger Upgrade to version which doesn't contain the PR Changes

% oc adm upgrade --to-image=registry.ci.openshift.org/ocp/release@sha256:b8105494ce61dc1f5ba68f173c78adfb834ff70c66e7399b9ae401021517f27f  --allow-explicit-upgrade --force
warning: The requested upgrade image is not one of the available updates.  You have used --allow-explicit-upgrade to the update to proceed anyway
warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
Updating to release image registry.ci.openshift.org/ocp/release@sha256:b8105494ce61dc1f5ba68f173c78adfb834ff70c66e7399b9ae401021517f27f
% 
% oc adm upgrade 
Error while reconciling 4.17.0-0.test-2024-08-22-131833-ci-ln-ntyc4tb-latest: the cluster operator authentication is degraded

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

%  oc adm upgrade status 
info: An upgrade is in progress. Working towards 4.17.0-0.nightly-2024-08-19-165854: 6 of 900 done (0% complete)

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

dinesh@Dineshs-MacBook-Pro Downloads %

with error upgrade is proceeded and CVO is throwing the error


% 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.nightly-2024-08-19-165854: 110 of 900 done (12% complete), waiting on etcd, kube-apiserver

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

{
  "lastTransitionTime": "2024-08-22T15:41:42Z",
  "status": "False",
  "type": "Failing"
}
...
...
info: An upgrade is in progress. Unable to apply 4.17.0-0.nightly-2024-08-19-165854: an unknown error has occurred: MultipleErrors

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

{
  "lastTransitionTime": "2024-08-22T16:06:12Z",
  "message": "Multiple errors are preventing progress:\n* Cluster operator authentication is degraded\n* Cluster operators cluster-autoscaler, console, marketplace, monitoring, node-tuning, openshift-apiserver, openshift-controller-manager are updating versions",
  **"reason": "MultipleErrors",**
  "status": "True",
  "type": "Failing"
}

Expected/New Failure: Reason: ClusterOperatorDegraded; Message: CO A is degraded
Install a 4.17 Cluster and degrade the CO authentication

% oc get clusterversion 
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.17.0-0.nightly-2024-08-18-131731   True        False         22m     Cluster version is 4.17.0-0.nightly-2024-08-18-131731
%
% 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 
% 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
% 
% oc get co authentication 
NAME             VERSION                              AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
authentication   4.17.0-0.nightly-2024-08-18-131731   True        False         True       28m     OAuthServerConfigObservationDegraded: failed to apply IDP oidcidp config: dial tcp: lookup www.idp-issuer.example.com on 172.30.0.10:53: no such host
%

Trigger an upgrade to version which contains the PR changes

% oc adm upgrade --to-image=registry.build05.ci.openshift.org/ci-ln-r73233t/releasesha256:6005ad60e79b21be48536e8574123d9a5c1b698f79622722edf23aca45884732  --allow-explicit-upgrade --force
warning: Using by-tag pull specs is dangerous, and while we still allow it in combination with --force for backward compatibility, it would be much safer to pass a by-digest pull spec instead
warning: The requested upgrade image is not one of the available updates.  You have used --allow-explicit-upgrade to the update to proceed anyway
warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
Updating to release image registry.build05.ci.openshift.org/ci-ln-r73233t/releasesha256:6005ad60e79b21be48536e8574123d9a5c1b698f79622722edf23aca45884732
% 
% oc adm upgrade status
Error while reconciling 4.17.0-0.nightly-2024-08-18-131731: the cluster operator authentication is degraded

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

%

Upgrade is not triggered and CVO is throwing an error

% while true; do oc adm upgrade; oc get clusterversion version -o json | jq '.status.conditions[] | select (.type=="Failing")' ; sleep 60; done  

Error while reconciling 4.17.0-0.nightly-2024-08-18-131731: the cluster operator authentication is degraded

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

{
  "lastTransitionTime": "2024-08-23T07:12:40Z",
  "message": "Cluster operator authentication is degraded",
  "reason": "ClusterOperatorDegraded",
  "status": "True",
  "type": "Failing"
}
Error while reconciling 4.17.0-0.nightly-2024-08-18-131731: the cluster operator authentication is degraded

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

{
  "lastTransitionTime": "2024-08-23T07:12:40Z",
  "message": "Cluster operator authentication is degraded",
  "reason": "ClusterOperatorDegraded",
  "status": "True",
  "type": "Failing"
}
 %

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 3, 2024

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

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 3, 2024

openshift-ci bot requested a review from jiajliu June 3, 2024 14:11

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 3, 2024

openshift-ci bot requested review from LalatenduMohanty and petr-muller June 3, 2024 14:13

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 3, 2024

openshift-ci bot requested review from wking and removed request for LalatenduMohanty June 3, 2024 14:15

Davoska marked this pull request as draft June 4, 2024 13:25

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 4, 2024

Davoska force-pushed the OCPBUGS-15200-filter-out-update-effect-none-errors branch 2 times, most recently from e11d635 to 8b4d632 Compare June 11, 2024 19:09

openshift-ci bot requested a review from dis016 June 11, 2024 19:11

Davoska changed the title ~~OCPBUGS-15200: Filter out UpdateEffectNone errors from the summarized task graph error~~ OCPBUGS-15200: Filter out shallowly UpdateEffectNone errors from the Failing condition Jun 11, 2024

wking reviewed Jun 11, 2024

View reviewed changes

pkg/cvo/cvo_scenarios_test.go Show resolved Hide resolved

wking reviewed Jun 11, 2024

View reviewed changes

pkg/cvo/status.go Outdated Show resolved Hide resolved

wking reviewed Jun 11, 2024

View reviewed changes

pkg/cvo/status.go Outdated Show resolved Hide resolved

petr-muller reviewed Jun 12, 2024

View reviewed changes

pkg/cvo/status.go Outdated Show resolved Hide resolved

pkg/cvo/status.go Outdated Show resolved Hide resolved

pkg/cvo/status.go Outdated Show resolved Hide resolved

Davoska force-pushed the OCPBUGS-15200-filter-out-update-effect-none-errors branch 2 times, most recently from 4528f98 to 411f084 Compare July 26, 2024 18:27

Davoska changed the title ~~OCPBUGS-15200: WIP: Filter out shallowly UpdateEffectNone errors from a MultipleErrors message in the Failing condition~~ OCPBUGS-15200: Filter out shallowly UpdateEffectNone errors from a MultipleErrors message in the Failing condition Jul 26, 2024

Davoska requested a review from petr-muller July 26, 2024 20:29

petr-muller reviewed Jul 29, 2024

View reviewed changes

pkg/cvo/cvo_scenarios_test.go Outdated Show resolved Hide resolved

Davoska force-pushed the OCPBUGS-15200-filter-out-update-effect-none-errors branch 2 times, most recently from dfc9b34 to 775a7d8 Compare August 5, 2024 15:44

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 5, 2024

hongkailiu reviewed Aug 6, 2024

View reviewed changes

pkg/cvo/status.go Outdated Show resolved Hide resolved

pkg/cvo/status.go Outdated Show resolved Hide resolved

hongkailiu reviewed Aug 7, 2024

View reviewed changes

pkg/cvo/status.go Outdated Show resolved Hide resolved

pkg/cvo/status.go Outdated Show resolved Hide resolved

pkg/cvo/status_test.go Outdated Show resolved Hide resolved

pkg/cvo/status.go Show resolved Hide resolved

Davoska added 3 commits August 8, 2024 19:47

pkg/cvo/status_test.go: Test setting Failing condition in updateClust…

dc830db

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

Davoska force-pushed the OCPBUGS-15200-filter-out-update-effect-none-errors branch from 90cd133 to 7676d46 Compare August 8, 2024 17:53

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 12, 2024

openshift-ci bot assigned hongkailiu Aug 12, 2024

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 12, 2024

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 14, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

OCPBUGS-15200: Filter out shallowly `UpdateEffectNone` errors from a `MultipleErrors` message in the Failing condition #1050

OCPBUGS-15200: Filter out shallowly `UpdateEffectNone` errors from a `MultipleErrors` message in the Failing condition #1050

Davoska commented Jun 3, 2024 •

edited

Loading

openshift-ci-robot commented Jun 3, 2024

Davoska commented Jun 3, 2024

openshift-ci-robot commented Jun 3, 2024

Davoska commented Jun 3, 2024 •

edited

Loading

Davoska commented Jun 3, 2024

petr-muller commented Jun 3, 2024 •

edited

Loading

petr-muller commented Jun 3, 2024

Davoska commented Jun 4, 2024

openshift-ci-robot commented Jun 11, 2024

petr-muller left a comment

petr-muller commented Jul 29, 2024 •

edited

Loading

Davoska commented Aug 5, 2024 •

edited

Loading

hongkailiu left a comment

Davoska commented Aug 9, 2024

Davoska commented Aug 11, 2024

Davoska commented Aug 12, 2024

hongkailiu commented Aug 12, 2024

openshift-ci bot commented Aug 12, 2024

Davoska commented Aug 14, 2024

openshift-ci bot commented Aug 14, 2024

openshift-ci bot commented Aug 14, 2024

Davoska commented Aug 14, 2024 •

edited

Loading

dis016 commented Aug 23, 2024 •

edited

Loading

OCPBUGS-15200: Filter out shallowly UpdateEffectNone errors from a MultipleErrors message in the Failing condition #1050

Are you sure you want to change the base?

OCPBUGS-15200: Filter out shallowly UpdateEffectNone errors from a MultipleErrors message in the Failing condition #1050

Conversation

Davoska commented Jun 3, 2024 • edited Loading

openshift-ci-robot commented Jun 3, 2024

Davoska commented Jun 3, 2024

openshift-ci-robot commented Jun 3, 2024

Davoska commented Jun 3, 2024 • edited Loading

Davoska commented Jun 3, 2024

petr-muller commented Jun 3, 2024 • edited Loading

petr-muller commented Jun 3, 2024

Davoska commented Jun 4, 2024

openshift-ci-robot commented Jun 11, 2024

petr-muller left a comment

Choose a reason for hiding this comment

petr-muller commented Jul 29, 2024 • edited Loading

Davoska commented Aug 5, 2024 • edited Loading

hongkailiu left a comment

Choose a reason for hiding this comment

Davoska commented Aug 9, 2024

Davoska commented Aug 11, 2024

Davoska commented Aug 12, 2024

hongkailiu commented Aug 12, 2024

openshift-ci bot commented Aug 12, 2024

Davoska commented Aug 14, 2024

openshift-ci bot commented Aug 14, 2024

openshift-ci bot commented Aug 14, 2024

Davoska commented Aug 14, 2024 • edited Loading

dis016 commented Aug 23, 2024 • edited Loading

OCPBUGS-15200: Filter out shallowly `UpdateEffectNone` errors from a `MultipleErrors` message in the Failing condition #1050

OCPBUGS-15200: Filter out shallowly `UpdateEffectNone` errors from a `MultipleErrors` message in the Failing condition #1050

Davoska commented Jun 3, 2024 •

edited

Loading

Davoska commented Jun 3, 2024 •

edited

Loading

petr-muller commented Jun 3, 2024 •

edited

Loading

petr-muller commented Jul 29, 2024 •

edited

Loading

Davoska commented Aug 5, 2024 •

edited

Loading

Davoska commented Aug 14, 2024 •

edited

Loading

dis016 commented Aug 23, 2024 •

edited

Loading