Description of problem (please be detailed as possible and provide log snippests): After upgrade from OCS 4.6 to OCS 4.7 I see only those noobaa pods: noobaa-db-pg-0 1/1 Running 0 15h noobaa-endpoint-689786fc49-vwghs 1/1 Running 0 15h noobaa-operator-8c5d75f7c-dsth2 1/1 Running 0 15h noobaa-upgrade-job-4fhw5 0/1 Completed 0 15h But we were used to look in automation for 3 pods which have app=noobaa label, but this time only 2 pods have it and automation is failing. Version of all relevant components (if applicable): OCS: 4.7.0-228.ci OCP: 4.6.0-0.nightly-2021-01-12-112514 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 Is there any workaround available to the best of your knowledge? No I am aware of Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Install OCS 4.6 2. Upgrade to OCS 4.7 3. Actual results: No noobaa-core-0 pod exists after upgarde Expected results: Have noobaa core pod running as we were used to if nothing changed in the noobaa and this pod doesn't exist anymore. Additional info: Job: https://ocs4-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/qe-deploy-ocs-cluster/16271//console Must gather logs: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j015vu1cs33-uan/j015vu1cs33-uan_20210112T154141/logs/failed_testcase_ocs_logs_1610470510/test_upgrade_ocs_logs/ Execution on AWS: https://ocs4-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/qe-deploy-ocs-cluster/16271/ http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j002ai3c33-uan/j002ai3c33-uan_20210111T103944/logs/failed_testcase_ocs_logs_1610365320/test_check_mon_pdb_post_upgrade_ocs_logs/
verified with build: 4.7.0-231.ci oc commands output: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j072ai3c33-ua/j072ai3c33-ua_20210119T082836/logs/testcases_1611048461/ocs_must_gather/quay-io-rhceph-dev-ocs-must-gather-sha256-40727dd07d59d2e95cbc79026cec35385fd9f23691fce3933f6c0087061b7ae6/namespaces/openshift-storage/oc_output/ build: https://ocs4-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/qe-deploy-ocs-cluster/16469/
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: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement 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:2041