Description of problem: Currently, in order to properly "seal" (make a VM generic in preparation for cloning or template), it is a manual process or a painful RHEV-CLI process in order to use virt-sysprep. In RHEL+KVM (or CENTOS, Ubuntu, etc), this is not an issue. Our own Red Hat documentation suggests a painful manual removal of SSH keys, UDEV rules, MAC addresses, system id, and hostname. It is the complete opposite of automation. In order to run sys-virtprep in RHEV, you have to go through the trouble of deploying the RHEV-CLI, locate the the disk image, activate the logical volume, run virt-sysprep, deactivate the logical volume, then create the template back in RHEV-M. Version-Release number of selected component (if applicable): all versions How reproducible: Create a VM in RHEV. You are unable to utilize `virt-sysprep` or other libguestfs tools in a convenient manner. Expected results: Have an option in the template tab or VM tab to open a dialog box for sealing options.
I ran into this same issue at a customer site this week. The process of building a template does seem archaic in comparison to the larger story we're delivering around hybrid cloud automation. It would be helpful to have this functionality delivered from the UI for RHEL guests.
upstream tracking https://trello.com/c/dN08y1W2
may appear in 4.1.z or even 4.1 GA
Verification builds: rhvm-4.2.0.2-0.1.el7 qemu-kvm-rhev-2.9.0-16.el7_4.13.x86_64 sanlock-3.5.0-1.el7.x86_64 libvirt-client-3.2.0-14.el7_4.5.x86_64 vdsm-4.20.9.3-1.el7ev.x86_64 cloud-init-0.7.9-19.el7
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1488
BZ<2>Jira Resync