Details
-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
None
-
4.13.z
-
Important
-
No
-
Sprint 248, Sprint 249, Sprint 250
-
3
-
False
-
Description
Description of problem:
CO/DNS stuck in Progressing when upgrade from 4.13 to 4.14, it occurred in one upgrade CI job of "4.14-upgrade-from-eus-4.12-nutanix-ipi-proxy-fips", details see: https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-4.14-upgrade-from-eus-4.12-nutanix-ipi-proxy-fips-f14/1746559435393732608#1:build-log.txt%3A40
version 4.13.0-0.nightly-2024-01-13-200411 True True 119m Working towards 4.14.0-0.nightly-2024-01-14-085502: 711 of 860 done (82% complete), waiting on dns
Version-Release number of selected component (if applicable):
upgrade from: 4.12.47 -> 4.13.0-0.nightly-2024-01-13-200411 -> 4.14.0-0.nightly-2024-01-14-085502
How reproducible:
once in CI
Steps to Reproduce:
1. see upgrade CI job
2.
3.
Actual results:
co/dns stuck in progressing status, upgrade failed.
Expected results:
upgrade succeeds
Additional info:
must-gather: https://gcsweb-qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-4.14-upgrade-from-eus-4.12-nutanix-ipi-proxy-fips-f14/1746559435393732608/artifacts/nutanix-ipi-proxy-fips-f14/gather-must-gather/artifacts/