Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem (please be detailed as possible and provide log snippests): ========================================================================= RGW pod is not deployed with latest OCS 4.7.0-249.ci build. Rook logs show this snip: 2021-02-02 19:08:22.143697 I | ceph-object-controller: object store "ocs-storagecluster-cephobjectstore" deployment "rook-ceph-rgw-ocs-storagecluster-cephobjectstore-a" started 2021-02-02 19:08:22.157689 E | ceph-object-controller: failed to reconcile failed to create object store deployments: failed to create object store "ocs-storagecluster-cephobjectstore": failed to start rgw pods: failed to create rgw deployment: Deployment.apps "rook-ceph-rgw-ocs-storagecluster-cephobjectstore-a" is invalid: spec.template.spec.containers[1].name: Invalid value: "rgwceph-client-rook-ceph-rgw-ocs-storagecluster-cephobjectstore-a-log-collector": must be no more than 63 characters Some background: --------------------- From builds >4.7.0-241.ci and below 4.7.0-248.ci, OSD pod creations were failing due to Bug 1922108. With new build 4.7.0-249.ci, though OSD pods are deployed (fixed bug 1922108), RGW pod deployment is now failing. P.S: RGW pods were deployed successfully till 4.7.0-241.ci build Version of all relevant components (if applicable): ======================================================= OCP = 4.7.0-0.nightly-2021-01-31-031653 OCS = ocs-operator.v4.7.0-249.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? =========================================================================== Yes. In the absence of RGW, even Noobaa backingstore creation failed. 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)? ======================================================== 3 Can this issue reproducible? ================================= Tested once Can this issue reproduce from the UI? ========================================= OCS installed from UI If this is a regression, please provide more details to justify this: ======================================================================= Yes. RGW pods were created successfully for the last accepted build - 4.7.0-241.ci Steps to Reproduce: ======================== 1. Create OCP 4.7 cluster 2. Install OCS 4.7.0-249.ci using UI 3. Check for PODS, Noobaa backingstores Actual results: ================== 1. RGW pod is not created due to exceeded length of character in the name of deployment.apps 2. Due to absence of RGW, noobaa deployment is also affected as default Backingstore is not created. Expected results: ==================== RGW pod should be deployed. Additional info: ====================== In build 4.7.0-249.ci ------------------------- $ oc get cephobjectstoreuser NAME AGE noobaa-ceph-objectstore-user 22m ocs-storagecluster-cephobjectstoreuser 26m [nberry@localhost ocs-249]$ oc get cephobjectstoreuser NAME AGE noobaa-ceph-objectstore-user 24m ocs-storagecluster-cephobjectstoreuser 28m $ oc get all|grep rgw service/rook-ceph-rgw-ocs-storagecluster-cephobjectstore ClusterIP 172.30.125.160 <none> 80/TCP 33m [nberry@localhost ocs-249]$ In previous build (4.7.0-241.ci) with successful RGW deployment: ------------------------------------------------------------- $ oc get all |grep rgw pod/rook-ceph-rgw-ocs-storagecluster-cephobjectstore-a-7796585h2wxr 1/1 Running 0 12h service/rook-ceph-rgw-ocs-storagecluster-cephobjectstore ClusterIP 172.30.174.119 <none> 80/TCP 12h deployment.apps/rook-ceph-rgw-ocs-storagecluster-cephobjectstore-a 1/1 1 1 12h replicaset.apps/rook-ceph-rgw-ocs-storagecluster-cephobjectstore-a-77965857bd 1 1 1 12h ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Let's see if we can get this in the next 4.7 build...
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