Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-14335

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • 4.10.z
    • 4.10.z
    • Node / CRI-O
    • None
    • Important
    • No
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      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

      Version-Release number of selected component (if applicable):

      OCP 4.10.51

      How reproducible:

      N/A

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      Umask from same image varies depending on the node

      Expected results:

      Umask is always the same

      Additional info:

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

              sgrunert@redhat.com Sascha Grunert
              rhn-support-mabajodu Mario Abajo Duran
              Sunil Choudhary Sunil Choudhary
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: