test: [sig-instrumentation] Prometheus metrics should be available after an upgrade is failing frequently in CI, see search results: https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-instrumentation%5C%5D+Prometheus+metrics+should+be+available+after+an+upgrade This test is panicking on metal-ipi upgrades: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.9-upgrade-from-stable-4.8-e2e-metal-ipi-upgrade/1410386679042150400 However there's no trace to know exactly why, Ginkgo offers a suggestion to get a traceback. Test logs: Your test failed. Ginkgo panics to prevent subsequent assertions from running. Normally Ginkgo rescues this panic so you shouldn't see it. But, if you make an assertion in a goroutine, Ginkgo can't capture the panic. To circumvent this, you should call defer GinkgoRecover() at the top of the goroutine that caused this panic. Jul 1 01:55:55.662: INFO: "[sig-instrumentation] Prometheus metrics should be available after an upgrade": panic: Your test failed. Ginkgo panics to prevent subsequent assertions from running. Normally Ginkgo rescues this panic so you shouldn't see it. But, if you make an assertion in a goroutine, Ginkgo can't capture the panic. To circumvent this, you should call defer GinkgoRecover()
Could you have a look at this? Thanks!
Taking a look
Looking at the CI logs, the test is only failing on metal-ipi upgrades. This test suite does not run on openshift/origin PRs and cannot be run through cluster bot either. Is there any other way to troubleshoot the problem? Otherwise we might need to completely disable the test.
LGTM, the case will be skipped in baremetal cluster if it don't have storage class
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:3759