Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem (please be detailed as possible and provide log snippests): During OCS 4.4 RC4 deployment the rook-ceph-osd pods end up in a CrashLoopBackOff state which causes the deployment to fail. Jenkins job where we experienced this: https://ocs4-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/qe-deploy-ocs-cluster/7315//console Mail thread with further details: http://post-office.corp.redhat.com/archives/rhocs-eng/2020-May/msg00048.html Version of all relevant components (if applicable): ocs-olm-operator:4.4.0-418.ci OCP 4.4 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes, we currently cannot deploy OCS 4.4 RC4. Is there any workaround available to the best of your knowledge? No 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? Untested If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Deploy OCP 4.4 2. Deploy OCS 4.4 RC4 (4.4.0-418.ci) Actual results: OCS fails to deploy properly due to rook-ceph-osd pods being in CrashLoopBackOff state Expected results: rook-ceph-osd pods reach Running state and we continue on to a successful OCS deployment Additional info: must-gather logs: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/jnk-au3r33-t1/jnk-au3r33-t1_20200506T131058/logs/failed_testcase_ocs_logs_1588771348/deployment_ocs_logs/
Reassigning while Seb is on holiday to get the RC builds unblocked...
Upstream PR is opened, still testing for downstream on an AWS cluster...
The change has been tested. I validated that I hit the issue on my aws cluster before applying the fix. After applying the fix, the OSDs started successfully. The fix is merged downstream and ready for the next RC build. https://github.com/openshift/rook/pull/52
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, 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/RHBA-2020:2393