----- Original Message -----
From: "Frank Wall" <fw@moov.de> To: "Yedidyah Bar David" <didi@redhat.com> Cc: "Itamar Heim" <iheim@redhat.com>, users@ovirt.org, "Doron Fediuck" <dfediuck@redhat.com>, "Oved Ourfalli" <oourfali@redhat.com>, "Sandro Bonazzola" <sbonazzo@redhat.com> Sent: Sunday, January 26, 2014 11:04:23 PM Subject: Re: [Users] Hosted-engine runtime issues (3.4 BETA)
On Sun, Jan 26, 2014 at 03:54:34PM -0500, Yedidyah Bar David wrote:
Indeed. Might it be possible to not just move to maintenance but remove it from the engine? Then you can try again deploy as a second host.
I'll give it a spin. The host is scheduled for reinstallation tomorrow.
Good luck. Please report about any results/issues. If it fails, you can try first, after removing from the engine, # yum remove libvirt vdsm # rm -rf /etc/vdsm /etc/libvirt (or, of course, just reinstall if you do not care).
Well, this is also an unplanned, unsupported configuration. Might work for you - I don't know about anyone that tried that - but if possible, it's really better if you can add another host by hosted-engine --deploy.
I was expecting this answer :-) That's OK for me, I just wanted to try it out before reinstalling the host.
That's just fine, of course. And it's nice to know that it worked :-)
Thanks - Frank
Thanks, -- Didi