@sascha. ---> Nokia SEP Senior Manager called nme to a meeting yesterday to ask the progress of this OCP 4.9.z backport. It's needed urgently! The BZ has severity "low" which is not acceptable, The case has visibilty to Senior Nokia vRAN/SEP Management We need that the backport can be expedited... Colum Gaynor - Senior Partner Success Manager, Nokia Global Account
@Sunil Choudhary <schoudha> ---> Is there a schedule when the OCP 4.9.z bakport (ie this BZ) can enter QE. I have understood that backport to OCP 4.10.z went ok ? Colum Gaynor - Senior Partner Success Manager
Attached PR merged
sh-4.4# umask 0022 sh-4.4# ps lp $(grep -l "Umask:[[:space:]]0000" /proc/[0-9]*/status | cut -f3 -d/) | grep -v "]$" grep: /proc/23989/status: No such file or directory F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 4 0 1 0 20 0 177040 15388 do_epo Ss ? 0:09 /usr/lib/systemd/systemd --switched-root --system --deserialize 17 Verified on 4.9.46
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: OpenShift Container Platform 4.9.47 bug fix and security 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:6147