Closed apoorvajagtap closed 1 week ago
@apoorvajagtap: This pull request references Jira Issue OCPBUGS-32293, 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.
/assign @adambkaplan
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: adambkaplan, apoorvajagtap, sayan-biswas
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest-required
Remaining retests: 0 against base HEAD 886b7ae2ff74fceb4dbc8675dd01882e1b294632 and 2 for PR HEAD 809e832a14e2b63b808753dd30d0f2bcdf503d78 in total
Job Failure Risk Analysis for sha: 809e832a14e2b63b808753dd30d0f2bcdf503d78
Job Name | Failure Risk |
---|---|
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6 | IncompleteTests Tests for this run (18) are below the historical average (741): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems) |
New changes are detected. LGTM label has been removed.
@adambkaplan While looking through the test logs, I realized that it creates deployment (template changes introduced with 4.15) & the test waits for deploymentConfig to be ready. Instead of skipping, I have replaced the wait function, and I hope this will fix it. PTAL :)
:thinking: Now I'm wondering why it took us this long to catch the change...
/retest
@apoorvajagtap: 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-serial | ba2a8f06e34c88f55e547b21fe2827b9a8f2e224 | link | false | /test e2e-aws-ovn-single-node-serial |
ci/prow/e2e-gcp-ovn-builds | ba2a8f06e34c88f55e547b21fe2827b9a8f2e224 | link | true | /test e2e-gcp-ovn-builds |
ci/prow/e2e-aws-ovn-single-node-upgrade | ba2a8f06e34c88f55e547b21fe2827b9a8f2e224 | link | false | /test e2e-aws-ovn-single-node-upgrade |
Full PR test history. Your PR dashboard.
Job Failure Risk Analysis for sha: ba2a8f06e34c88f55e547b21fe2827b9a8f2e224
Job Name | Failure Risk |
---|---|
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial | Low [sig-arch] events should not repeat pathologically for ns/openshift-etcd-operator This test has passed 49.30% of 71 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days. |
Found the culprit in https://github.com/openshift/cluster-samples-operator/pull/540, so yes, aside from that wait, you need to update that run as I mentioned above.
Also, given we have those two extra places which don't seem to be in-sync with what we have in samples, I'd suggest to sync them as well. To make them all consistent.
/approve cancel Please ping me directly on slack once all of the above is fixed, I don't want to have a half baked solution.
Also DumpApplicationPodLogs
works for DCs only, so that needs fixing as well.
Reverting changes to cluster-samples-operator in https://github.com/openshift/cluster-samples-operator/pull/542
/close
Replacing with https://github.com/openshift/origin/pull/28732
@adambkaplan: Closed this PR.
@apoorvajagtap: This pull request references Jira Issue OCPBUGS-32293. The bug has been updated to no longer refer to the pull request using the external bug tracker.
Failing Jenkins Pipeline test blocks multiple PRs from merging. As agreed, skipping these tests temporarily.