Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-75084

Bootable volumes are re-imported after set enableMultiArchBootImageImport to true for AMD64

XMLWordPrintable

    • Quality / Stability / Reliability
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Release Notes
    • Hide
      Known issue: duplicate boot sources after enabling enableMultiArchBootImageImport must be deleted

      If you enable spec.featureGates.enableMultiArchBootImageImport after boot sources were imported, OpenShift Virtualization recreates the boot source import resources using architecture-suffixed names. For example: fedora-amd64, fedora-arm64, fedora-s390x depending on what the cluster supports. The older, non-suffixed boot source resources are not automatically removed and remain in the openshift-virtualization-os-images namespace. This can result in duplicate boot sources displaying in the Web Console and the CLI. Storage usage can potentially increase because extra PVCs or VolumeSnapshots are still present.

      Workaround: Delete the leftover boot source resources. First, identify the DataSource objects that are currently active. These are the DataSource objects that resolve to the PVC/VolumeSnapshot that you want to keep. Next, delete the older/stale DataSource objects and the PVCs/VolumeSnapshots that they reference.
      Show
      Known issue: duplicate boot sources after enabling enableMultiArchBootImageImport must be deleted If you enable spec.featureGates.enableMultiArchBootImageImport after boot sources were imported, OpenShift Virtualization recreates the boot source import resources using architecture-suffixed names. For example: fedora-amd64, fedora-arm64, fedora-s390x depending on what the cluster supports. The older, non-suffixed boot source resources are not automatically removed and remain in the openshift-virtualization-os-images namespace. This can result in duplicate boot sources displaying in the Web Console and the CLI. Storage usage can potentially increase because extra PVCs or VolumeSnapshots are still present. Workaround: Delete the leftover boot source resources. First, identify the DataSource objects that are currently active. These are the DataSource objects that resolve to the PVC/VolumeSnapshot that you want to keep. Next, delete the older/stale DataSource objects and the PVCs/VolumeSnapshots that they reference.
    • Known Issue
    • Proposed
    • CNV I/U Operators Sprint 284
    • None

      Description of problem:

      On a cluster which default architecture is amd64, set enableMultiArchBootImageImport to true on the cluster, the bootable volumes are re-imported, which causes duplicated volumes with different label.

$ oc get VolumeSnapshot -n openshift-virtualization-os-images
NAME                                 READYTOUSE   SOURCEPVC                            SOURCESNAPSHOTCONTENT   RESTORESIZE   SNAPSHOTCLASS                            SNAPSHOTCONTENT                                    CREATIONTIME   AGE
centos-stream10-1d7e2727e6e4         true         centos-stream10-1d7e2727e6e4                                 30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-7cbadd4d-40a6-4edf-8654-26a5d01ae2ac   4d10h          4d10h
centos-stream10-840d19d49be8         true         centos-stream10-840d19d49be8                                 30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-f89511d4-3213-4a15-91d1-838008c5b964   5d             5d
centos-stream10-amd64-1d7e2727e6e4   true         centos-stream10-amd64-1d7e2727e6e4                           30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-b2e998b2-f022-4e82-82d0-9552cabdf045   13m            13m
centos-stream9-05a83de68e2f          true         centos-stream9-05a83de68e2f                                  30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-57907560-e4fa-444d-958f-03f6994e4338   3d12h          3d12h
centos-stream9-amd64-05a83de68e2f    true         centos-stream9-amd64-05a83de68e2f                            30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-f2ee12f8-8bd9-434a-8bcc-1b43ede7ab67   13m            13m
fedora-68ed96832eca                  true         fedora-68ed96832eca                                          30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-c36b3a30-2e59-49f3-bc81-40aaadabacb9   5d             5d
fedora-amd64-68ed96832eca            true         fedora-amd64-68ed96832eca                                    30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-c8981c42-1b4b-435c-b6d6-b75b40bc0fdb   13m            13m
rhel10-amd64-c03936a065f2            true         rhel10-amd64-c03936a065f2                                    30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-59706ebd-74bc-4b4e-888c-ed057c7de62a   13m            13m
rhel10-c03936a065f2                  true         rhel10-c03936a065f2                                          30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-e4922faf-6a64-44e8-bbe3-ffc31337e76a   5d             5d
rhel8-4ccd8b6aee47                   true         rhel8-4ccd8b6aee47                                           30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-a7f4fe17-3354-4f3e-b2a4-77b321f3a83e   5d             5d
rhel8-amd64-4ccd8b6aee47             true         rhel8-amd64-4ccd8b6aee47                                     30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-5b18687f-eb05-4e52-8daa-debe4c8e2356   13m            13m
rhel9-ab4ec16077fe                   true         rhel9-ab4ec16077fe                                           30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-ec61069e-8d53-4794-a4af-4f33d2a8ff06   5d             5d
rhel9-amd64-ab4ec16077fe             true         rhel9-amd64-ab4ec16077fe                                     30Gi          ocs-storagecluster-rbdplugin-snapclass   snapcontent-f31b35ce-f305-434a-968e-38461dbf368c   13m            13m

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

      v4.20, v4.21

      How reproducible:

      100%

      Steps to Reproduce:

      1.Have a fresh cluster which architecture is amd64 
2.set enableMultiArchBootImageImport:true in HCO
3.check bootable volumes on web UI

      Actual results:

      duplicated volumes presents

      Expected results:

      no duplicate items generated

      Additional info:

       

        1. duplicate_volumes.png
          duplicate_volumes.png
          279 kB

              nunnatsa Nahshon Unna Tsameret
              gouyang1@redhat.com Guohua Ouyang
              Harel Meir Harel Meir
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: