Bug 1698407

Summary: console.vv file - set host FQDN in host field
Product: [oVirt] ovirt-engine Reporter: Liran Rotenberg <lrotenbe>
Component: BLL.VirtAssignee: Tomasz Barański <tbaransk>
Status: CLOSED CURRENTRELEASE QA Contact: Liran Rotenberg <lrotenbe>
Severity: medium Docs Contact:
Priority: urgent    
Version: 4.3.2.1CC: bugs, michal.skrivanek, rbarry
Target Milestone: ovirt-4.3.4Flags: pm-rhel: ovirt-4.3+
Target Release: 4.3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-11 06:25:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Liran Rotenberg 2019-04-10 10:25:46 UTC 
Description of problem:
When invoking console of a VM with console type VNC, the VV downloaded from engine should have the host FQDN under the host field.

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.3.1-0.1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a VM.
2. Set console type: VNC.
3. Run the VM.
4. Invoke console to the VM.
5. Check inside the VV file for host field.

Actual results:
In the host field we have the host name given in the engine, for example: host1.

Expected results:
host should be the host fqdn,
host: host_name.domain.com
Comment 3 Liran Rotenberg 2019-04-30 11:27:16 UTC 
Tried to verify on:
ovirt-engine-4.3.3.6-0.1.el7.noarch

Steps:
1. Create a VM.
2. Set console type: VNC.
3. Run the VM.
4. Invoke console to the VM.
5. Check inside the VV file for host field.

Results:
The host field is with the host name and not with the FQDN.
Comment 4 Michal Skrivanek 2019-04-30 12:22:47 UTC 
Tomasz, please do not move bugs to ON_QA without checking that it's actually there. Usually the automation works, when it doesn't and you have to flip it yourself you should always check that. The patch was intentionally hold back until 4.3.4, and so it shouldn't have been tested just yet in 4.3
Comment 5 Liran Rotenberg 2019-05-21 08:04:57 UTC 
Verified on:
ovirt-engine-4.3.4-0.1.el7.noarch

Steps:
1. Create a VM.
2. Set console type: VNC.
3. Run the VM.
4. Invoke console to the VM.
5. Check inside the VV file for host field.

Results:
The host field is set with the host's FQDN.
Comment 6 Sandro Bonazzola 2019-06-11 06:25:48 UTC 
This bugzilla is included in oVirt 4.3.4 release, published on June 11th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.4 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.