Bug 2027724

Summary: Warning log for rook-ceph-toolbox in ocs-operator log
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: N Balachandran <nibalach>
Component: ocs-operatorAssignee: Malay Kumar parida <mparida>
Status: CLOSED ERRATA QA Contact: Aviad Polak <apolak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.10CC: madam, mparida, muagarwa, ocs-bugs, odf-bz-bot, shan, sostapov, tnielsen
Target Milestone: ---   
Target Release: ODF 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.11.0-89 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-24 13:48:26 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:

Description N Balachandran 2021-11-30 13:54:08 UTC
Description of problem (please be detailed as possible and provide log
snippests):

The following message is seen in the OCS operator log file:

{"level":"info","ts":1638271388.673401,"logger":"KubeAPIWarningLogger","msg":"would violate \"latest\" version of \"baseline\" PodSecurity profile: host namespaces (hostNetwork=true), hostPath volumes (volume \"ceph-config\"), privileged (container \"rook-ceph-tools\" must not set securityContext.privileged=true)"}

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 2 Jose A. Rivera 2022-02-07 16:29:58 UTC
I don't immediately see anything that merits attention, on the surface. Given that this is explicitly labeled as a "warning", and thus far there have been no usability bugs in the Rook-Ceph toolbox, it's nothing severe. We might want to consider squashing/fixing this warning in the future, so I won't close it just yet unless someone weighs in and says this is expected behavior. Moving to ODF 4.11.

Comment 3 Travis Nielsen 2022-05-16 19:48:40 UTC
The toolbox doesn't need to run privileged. Rook's upstream toolbox spec [1] hasn't had the privileged flag since Rook v1.1 [2], which was the basis for OCS 4.3. The security context could be removed entirely from the toolbox pod spec and just use the default context like the upstream pod. The upstream toolbox works fine on openshift with no security context.

[1] https://github.com/rook/rook/blob/master/deploy/examples/toolbox.yaml
[2] https://github.com/rook/rook/blob/release-1.1/cluster/examples/kubernetes/ceph/toolbox.yaml

Comment 10 errata-xmlrpc 2022-08-24 13:48:26 UTC
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 (Important: Red Hat OpenShift Data Foundation 4.11.0 security, enhancement, & bugfix 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-2022:6156