Check for console capability before launching it's disruption monitoring. - #27439
Conversation
dgoodwin
changed the title
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
Testing once with force disabled to ensure we don't get test failures, or disruption data, when the backend doesn't run at all. |
…ing. Adds new utilities to check for enabled and known capabilities. Check also assumes that if the cluster doesn't know about the console capability, it predates 4.12 and thus we should assume to do monitoring for console as it was default then. The test should then see no ingress- backends for console, and not fail.
9ee5ff1 to
ce8e99d
Compare
|
Test confirmed that removing the backend from running entirely does not cause any tests to fail, they operate dynamically on the disruption backends seen in the monitor events, so when one disappears the test continue to work, only looking at those starting with ingress-. PR is now updated with the full fix to skip the backend if we do not know what the Console capability is (4.11), or it is not enabled. |
dgoodwin
changed the title
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
|
/lgtm |
|
/test e2e-aws-ovn-serial |
|
/test e2e-gcp-ovn-upgrade |
|
/assign @stbenjam |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, DennisPeriquet, dgoodwin 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
Bot
added
the
approved
|
/test ci/prow/e2e-aws-ovn-serial |
|
@dgoodwin: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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. |
|
/test e2e-aws-own-serial |
|
@dgoodwin: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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. |
|
/hold Revision ce8e99d was retested 3 times: holding |
openshift-ci
Bot
added
the
do-not-merge/hold
|
/hold cancel aws-ovn-serial build failed to download an rpm. |
openshift-ci
Bot
removed
the
do-not-merge/hold
|
/retest |
|
Mass failures in loki pods, looks like backoff pulling: "message": "Back-off pulling image "registry.redhat.io/openshift4/ose-oauth-proxy:latest"" |
|
@dgoodwin: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
|
/hold Revision ce8e99d was retested 3 times: holding |
openshift-ci
Bot
added
the
do-not-merge/hold
|
/hold cancel |
openshift-ci
Bot
removed
the
do-not-merge/hold
|
Registry issues may have been cleared. |
6 participants
Adds new utilities to check for enabled and known capabilities. Check
also assumes that if the cluster doesn't know about the console
capability, it predates 4.12 and thus we should assume to do monitoring
for console as it was default then.
The test should then see no ingress- backends for console, and not fail.
TRT-573