[ovirt-users] Re: ovirt 4.2 failed deploy

Hi Alex, I'm sorry we weren't able to help you get 4.2 up and running in time. Definitely let us know if you encounter any issues on your next attempt. Your feedback is greatly appreciated! -Phillip Bailey On Wed, May 16, 2018 at 9:36 AM, Alex K wrote: > Hi, > > I am

[ovirt-users] Re: ovirt 4.2 failed deploy

gt; Cc: Alex K <rightkickt...@gmail.com>; Phillip Bailey <phbai...@redhat.com>; users <users@ovirt.org> Subject: Re: [ovirt-users] Re: ovirt 4.2 failed deploy On Tue, May 15, 2018 at 7:01 PM, Justin Zygmont <jzygm...@proofpoint.com<mailto:jzygm...@proofpoint.com>> w

[ovirt-users] Re: ovirt 4.2 failed deploy

Hi, I am sorry I don't have this setup available anymore. I had to provide a quick solution and went with 4.1 version. I will see if I can reproduce this on next build. Thanx, Alex On Wed, May 16, 2018 at 5:38 AM, Phillip Bailey wrote: > Alex, > > I haven't run into any

[ovirt-users] Re: ovirt 4.2 failed deploy

ghtkickt...@gmail.com] > *Sent:* Tuesday, May 15, 2018 2:00 AM > *To:* Phillip Bailey <phbai...@redhat.com> > *Cc:* users <users@ovirt.org> > *Subject:* [ovirt-users] Re: ovirt 4.2 failed deploy > > > > I overcame this with: > > run at host: > > >

[ovirt-users] Re: ovirt 4.2 failed deploy

Alex, I haven't run into any issues with ovirt-ha-agent. I'm adding Simone who may have a better idea of what could be causing the problem. Could you provide any logs you have available from that deployment? Also, could you please run "journalctl -u ovirt-ha-agent" on that host and provide the

[ovirt-users] Re: ovirt 4.2 failed deploy

I wonder why this option isn’t just added to the hosted-engine command instead? From: Alex K [mailto:rightkickt...@gmail.com] Sent: Tuesday, May 15, 2018 2:00 AM To: Phillip Bailey <phbai...@redhat.com> Cc: users <users@ovirt.org> Subject: [ovirt-users] Re: ovirt 4.2 failed deploy

[ovirt-users] Re: ovirt 4.2 failed deploy

Hi Philip, I finally was not able to complete it. The ovirt ha agent at host was not starting for some reason. It could be because I ran a hosted-engine-cleanup earlier. So I need to repeat from scratch to be able to reproduce/verify. Alex On Tue, May 15, 2018 at 2:48 PM, Phillip Bailey

[ovirt-users] Re: ovirt 4.2 failed deploy

Alex, I'm glad to hear you were able to get everything running! Please let us know if you have any issues going forward. Best regards, -Phillip Bailey On Tue, May 15, 2018 at 4:59 AM, Alex K wrote: > I overcame this with: > > run at host: > >

[ovirt-users] Re: ovirt 4.2 failed deploy

I overcame this with: run at host: /usr/sbin/ovirt-hosted-engine-cleanup Redeployed then engine engine-setup This time was ok. Thanx, Alex On Tue, May 15, 2018 at 10:51 AM, Alex K wrote: > Hi, > > Thanx for the feedback. > > *getent ahostsv4 v0.mydomain* > > gives:

[ovirt-users] Re: ovirt 4.2 failed deploy

Hi, Thanx for the feedback. *getent ahostsv4 v0.mydomain* gives: 172.16.30.10STREAM v0 172.16.30.10DGRAM 172.16.30.10RAW which means that *getent ahostsv4 v0.mydomain | grep v0.mydomain* gives null I overcame this by using the flag *--noansible* to proceed with the python way

[ovirt-users] Re: ovirt 4.2 failed deploy

Hi Alex, I believe the lines below from the deploy log point to the issue. I bolded the important parts. It looks like it was unable to resolve the FQDN for the host. What output and return code do you get when you run "getent ahostsv4 v0.mydomain | grep v0.mydomain" on that machine? 2018-05-14