-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.15
-
No
-
False
-
Prow Job Link: periodic-ci-openshift-jenkins-release-4.15-jenkins-ocp4.15-lp-interop-jenkins-interop-aws #1750999500643635200
Build ID: 1750999500643635200
Classification: Test Failure
Failed Step: jenkins-smoke-tests
Here are up to 10 related bugs produced by the step jenkins-smoke-tests and failed with failure type test_failure:
| Bug | Date Created | Assignee |
|---|---|---|
| OCPBUGS-28378 | 2024-01-26 | Corey Daley |
| OCPBUGS-22951 | 2023-11-06 | Corey Daley |
| OCPBUGS-15902 | 2023-07-06 | Corey Daley |
| LPTOCPCI-424 | 2023-07-06 | None |
This bug was filed using firewatch in OpenShift CI
[OCPBUGS-28385] Failure in periodic-ci-openshift-jenkins-release-4.15-jenkins-ocp4.15-lp-interop-jenkins-interop-aws - 01-26-2024
JOB RECENTLY PASSED
This job has been run successfully since this bug was filed. Please verify that this bug is still relevant and close it if needed.
Passing Run Link: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-jenkins-release-4.15-jenkins-ocp4.15-lp-interop-jenkins-interop-aws/1753286435630223360
Passing Run Build ID: 1753286435630223360
Please add the "ignore-passing-notification" tag to this bug to avoid future passing job notifications.
This comment was created using firewatch in OpenShift CI.
Corey Daley
added a comment - The one that passed was run manually, can you try to kick it off manually again and see what happens?
When I launch a cluster with the same nightly that you are using and run the interop tests using "make smoke" on the release-4.15 branch of openshift/jenkins, they pass without issue. Is it possible that the interop test is using a cached test image with the old code from before I fixed it recently?
Corey Daley
added a comment - The one that passed was run manually, can you try to kick it off manually again and see what happens?
When I launch a cluster with the same nightly that you are using and run the interop tests using "make smoke" on the release-4.15 branch of openshift/jenkins, they pass without issue. Is it possible that the interop test is using a cached test image with the old code from before I fixed it recently? Hi, cdaley - We did see one passing OCP 4.15 test run 1750977982932979712 on 26-Jan-2024. However, subsequent test runs from this week (1752244858552061952) failed on three (3) tests:
- jenkins-ephemeral.Deploy Jenkins on openshift using template based install: Create jenkins using ephemeral template : JKNS-02-TC01 open stdout
- : Run multi-stage test jenkins-interop-aws - jenkins-interop-aws-firewatch-report-issues container test
- : Run multi-stage test post phase
Could you kindly investigate the failures, and provide an estimate on a fix? Thank you! cc: dlane@redhat.com
A duplicate failure was identified in a recent run of the periodic-ci-openshift-jenkins-release-4.15-jenkins-ocp4.15-lp-interop-jenkins-interop-aws job:
Link: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-jenkins-release-4.15-jenkins-ocp4.15-lp-interop-jenkins-interop-aws/1752244858552061952
Build ID: 1752244858552061952
Classification: Test Failure
Failed Step: jenkins-smoke-tests
Please see the link provided above to determine if this is the same issue. If it is not, please manually file a new bug for this issue.
This comment was created using firewatch in OpenShift CI
After discussion with cdaley , we determined that the single "pods not found" test failure was not attributed to Jenkins. which does not use an operator. Latest Prow job passed, so closing ticket.