origin
origin copied to clipboard
openshift
OCPBUGS-34385: Add exception for openshift-e2e-loki KubePodNotReady
@dgoodwin: This pull request references Jira Issue OCPBUGS-34385, 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:
This should not be able to fail jobs.
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dgoodwin, neisw
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [dgoodwin,neisw]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@dgoodwin: This pull request references Jira Issue OCPBUGS-34385, 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)
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.
@dgoodwin: This pull request references Jira Issue OCPBUGS-34385, 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)
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.
@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/e2e-gcp-ovn
In response to this:
/override ci/prow/e2e-gcp-ovn
Not related and we need this ASAP.
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.
/retest-required
Remaining retests: 0 against base HEAD ff8fc0685363c6fa343e505e415d339b570bbc9f and 2 for PR HEAD da42550be3c9d04433c1ff9cf3726ceca22c1421 in total
@dgoodwin: once the present PR merges, I will cherry-pick it on top of release-4.16 in a new PR and assign it to you.
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.
/retest-required
Remaining retests: 0 against base HEAD 04df82ba3ca34056ae01f359665d3863f14b98de and 1 for PR HEAD da42550be3c9d04433c1ff9cf3726ceca22c1421 in total
/retest-required
Remaining retests: 0 against base HEAD 496aa73b710aec5b7d65f540e89fb20e089f5762 and 0 for PR HEAD da42550be3c9d04433c1ff9cf3726ceca22c1421 in total
/hold
Revision da42550be3c9d04433c1ff9cf3726ceca22c1421 was retested 3 times: holding
/jira refresh
The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.
@openshift-bot: This pull request references Jira Issue OCPBUGS-34385, which is invalid:
- expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.17.0" instead
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.
In response to this:
/jira refresh
The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.
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.
@dgoodwin: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-aws-ovn-single-node-upgrade | da42550be3c9d04433c1ff9cf3726ceca22c1421 | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-gcp-ovn-builds | da42550be3c9d04433c1ff9cf3726ceca22c1421 | link | true | /test e2e-gcp-ovn-builds |
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.
Job Failure Risk Analysis for sha: da42550be3c9d04433c1ff9cf3726ceca22c1421
| Job Name | Failure Risk |
|---|---|
| pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade | High [sig-network-edge] Verify DNS availability during and after upgrade success This test has passed 99.63% of 1900 runs on release 4.17 [Overall] in the last week. --- [sig-arch] events should not repeat pathologically for ns/openshift-kube-apiserver-operator This test has passed 99.94% of 4775 runs on release 4.17 [Overall] in the last week. --- [bz-Node Tuning Operator] clusteroperator/node-tuning should not change condition/Available This test has passed 99.98% of 4786 runs on release 4.17 [Overall] in the last week. |
@dgoodwin: Closed this PR.
In response to this:
/close
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.
@dgoodwin: This pull request references Jira Issue OCPBUGS-34385. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.
In response to this:
This should not be able to fail jobs.
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.