e2e: verify cluster operators sync status#22092
e2e: verify cluster operators sync status#22092derekwaynecarr wants to merge 1 commit intoopenshift:masterfrom
Conversation
openshift-ci-robot
added
the
size/L
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekwaynecarr The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
w/ 2m wait, we get failures with the following: kube-scheduler, monitoring, image-registry, cluster-storage-operator, network, and dns. will bump to 5m wait, we should think about heartbeat requirements. the operator-lifecycle-manager component never appears to report cvo out again. |
|
|
||
| // gate on all clusteroperators being ready | ||
| available := make(map[string]struct{}) | ||
| g.By(fmt.Sprintf("waiting for all cluster operators to be stable at the same time")) |
There was a problem hiding this comment.
Should there be a helper function for this rather than inlining it twice here and once in #22058?
|
/retest finding the latest victims for getting a bz. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci-robot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci-robot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. DetailsIn response to this:
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. |
derekwaynecarr
force-pushed
the
delete-cluster-operators
branch
from
17c2bb6 to
77dfe25
Compare
derekwaynecarr
removed
the
lifecycle/rotten
|
@derekwaynecarr: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci-robot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci-robot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. DetailsIn response to this:
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. |
4 participants
The test attempts to verify that all SLOs frequently report status.
It deletes all existing ClusterOperator resources for a stable cluster, and waits to ensure that all SLOs report a reconstructed status after enough time. Test is intended to shake out component operator failures that only report status once rather than frequently.