[OCP 4.10] crio umask set to 0000 in some nodes

Similar issue to bugzilla [1] 2106794 but happening on 4.10.51 cluster

Running pods:
NAME                               READY   STATUS      RESTARTS   AGE     IP             NODE                                       NOMINATED NODE   READINESS GATES
aaaaaa-2-2q5w6                     1/1     Running     0          5d21h   10.129.2.xx    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx   <none>           <none>
aaaaaa-2-thrj8                     1/1     Running     0          5d22h   10.128.3.yyy   yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy   <none>           <none>

Pods  umask:
$ oc rsh aaaaaa-2-2q5w6
sh-4.4$ umask
0000

$ oc rsh aaaaaa-2-thrj8
sh-4.4$ umask
0022

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2106794

OCP 4.10.51

N/A

1.
2.
3.

Umask from same image varies depending on the node

Umask is always the same

seems the same issue as already fixed -> https://bugzilla.redhat.com/show_bug.cgi?id=2106794