On Mon, Feb 25, 2019 at 2:53 PM Sakhi Hadebe <sakhi@sanren.ac.za> wrote:
Hi  Simone,

The name resolution is working fine.

Running:
getent ahosts engine.sanren.ac.za

gives the same output:

192.168.x.x    STREAM engine.sanren.ac.za
192.168.x.x    DGRAM
192.168.x.x    RAW
 The IP address being the engine IP Address.

The hosts are on the same subnet as the HostedEngine. I can ping the hosts from each other. There is a NATting device, that NATs the private IP addresses to public IP addresses. From the hosts I can reach the internet, but I cant ping from outside (security measure). We also using this device to VPN to the cluster

[root@gohan ~]# virsh -r list
 Id    Name                           State
----------------------------------------------------
 13    HostedEngine                   running

[root@gohan ~]# virsh -r dumpxml HostedEngine | grep -i tlsPort
    <graphics type='spice' port='5901' tlsPort='5902' autoport='yes' listen='192.168.x.x' passwdValidTo='1970-01-01T00:00:01'>

[root@gohan ~]# virsh -r vncdisplay HostedEngine
192.168.x.x:0

[root@gohan ~]# hosted-engine --add-console-password
Enter password:

You can now connect the hosted-engine VM with VNC at 192.168.x.x:5900

VNCing with the above gives me the blank black screen and a cursor (See attached). I cant do anything on that screen.

OK, I can suggest to to power off the engine VM with hosted-engine --vm-poweroff and then start it again with hosted-engine --vm-start in order to follow the whole boot process over VNC
 


Please help

 

On Mon, Feb 25, 2019 at 11:34 AM Simone Tiraboschi <stirabos@redhat.com> wrote:


On Mon, Feb 25, 2019 at 10:27 AM Sakhi Hadebe <sakhi@sanren.ac.za> wrote:
Hi Simone,

Thank you for your response. Executing the command below, gives this:

[root@ovirt-host]# curl http://$(grep fqdn /etc/ovirt-hosted-engine/hosted-engine.conf | cut -d= -f2)/ovirt-engine/services/health  
curl: (7) Failed to connect to engine.sanren.ac.za:80; No route to host

I tried to enable http traffic on the ovirt-host, but the error persists

Run, on your hosts,
getent ahosts engine.sanren.ac.za

and ensure that it got resolved as you wish.
Fix name resolution and routing on your hosts in a coherent manner. 



--
Regards,
Sakhi Hadebe
Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR
 
Tel:   +27 12 841 2308
Fax:   +27 12 841 4223
Cell:  +27 71 331 9622
Email: sakhi@sanren.ac.za