Created attachment 1425811 [details]
Description of problem:
While deploying HostedEngine successfully, set a temporary password by "hosted-engine --add-console-password --password="123456",
Use "vncviewer 10.73.73.106:5902" to login to HE-VM, but failed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Clean install redhat-virtualization-host-184.108.40.206-0.20180420.0 with ks
2. Deploy HE via cockpit
3. Use "hosted-engine --add-console-password " to set a temporary password
4. Login to the HE-VM by the temporary password
After step4, login to HE-VM failed
After step4, login to HE-VM successfully
Created attachment 1425813 [details]
Not sure if relevant but I see 10.73.73.106 in the terminal screenshot and 10.73.73.105 in the engine one.
Should the point to the same env?
(In reply to Simone Tiraboschi from comment #2)
> Not sure if relevant but I see 10.73.73.106 in the terminal screenshot and
> 10.73.73.105 in the engine one.
> Should the point to the same env?
Yes , it is the same env.
'hosted-engine --add-console-password' is simply calling
and from the logs it run successfully but then the user cannot login with that password directly pointing a VNC client to host address on the right port.
We didn't change that code in recent months/years.
The only relevant change is that we recently switched from VNC to Spice+VNC, Could it affect our setTicket call?
Yes. See https://github.com/oVirt/vdsm/blob/0cfab8ce3730ee89ed5b9dd9320a501d4254c0a0/lib/vdsm/virt/vm.py#L4977
You can use updateDevice instead if you need to set it on arbitrary console/protocol
Works for me with these component:
I will move to verify if the bug become to ON_QA.
Moving to verified forth to https://bugzilla.redhat.com/show_bug.cgi?id=1571113#c6.
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.
Since the problem described in this bug report should be
resolved in oVirt 4.2.3 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.