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

RHCOS misses udev rules for GCE PD NVMe disks

XMLWordPrintable

    • Important
    • No
    • 3
    • Sprint 233 - Team OSInt, Sprint 234 - Team OSInt, Sprint 235, Sprint 236 - OSIntegration, Sprint 237 - OSIntegration
    • 5
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, pods were stuck in the `ContainerCreating` state on Google Cloud Platform Confidential Computing instances, which caused a volume mount failure. This fix adds support for the Persistent Disk storage type for Confidential Computing instances in Google Cloud Platform, which can be used as persistent volumes in {product-title}. As a result, pods are able to enter a `Running` state and volumes can be mounted. (link:https://issues.redhat.com/browse/OCPBUGS-7582[*OCPBUGS-7582*])
      Show
      Previously, pods were stuck in the `ContainerCreating` state on Google Cloud Platform Confidential Computing instances, which caused a volume mount failure. This fix adds support for the Persistent Disk storage type for Confidential Computing instances in Google Cloud Platform, which can be used as persistent volumes in {product-title}. As a result, pods are able to enter a `Running` state and volumes can be mounted. (link: https://issues.redhat.com/browse/OCPBUGS-7582 [* OCPBUGS-7582 *])
    • Enhancement
    • Done

      Description of problem:

      Pod stays in "ContainerCreating" and volume mount failure on Confidential Computing.

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

      4.13.0-0.nightly-2023-02-15-202607

      How reproducible:

      Always on GCP Confidential Computing profile

      Steps to Reproduce:

      1. Create a cluster with Confidential Computing (See https://issues.redhat.com/browse/OCPBU-142)  
2. Create pvc with standard-csi sc, pvc is "Bound"
3. Pod stays in "ContainerCreating" and volume mount failure.  
$ oc describe pod
  Warning  FailedMount             <invalid> (x20 over 24m)  kubelet                  MountVolume.MountDevice failed for volume "pvc-81cb59ab-cd79-4400-8fe8-3e4ac4aa0bd7" : rpc error: code = Internal desc = Error when getting device path: rpc error: code = Internal desc = error verifying GCE PD ("pvc-81cb59ab-cd79-4400-8fe8-3e4ac4aa0bd7") is attached: failed to find and re-link disk pvc-81cb59ab-cd79-4400-8fe8-3e4ac4aa0bd7 with udevadm after retrying for 3s: timed out waiting for the condition

      Actual results:

      Pod is "ContainerCreating" and volume mount failed

      Expected results:

      Pod should be in "Running" status.

      Additional info:

       

              rravanel Renata Andrade Matos Ravanelli
              wduan@redhat.com Wei Duan
              Wei Duan Wei Duan
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: