openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Merge pull request #105819 from Vaishali-gif-rh/CNV-78167

Browse Source 
CNV-78167: Known issue tracker - 4.21
This commit is contained in:
Shikha Jhala
2026-02-04 09:52:49 -05:00
committed by GitHub
parent 281249a2fe ad02b595b3
commit a53aa84d40
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
virt/release_notes/virt-4-21-release-notes.adoc
View File

@@ -211,3 +211,16 @@ Upgrading to {VirtProductName} 4.21 when using wasp-agent:: If you are upgrading
+
link:https://issues.redhat.com/browse/CNV-75837[CNV-75837]
//CNV-78167
Duplicate boot sources created after enabling multi-architecture imports::
When you enable the `spec.featureGates.enableMultiArchBootImageImport` feature gate after boot sources have already been imported, {VirtProductName} recreates the boot source import resources using architecture-suffixed names, such as `fedora-amd64` or `fedora-arm64`.
+
The original, non-suffixed boot source resources are not automatically removed and remain in the `openshift-virtualization-os-images` namespace. This results in duplicate boot sources appearing in the web console and CLI. These stale resources continue to consume storage space because the associated PVCs or `VolumeSnapshots` are retained.
+
To work around this problem, manually delete the stale boot source resources:
+
. Identify the currently active `DataSource` objects that resolve to the PVCs or `VolumeSnapshots` you want to keep.
. Delete the older, non-suffixed `DataSource` objects and the PVCs or `VolumeSnapshots` they reference.
+
link:https://issues.redhat.com/browse/CNV-75084[CNV-75084]