Description of problem:

OCP version : 4.13.23

The customer is facing issue with umask. Previously they the same issue with 4.10 .

 It fixed till 4.13.0 https://issues.redhat.com/browse/OCPBUGS-13280 . The customer is again facing the same issue in cluster 4.13.23. They want to know why this occuring.

As per this Jira customer updated their ROCKS from V4.11.xx to V4.13.23 last October and found the same issue reoccurred.

sh-4.4# ps lp $(grep -l "Umask:[[:space:]]0000" /proc/[0-9]*/status | cut -f3 -d/) | grep -v "]$"

[2024-02-05 09:08:51.391] 4     0   8257      1  20   0 2885224 194916 -    Ssl  ?        1805:37 /usr/bin/crio

cat status  |grep -i umask
Umask:    0000

How reproducible:

Steps to Reproduce:

    1.
    2.
    3.
    

Actual results:

    crio - umask value set to 0000

Expected results:

    crio - umask value should be 0022 

Additional info: