-
Bug
-
Resolution: Unresolved
-
Major
-
CNV v4.14.0, CNV v4.15.0, CNV v4.16.0, CNV v4.17.0, CNV v4.18.0
-
2
-
False
-
-
False
-
-
None
-
Red
-
Release Note Not Required
-
---
-
---
-
-
Yes
-
None
Description of problem:
The doc about "Configuring a storage class for custom boot source updates" needs to be re-worked:
https://docs.openshift.com/container-platform/4.16/virt/storage/virt-automatic-bootsource-updates.html#virt-configuring-storage-class-bootsource-update_virt-automatic-bootsource-updates
Key points:
- either add the storage class in the HCO CR
- or change the virt-default storage class
- or change the default storage class (explain the difference)
Re-import the images:
- delete the old boot source (DataSource, DataVolume/PVC, VolumeSnapshot)
Version-Release number of selected component (if applicable):
4.18, 4.17, 4.16, 4.15, 4.14
How reproducible:
Always
Actual results:
No accurate and clear steps
Expected results:
Clear steps for the user
Storage team described the accurate steps of the process: https://docs.google.com/document/d/1DMQk7m04D0v8B13nQ1CgqFnmJBlUchEMYzriqLBy1DQ/edit?tab=t.0
- clones
-
-
- Closed
-
- links to