Description of problem: Wrong port ":-1" being reported several times, while running "hosted-engine --add-console-password" right after running "hosted-engine --vm-start-paused" on ha-host in global maintenance. Opening this bug based on https://bugzilla.redhat.com/show_bug.cgi?id=1674932#c13. I see that VNC console port getting reported incorrectly to the customer for engine's VM started in paused mode: alma03 ~]# hosted-engine --add-console-password Enter password: You can now connect the hosted-engine VM with VNC at 10.35.92.3:5902 [root@alma03 ~]# hosted-engine --vm-poweroff [root@alma03 ~]# hosted-engine --vm-start-paused [root@alma03 ~]# hosted-engine --add-console-password Enter password: You can now connect the hosted-engine VM with VNC at 10.35.92.3:-1 [root@alma03 ~]# hosted-engine --add-console-password Enter password: You can now connect the hosted-engine VM with VNC at 10.35.92.3:-1 [root@alma03 ~]# hosted-engine --add-console-password Enter password: You can now connect the hosted-engine VM with VNC at 10.35.92.3:-1 [root@alma03 ~]# hosted-engine --add-console-password Enter password: You can now connect the hosted-engine VM with VNC at 10.35.92.3:5902 Version-Release number of selected component (if applicable): ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch ovirt-hosted-engine-setup-2.3.8-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1.Deploy HE over NFS. 2.Set environment in to global maintenance. 3.hosted-engine --vm-poweroff 4.hosted-engine --vm-start-paused 5.Run hosted-engine --add-console-password 6.Run hosted-engine --add-console-password several more times, until you receive correct VNC port value. Actual results: Wrong port ":-1" being reported several times, while running "hosted-engine --add-console-password" right after running "hosted-engine --vm-start-paused" on ha-host in global maintenance. Expected results: VNC should have only positive port numbers and they should work properly. Additional info: Please see also https://pnt-devops-rad-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ccs-mr-preview-prod/2608/artifact/doc-Administration_Guide/preview/index.html#Booting_a_Self-Hosted_Engine_in_Recovery_Mode_SHE_admin.
Verified on ovirt-hosted-engine-setup-2.3.10-1.el7ev.noarch
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-2019:2435