Similar to BZ 1915698 Description of problem (please be detailed as possible and provide log snippests): On Azure platform after OCS upgrade from 4.6 to OCS 4.7, I see all noobaa pods are not in Running state noobaa-db-0 1/1 Running 0 14h noobaa-db-pg-0 0/1 Init:0/1 128 14h noobaa-operator-9995644ff-b2zn7 1/1 Running 0 14h Version of all relevant components (if applicable): OCP: 4.7.0-fc.4 OCS: ocs-operator.v4.7.0-241.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes, Blocking the upgrade automation on [azure platform] Is there any workaround available to the best of your knowledge? No, I am not aware of it for now. Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 2 Can this issue reproducible? yes. reproducibility till time 1/1 Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1.Install OCP 4.6 and OCS 4.6 2.Upgrade OCP to 4.7 (Auto) 3.verify OCP upgraded successfully 4.Upgrade OCS to 4.7 Actual results: No noobaa-core-0 pod exists after the upgrade Expected results: noobaa core pod running. Additional info: Job: https://ocs4-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/qe-deploy-ocs-cluster/16799/console Logs: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/sgatfane-2801/sgatfane-2801_20210128T053058/logs/failed_testcase_ocs_logs_1611852615/test_upgrade_ocs_logs/ http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/sgatfane-2801/sgatfane-2801_20210128T053058/logs/failed_testcase_ocs_logs_1611849423/test_upgrade_logging_ocs_logs/ocs_must_gather/ http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/sgatfane-2801/sgatfane-2801_20210128T053058/logs/failed_testcase_ocs_logs_1611849423/test_upgrade_logging_ocs_logs/noobaa_db_dump/ http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/sgatfane-2801/sgatfane-2801_20210128T053058/logs/failed_testcase_ocs_logs_1611852615/test_check_mon_pdb_post_upgrade_ocs_logs/
Closing this bug as it got created accidentally due to network delay. Same as https://bugzilla.redhat.com/show_bug.cgi?id=1922113 *** This bug has been marked as a duplicate of bug 1922113 ***