-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
4.18
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Turning an existing virtual machine disk image into a generalized image for use in templates is a common ask from customers who have migrated to the platform. The documentation is incomplete and difficult for new users.
Version-Release number of selected component (if applicable):
4.18
How reproducible:
always
Steps to Reproduce:
1. Deploy or identify an existing Linux VM on CNV 2. Navigate to https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/virtualization/advanced-vm-creation#virt-generalizing-linux-vm-image_virt-creating-vms-uploading-images 3. Follow steps to "Generlalize a VM image"
Actual results:
* Steps 3, 4, and 5: Example naming of PV is inconsistent: <my_vm_volume> and <my-vm-volume> * Step 6 assumes disk image is visible at 'disk.img'. In my testing using ODF and rbd this is not correct. It is at /dev/vda ** Discovery of the true volume location inside the libguestfs pod may be discovered by viewing the volumeDevices in that pod spec * Step 9 this step will hang if the libguestfs pod is not terminated. The clone initiated by adding to the catalog will just sit in pending indefinitely. A step "6.5" should be added to exit the libguestfs pod.
Expected results:
The documentation should be concise but account for variability which confounds a new user.
Additional info:
https://redhat-internal.slack.com/archives/C068X44C8VB/p1745608585579509
- is cloned by
-
CNV-60687 generalize VM disk image docs incomplete
-
- New
-