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

Seeing the local disk labels 'google-' generated for the root disk on upgraded 4.13. cluster

XMLWordPrintable

    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Seeing the labels 'google-' generated for the root disk

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

       

      How reproducible:

       

      Steps to Reproduce:

      1.Provision a fresh cluster: RHCOS 4.12.0/OCP 4.12.17
      2. Upgrade from 4.12.17 to 4.13.1 using the fast-4.13 channel. ( after unblocking the 4.13.1 version) 
      $ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.12-kube-1.26-api-removals-in-4.13":"true"}}' --type=merge ( to unblock)
      3. Now go to compute node terminal and issue
       chroot /host
      
       
      
      4) sh-4.4# chroot /host
      
      sh-5.1# lsblk
      
      NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
      
      vda    252:0    0 19.5G  0 disk 
      
      
      
      -vda3 252:3    0  384M  0 part /boot
      
      `-vda4 252:4    0 19.2G  0 part /var/lib/containers/storage/overlay
      
                                      /var
      
                                      /sysroot/ostree/deploy/rhcos/var
      
                                      /sysroot
      
                                      /usr
      
                                      /etc
      
                                      /
      
      sh-5.1# cd /dev/disk/by-id
      
      sh-5.1# ls -l
      
      total 0
      
      lrwxrwxrwx. 1 root root  9 Jun  1 19:42 google- -> ../../vda
      
      lrwxrwxrwx. 1 root root 10 Jun  1 19:42 google--part3 -> ../../vda3
      
      lrwxrwxrwx. 1 root root 10 Jun  1 19:42 google--part4 -> ../../vda4
      
      sh-5.1# 
      
      

      Actual results:

      The labels with "google-" appear and symlink is pointing to root disk.

      Expected results:

      should not see any labels as no disks were added to this cluster.

      Additional info:

      Note: Could not reproduce on a fresh 4.13.0 cluster install or on 4.12.0

              Unassigned Unassigned
              dnaphade1 Deepti Naphade (Inactive)
              Wei Duan Wei Duan
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: