Description of problem: Importing a Virtual Machine OVA always enables 'Cloud-init/Sysprep' even though it is unchecked/disabled before exporting. Version-Release number of selected component (if applicable): ovirt-engine-4.2.7.5-0.1.el7ev.noarch How reproducible: [100%] Steps to Reproduce: 1. Create a VM and keep 'Cloud_Init/Sysprep' unchecked. 2. Export the VM as OVA 3. Now, Import the exported OVA. 4. Edit the VM(which is imported using the OVA) and check if 'Cloud_Init/Sysprep' is enabled. Actual results: 'Cloud_Init/Sysprep' is enabled by default even though it is disabled before exporting. Expected results: 'Cloud_Init/Sysprep' should not be enabled after import if it is disabled before export.
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both
sync2jira
WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops
Verified on: - ovirt-engine-4.4.0-0.15.master.el7.noarch Verification steps: 1. Create a VM and make sure 'Initial Run > Use Cloud-Init/Sysprep' is unchecked. 2. Export the VM as OVA. 3. Import the vm from the exported OVA file. Result: - VM is imported and 'Initial Run > Use Cloud-Init/Sysprep' remain unchecked.
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops
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 (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), 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/RHSA-2020:3247