Description of problem (please be detailed as possible and provide log snippests): Version of all relevant components (if applicable): Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Description: On IPI deployment while upgrading to 4.10, Noobaa health does not get into OK state. This issue prevents testing upgrade scenarios on the Azure platform. This would be an execution that we saw the problem: https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/2274/consoleFull Also here is the must-gather result to see the status of health, http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-052zi3c33-uo/j-052zi3c33-uo_20211115T142831/logs/deployment_1636986797/ocs_must_gather/quay-io-rhceph-dev-ocs-must-gather-sha256-2cfd1466b584aba7c3d94a6d2397267443416fe7db8a7fc132e4137ed640ca8f/noobaa/logs/openshift-storage/ Please let me know if any detail is missed so I can add further information.
*** Bug 2023768 has been marked as a duplicate of this bug. ***
Tested and verified by automatic job. OCP: 4.9.0-0.nightly-2021-11-18-000209 ODF version: ocs-registry:4.9.0-241.ci >> VERIFIED