Bug 2070008 - The Console Disconnect Action Delay property isn't included in the OVF
Summary: The Console Disconnect Action Delay property isn't included in the OVF
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.5.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.5.0
: 4.5.0.1
Assignee: Arik
QA Contact: Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-30 09:30 UTC by Tamir
Modified: 2022-04-20 06:33 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.5.0.1
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-20 06:33:59 UTC
oVirt Team: Virt
Embargoed:
sbonazzo: ovirt-4.5+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 202 0 None Merged Add console disconnect action delay to OVF 2022-03-31 08:47:25 UTC
Red Hat Issue Tracker RHV-45477 0 None None None 2022-03-30 09:34:27 UTC

Description Tamir 2022-03-30 09:30:29 UTC
Description of problem:
After exporting a VM with the Console Disconnect Action Delay property and importing back the VM, the Console Disconnect Action Delay property in the imported VM was reset. The Console Disconnect Action Delay property wasn't included in the OVF.

Version-Release number of selected component (if applicable):
    - Engine instance with RHV 4.5.0-4 (ovirt-engine-4.5.0-0.237.el8ev) and RHEL 8.6 installed.
    - 3 hosts with RHV 4.5.0-4 and RHEL 8.6 and with vdsm-4.50.0.10-1.el8ev.


How reproducible:
100%

Steps to Reproduce:
1. Create a 4.7 data center and a 4.7 cluster.
2. Install the hosts and create a new NFS storage domain.
3. Create a VM with Console Disconnect Action set to Shutdown virtual machine and Console Disconnect Action Delay set to 9 minutes for example.
4. Export the VM to OVA.
5. Import the VM back to RHV.
6. Edit the imported VM and verify that the Console Disconnect Action Delay is set to 9.


Actual results:
1. The 4.7 data center and the 4.7 cluster were created.
2. The host was installed and the NFS storage domain was created.
3. The VM was created with Console Disconnect Action Delay set to 9 minutes.
4. The VM was exported successfully to OVA.
5. The VM was imported back to RHV.
6. The Console Disconnect Action Delay property was set to 0.

Expected results:
Steps 1-5 results are as expected. 
In step 6, the Console Disconnect Action Delay property should have been set to 9. 

Additional info:

Comment 1 Tamir 2022-04-12 15:45:53 UTC
Verified on RHV 4.5.0-5.

Env:
    - Engine instance with RHV 4.5.0-5 (ovirt-engine-4.5.0.2-0.7.el8ev) and RHEL 8.6 installed.
    - 3 hosts with RHV 4.5.0-5 and RHEL 8.6 and with vdsm-4.50.0.11-1.el8ev.

Steps:

In Admin Portal:
1. Create a 4.7 data center and a 4.7 cluster.
2. Install the hosts and create a new NFS storage domain.
3. Create a VM with Console Disconnect Action set to Shutdown virtual machine and Console Disconnect Action Delay set to 2 minutes.
4. Export the VM to OVA.
5. Extract the OVA file and check that the "vm.ovf" file contains the lines:
        <ConsoleDisconnectAction>SHUTDOWN</ConsoleDisconnectAction>
        <ConsoleDisconnectActionDelay>2</ConsoleDisconnectActionDelay>
6. Import the VM back to RHV.
7. Edit the imported VM and verify that the Console Disconnect Action Delay is set to 2.

Results (As Expected):
1. The 4.7 data center and the 4.7 cluster were created.
2. The hosts were installed and the NFS storage domain was created.
3. The VM was created with Console Disconnect Action Delay set to 2 minutes.
4. The VM was exported successfully to OVA.
5. The "vm.ovf" file contains the following child items inside the VirtualSystem item:
        <ConsoleDisconnectAction>SHUTDOWN</ConsoleDisconnectAction>
        <ConsoleDisconnectActionDelay>2</ConsoleDisconnectActionDelay>
6. The VM was imported back to RHV.
7. The Console Disconnect Action Delay property was set to 2.

Comment 2 Sandro Bonazzola 2022-04-20 06:33:59 UTC
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.