Bug 2172089
| Summary: | [Tracker for Ceph BZ 2174461] rook-ceph-nfs pod is stuck at status 'CreateContainerError' after enabling NFS in ODF 4.13 | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Amrita Mahapatra <ammahapa> | |
| Component: | ceph | Assignee: | Tamil <tmuthami> | |
| ceph sub component: | Ceph-MGR | QA Contact: | Amrita Mahapatra <ammahapa> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | high | CC: | bniver, branto, brgardne, dkhandel, ebenahar, gdeschner, mmuench, muagarwa, nberry, ndevos, ocs-bugs, odf-bz-bot, rar, sostapov, sprabhu, tmuthami | |
| Version: | 4.13 | Keywords: | TestBlocker | |
| Target Milestone: | --- | |||
| Target Release: | ODF 4.13.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2174461 (view as bug list) | Environment: | ||
| Last Closed: | 2023-06-21 15:24:01 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 2174461 | |||
| Bug Blocks: | ||||
I see a message from the dashboard screenshot "dbus-daemon not found in $PATH". I think the package that provides dbus-daemon must have been removed from our image. registry.access.redhat.com/ubi8/ubi:8.7 has the `dbus-daemon` app. I think the dbus package should be set as a requirement for the NFS Ganesha RPM as well. Moving this to the build component for them to check that out. The rhceph image(RHEL9 based) `6-105` is used to build the 4.13 rook image. I can see the `dbus` package is listed in the package list for this image. https://quay.io/repository/rhceph-dev/rhceph/manifest/sha256:dfeceae86b14ab0c349ead487cbae17deebbed579021d5fbdf7b6df9d43e9623?tab=packages The dbus packae is available in the package but there is no dbus-daemon package installed. @Blaine Do we need the dbus-daemon in rook-ceph image only or both rook-ceph as well as rhceph container? We need to re-assign the bz based on that. @branto the rhceph container will need dbus-daemon. Thanks :) I will go ahead and create a rhceph BZ to track that. @branto, I created https://bugzilla.redhat.com/show_bug.cgi?id=2172089 to track getting the package into rhceph. I believe that should be rhcs 6.0. If some part of that doesn't sound right, I'd appreciate if you'd update it. Looks good to me, thanks for creating the bz! Fix should be available with RHCS 6.1, its already merged upstream. 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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix 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/RHBA-2023:3742 |
Description of problem (please be detailed as possible and provide log snippests): rook-ceph-nfs pod is stuck at status 'CreateContainerError' after enabling nfs feature, $ oc get cephnfs NAME AGE ocs-storagecluster-cephnfs 21m $ oc get pods|grep rook-ceph-nfs rook-ceph-nfs-ocs-storagecluster-cephnfs-a-dd598659f-bb8xn 1/2 CreateContainerError 0 19m The error msg is, Error: container create failed: time="2023-02-23T08:54:29Z" level=error msg="runc create failed: unable to start container process: exec: \"dbus-daemon\": executable file not found in $PATH" Version of all relevant components (if applicable): OCP version: 4.13.0-0.nightly-2023-02-23-000625 OCS version: 4.13.0-86 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? yes 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? yes If this is a regression, please provide more details to justify this: NA Steps to Reproduce: 1. Enable nfs from UI by slecting the checkbox from storagesystem creation page or from CLI by patch request, $ oc patch -n openshift-storage storageclusters.ocs.openshift.io ocs-storagecluster --patch '{"spec": {"nfs":{"enable": true}}}' --type merge 2. Check cephnfs got created $ oc get cephnfs 3. Check the status for rook-ceph-nfs pod $ oc get pods|grep rook-ceph-nfs Actual results: rook-ceph-nfs pod is stuck at status 'CreateContainerError' after enabling nfs feature. Expected results: rook-ceph-nfs pod should be running after enabling nfs feature. Additional info: Have attached rook-ceph-nfs pod log.