Bug 2106794 - crio umask sometimes set to 0000
Summary: crio umask sometimes set to 0000
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: 4.10.z
Assignee: Sascha Grunert
QA Contact: Weinan Liu
URL:
Whiteboard:
Depends On: 2106795
Blocks: 2106793
TreeView+ depends on / blocked
 
Reported: 2022-07-13 14:15 UTC by Sascha Grunert
Modified: 2022-08-23 18:29 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2040612
Environment:
Last Closed: 2022-08-23 18:29:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github cri-o cri-o pull 6053 0 None open [release-1.23] BZ#2040612 Use a default umask of `0o022` 2022-07-13 14:18:43 UTC
Red Hat Product Errata RHBA-2022:6095 0 None None None 2022-08-23 18:29:25 UTC

Comment 3 Weinan Liu 2022-08-10 10:21:43 UTC 
sh-4.4# umask
0022
sh-4.4# ps lp $(grep -l "Umask:[[:space:]]0000" /proc/[0-9]*/status | cut -f3 -d/) | grep -v "]$"
F   UID     PID    PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4     0       1       0  20   0 177900 16180 do_epo Ss   ?          0:41 /usr/lib/systemd/systemd --switched-root --system --deserialize 16

sh-4.4# oc version
Client Version: 4.10.0-202207291637.p0.ge29d58e.assembly.stream-e29d58e
Server Version: 4.10.0-0.nightly-2022-08-09-203611
Kubernetes Version: v1.23.5+012e945
sh-4.4#
Comment 7 errata-xmlrpc 2022-08-23 18:29:02 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 (OpenShift Container Platform 4.10.28 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-2022:6095
Note You need to log in before you can comment on or make changes to this bug.