Le 2015-10-12 09:17, Nico a écrit : 

> Le 2015-10-12 09:09, Barak Korren a écrit : 
> What that procedure describes is backing up an existing engine,
> installing a new one and then restoring the backed up data into it.
> This was probably written to describe migration from a stand-alone
> engine host, not an AllInOne.
> Theoretically this should work for your setup, but I am not sure if
> the new hosted engine will be able to properly use the AllInOne node
> as a hypervisor (it would probably depend on the copied configuration
> containing enough details to allow the engine to connect to it over
> the network. you will probably at the very last have to shut down the
> existing engine before starting up the hosted engine)
> I would suggest doing as many backups as you can before starting, and
> performing the H.E. setup on a host that wasn't used by the existing
> engine, that way if it fails you can just shut it down and bring your
> old engine back up.

I got a backup running at this moment, scping
/gluster/ovirt/d44ee4b0-8d36-467a-9610-c682a618b698/images/ to a third

So, once done, i'll give a shot on the node2 which is running only VDSM
as Host agent. 

Hope all will be fine ! 


My backups are done, i'm now processing the installation for having the
engine in a VM but i got the following error at the first step: 

[root@devnix-virt-master02 ~]# hosted-engine --deploy
[ INFO ] Stage: Initializing
[ INFO ] Generating a temporary VNC password.
[ INFO ] Stage: Environment setup
Continuing will configure this host for serving as hypervisor and create
a VM where you have to install oVirt Engine afterwards.
Are you sure you want to continue? (Yes, No)[Yes]:
Configuration files: []
Log file:
Version: otopi-1.3.2 (otopi-1.3.2-1.el7.centos)
[ INFO ] Hardware supports virtualization
[ INFO ] Bridge ovirtmgmt already created
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization 


During customization use CTRL-D to abort.
[ ERROR ] The following storage pool has been found connected:
[ ERROR ] Failed to execute stage 'Environment customization': Cannot
setup Hosted Engine with connected storage pools
[ INFO ] Stage: Clean up
[ INFO ] Generating answer file
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination 

There is no VM running at this moment on this hypervisor (node 2). The
error suggests that the storage is still in use. 

[root@devnix-virt-master02 ~]# vdsClient -s 0

Does that mean i must set this hypervisor (node 2) in MAINTENANCE in
order to continue the steps described in





Users mailing list

Reply via email to