Bug 1790825: fix test flake in olm tests #24436
Conversation
openshift-ci-robot
added
the
bugzilla/valid-bug
|
@ecordell: This pull request references Bugzilla bug 1790825, 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. In 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. |
openshift-ci-robot
added
the
size/S
ecordell
force-pushed
the
fix-olm-test-flake
branch
from
a3a6130
to
29fba72
Compare
|
/retest |
1 similar comment
|
/retest |
|
/lgtm |
|
/retest |
3 similar comments
|
/retest |
|
/retest |
|
/retest |
|
@ecordell: This pull request references Bugzilla bug 1790825, which is valid. In 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. |
|
/retest |
1 similar comment
|
/retest |
ecordell
force-pushed
the
fix-olm-test-flake
branch
from
29fba72
to
bff9d7a
Compare
ecordell
force-pushed
the
fix-olm-test-flake
branch
from
bff9d7a
to
f61565e
Compare
|
/retest |
ecordell
force-pushed
the
fix-olm-test-flake
branch
from
f61565e
to
c557c3c
Compare
|
/retest |
ecordell
force-pushed
the
fix-olm-test-flake
branch
from
c557c3c
to
8a012ae
Compare
|
/retest |
ecordell
force-pushed
the
fix-olm-test-flake
branch
from
8a012ae
to
a8b7078
Compare
openshift-ci-robot
added
the
needs-rebase
ecordell
force-pushed
the
fix-olm-test-flake
branch
3 times, most recently
from
a3f3859
to
b4517ce
Compare
|
This is killing us in 4.5 CI, causing ~34% of the past day's 4.5 promotion failures. Can we get a review, @bparees? |
ecordell
force-pushed
the
fix-olm-test-flake
branch
from
b4517ce
to
62df410
Compare
|
i've put a comment on it, but more importantly i'd expect the olm team to be driving this through merge, or for it to be esclated to their group lead @shawn-hurley. unfortunately the github review assignees don't mean anything useful in terms of who is best qualified to review/merge changes. |
|
I'm actively working on it as of this afternoon - other changes merged which required changes to this PR. Looks like I missed something. |
ecordell
force-pushed
the
fix-olm-test-flake
branch
from
62df410
to
ec86700
Compare
|
/retest |
|
/retest I see networking and etcd issues in gcp and fips |
|
/retest |
if the operatrgroup is not ready by the time the CSV is created, the CSV may temporarily make the CSV go unhealthy. This emits an alert, which can make the prometheus test ensuring no alerts fail.
ecordell
force-pushed
the
fix-olm-test-flake
branch
from
ec86700
to
c6d02a4
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ecordell, kevinrizza, shawn-hurley 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 |
openshift-ci-robot
added
the
approved
|
/test e2e-aws-fips |
|
/retest this test is no longer causing problems. looks like there are other, unrelated flakes. |
|
/retest |
1 similar comment
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@ecordell: All pull requests linked via external trackers have merged. Bugzilla bug 1790825 has been moved to the MODIFIED state. In 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. |
If the operatrgroup is not ready by the time the CSV is created, the CSV
may temporarily make the CSV go unhealthy. This emits an alert, which
can make the prometheus test ensuring no alerts fail.