Il 04/Mar/2017 12:21, "Maton, Brett" <matonb@ltresources.co.uk> ha scritto:

I'm not sure why it's asking for vdsm-client >= 4.18.6

I've got the following vdsm rpms installed:

vdsm-4.19.4-1.el7.centos.x86_64
vdsm-api-4.19.4-1.el7.centos.noarch
vdsm-cli-4.19.4-1.el7.centos.noarch
vdsm-hook-vmfex-dev-4.19.4-1.el7.centos.noarch
vdsm-jsonrpc-4.19.4-1.el7.centos.noarch
vdsm-python-4.19.4-1.el7.centos.noarch
vdsm-xmlrpc-4.19.4-1.el7.centos.noarch
vdsm-yajsonrpc-4.19.4-1.el7.centos.noarch

Still missing vdsm-client in the list.

On 3 March 2017 at 15:26, Maton, Brett <matonb@ltresources.co.uk> wrote:

Ok thanks, I'll give that another go shortly

On 3 March 2017 at 15:24, Yaniv Kaul <ykaul@redhat.com> wrote:

On Fri, Mar 3, 2017 at 5:21 PM Maton, Brett <matonb@ltresources.co.uk> wrote:

Hi Simone,

  I just tried to install the RPM but got a dependency issue:

Error: Package: ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch (/ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch)
           Requires: vdsm-client >= 4.18.6

I haven't tried to install vdsm-client as I'm not sure what impact that will have on the other pacakges

vdsm-client is our 'next-gen' vdsClient - the CLI client to VDSM. You can and should install it in 4.1.

Y.

 

On 3 March 2017 at 10:59, Maton, Brett <matonb@ltresources.co.uk> wrote:

Thanks Simone,

  I'll give that a go this evening, I'm remote at the moment.

Regards,

Brett

On 3 March 2017 at 10:48, Simone Tiraboschi <stirabos@redhat.com> wrote:

On Fri, Mar 3, 2017 at 11:35 AM, Maton, Brett <matonb@ltresources.co.uk> wrote:

VM Up not responding - Yes that seems to be the case.

I did actually try hosted-engine --console

hosted-engine --console
The engine VM is running on this host
Connected to domain HostedEngine
Escape character is ^]
error: internal error: cannot find character device <null>

This was the result of https://bugzilla.redhat.com/show_bug.cgi?id=1364132

Could you please install this (it's from 4.1.1 RC) http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/el7/noarch/ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch.rpm to get it fixed.

You need then to run:

systemctl restart ovirt-ha-agent

hosted-engine --vm-shutdown

# wait for it

hosted-engine --vm-start

At this point you have should have the serial console.

 

On 3 March 2017 at 08:39, Simone Tiraboschi <stirabos@redhat.com> wrote:

On Thu, Mar 2, 2017 at 11:42 AM, Maton, Brett <matonb@ltresources.co.uk> wrote:

What is the correct way to shut down a cluster ?

I shutdown my 4.1 cluster following this guide https://github.com/rharmonson/richtech/wiki/OSVDC-Series:-oVirt-3.6-Cluster-Shutdown-and-Startup as the NAS hosting the nfs mounts needed rebooting after updates.

( I realise the guide is for 3.6, surely not that different ? )

It seams fine.

 

However hosted engine isn't starting now.

  failed liveliness check

So it seams that the engine VM is up but the engine is not responding.

 

I've tried connecting from the host starting the HE vm to see what's going on with:

virsh console HostedEngine

   I don't know what authentication it requires, tried engine admin details and root os...

hosted-engine --console 

 

hosted-engine --add-console-password
Enter password:
no graphics devices configured

unsurprisingly, remote-viewer vnc://localhost:5900

fails with Unable to connect to the graphic server vnc://localhost:5900

What can I do next ?

Check the status of the engine.

 

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users