Re: [ovirt-users] Single server hosted engine... almost there

[Yedidyah Bar David]

On Thu, Dec 8, 2016 at 5:24 PM, Mark Steckel  wrote:
> [Apologize. Accidentally hit send instead of save. Continuing below...]
>
>> - Yedidyah Bar David  wrote:
>> > On Thu, Dec 8, 2016 at 12:42 AM, Mark Steckel  wrote:
>> > > Hi,
>> > >
>> > > OK, I reset things and tried again but was more more careful regarding 
>> > > the DNS setup which I believe was correct this. In other words, the 
>> > > FQDNs were resolved from both the host and the HE VM.
>> > >
>> > > After the latest failure I execute 'ip address' to see the state of the 
>> > > interfaces. And lo and behold the /29 IP I had on eth0:1 no longer 
>> > > exists.
>> > >
>> > > So some context.
>> > >
>> > > The server's primary IP is a /24 with the gw being the x.y.z.1.
>> > >
>> > > I have have a /29 subnet to use for the VMs.
>> > >
>> > > I have been presuming that I place the a.b.c.1/29 on eth0:1 for the 
>> > > subnet's gw and OVirt will ether keep it in place or migrate it to the 
>> > > ovirtmgmt device. Instead it is deleted during "hosted-engine 
>> > > --deploy".(Note, when the .1/29 is assigned to eth0:1, the IP address is 
>> > > reachable from the the Internet.)
>> > >
>> > > Dnsmasq is configured to a) serve a.b.c.2/29 a.b.c.6/29 via DHCP and b) 
>> > > to resolve unique FQDNs for each IP. The he VM set to receive the 
>> > > a.b.c.2/29 address.
>> > >
>> > > Am I missing and or just misunderstanding something here?
>> >
>> > "eth0:1" is not really a different interface.
>> >
>> > Part of the deploy process is to take the interface you have chosen,
>> > create a new bridge, copy part of the configuration from the nic to
>> > the bridge, and add the nic to the bridge. This is one of the most
>> > delicate parts of the process, the one that if fails might leave you
>> > with no network access, the one due to which we recommend to run this
>> > inside 'screen'. You can't do this to "eth0" and keep "eth0:1"
>> > untouched. You need either a vlan interface or a separate physical
>> > nic. If you feel like this, please open a bug to make 'hosted-engine
>> > --deploy' notice and prevent what you tried to do. Currently it does
>> > not check IP aliases.
>
> I was creating the /29 gw IP on eth0:1 because it seems the simplest thing to 
> do. There is no requirement for it to hang off of eth0.
>
> Given that I have to hang the entire /29 subnet on the host (and VMs), and I 
> am presuming that the gw IP of the /29 must be on the host, do you have a 
> suggestion of how to configure this? (And to be explicit about it, do I need 
> the /29 gw IP on the host to ensure the vm networking operates?)

Not sure, but even if you do, I think you can do that after --deploy finishes.
Can you please detail (again, perhaps) your intention/plan? How many NICs you
have, can you use VLANs, etc.? Also, if if it's a single host that will remain
single, you might find it simpler to use virt-manager. oVirt is intended for
managing larger setups.

>
> Without the vm engine logs it is difficult to determine why the engine vm 
> fails when resolving its fqdn. At this point I'm presuming it's due to a 
> networking/routing issue, but am open to suggestions.
>
>
>> > Another point - the script that failed is 'engine-setup'. This one
>> > runs inside the engine vm, and keeps its logs in
>> > /var/log/ovirt-engine/setup. If it fails again, please check/post also
>> > these, if at all possible (that is, if you can access the vm).
>> > Thinking about this, it might be possible for 'hosted-engine --deploy'
>> > to get this log, perhaps through the virtual serial connection it
>> > opens to show you the output, and save it on the host side, for easier
>> > debugging. Please open a bug for this too :-)
>>
>
> When the engine vm setup fails I am unable to connect to it via 
> "hosted-engine --console". Should console access to the engine vm exist at 
> this point? If so, what is the best way to access the engine vm console?
>
> The lack access to the engine vm logs is very painful for trying to diagnose 
> what is going wrong. Ideas welcomed!
>

If the vm is still up, you can see its qemu process on the host
with 'ps'.

I detailed most of what I know about accessing the console in:

http://www.ovirt.org/documentation/admin-guide/hosted-engine-console/

Please note that in recent versions, '--console' connects you to the
serial console, not graphical one. We did this so that we do not
need to enforce installing a graphical env on mostly-headless hosts.

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Single server hosted engine... almost there

[Yedidyah Bar David]

On Thu, Dec 8, 2016 at 6:45 PM, Derek Atkins  wrote:
> Hi,
>
> On Thu, December 8, 2016 11:37 am, Mark Steckel wrote:
>>
>>> Yeah, I suspect you will need to set up your engine NOT using the
>>> appliance, but instead install CentOS and then the engine inside the VM.
>>> This will give you more direct access to the engine VM, and should give
>>> you the opportunity to set up the bridge routing during the process.
>>
>> Makes sense, at least in concept.
>>
>> But are you suggesting that I manually set up the vm for the engine (ie
>> not use "hosted-engine --deploy")
>
> No, you should still use hosted-engine --deploy, but use a CentOS install
> media instead of a virtual appliance.
>
>> and then manually run engine setup from w/i the vm?
>
> Yes.  You will need to do that.  But this should give you the opportunity
> to test networking, DNS, routing, etc on the host and VM prior to running
> engine-setup.

Not sure you really need much more control on the engine vm or
engine-setup for that - you mainly need to tell --deploy to not touch
iptables, and then handle that yourself.

Also, you can use the appliance without using cloud-init - then you can
do everything manually, and just save yourself from having to yum install
stuff inside the engine vm.

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Single server hosted engine... almost there

[Derek Atkins]

Hi,

On Thu, December 8, 2016 11:37 am, Mark Steckel wrote:
>
>> Yeah, I suspect you will need to set up your engine NOT using the
>> appliance, but instead install CentOS and then the engine inside the VM.
>> This will give you more direct access to the engine VM, and should give
>> you the opportunity to set up the bridge routing during the process.
>
> Makes sense, at least in concept.
>
> But are you suggesting that I manually set up the vm for the engine (ie
> not use "hosted-engine --deploy")

No, you should still use hosted-engine --deploy, but use a CentOS install
media instead of a virtual appliance.

> and then manually run engine setup from w/i the vm?

Yes.  You will need to do that.  But this should give you the opportunity
to test networking, DNS, routing, etc on the host and VM prior to running
engine-setup.

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

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

Re: [ovirt-users] Single server hosted engine... almost there

[Mark Steckel]

Hi,

- Derek Atkins  wrote:
> Hi,
> 
> On Thu, December 8, 2016 11:15 am, Mark Steckel wrote:
> >
> > - Derek Atkins  wrote:
> >> Hi,
> >>
> >> Mark Steckel  writes:
> >>
> >> > Am I missing and or just misunderstanding something here?
> >> >
> >> > Oh, and does ip_forwarding need to be set in the kernel? (ie
> >> > net.ipv4.ip_forward=1)
> >>
> >> If you expect the host to act as the router for your /29, then yes, it
> >> would need to forward packets.  You will also need to set up the
> >> firewall on the host to properly forward packets through.
> >>
> >> It honestly might be easier for you to get an actual router instead of
> >> trying to force your host to act as both host+router.  I suspect the
> >> hosted-engine --deploy script wouldn't really know how to properly
> >> handle the host as a router so it might either break that configuration
> >> or at least not know how to set it up.
> >
> > Agreed. Unfortunately, the hosting company (Hetzner) providing the server
> > requires the /29 to be on the host.
> >
> > Googling "ovirt Hetzner" shows that a number of people have attempted this
> > at Hetzner and have run into various problems. Here is one of the more
> > relevant examples:
> >
> > http://lists.ovirt.org/pipermail/users/2014-January/019785.html
> > (check out the first link)
> > http://lists.ovirt.org/pipermail/users/2014-February/020913.html
> >
> > So it seems this is doable, but needs a bit more finesse than I've used so
> > far.
> 
> Yeah, I suspect you will need to set up your engine NOT using the
> appliance, but instead install CentOS and then the engine inside the VM. 
> This will give you more direct access to the engine VM, and should give
> you the opportunity to set up the bridge routing during the process.

Makes sense, at least in concept. 

But are you suggesting that I manually set up the vm for the engine (ie not use 
"hosted-engine --deploy") and then manually run engine setup from w/i the vm?



> 
> > Mark
> 
> -derek
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> 

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

Re: [ovirt-users] Single server hosted engine... almost there

[Derek Atkins]

Hi,

On Thu, December 8, 2016 11:15 am, Mark Steckel wrote:
>
> - Derek Atkins  wrote:
>> Hi,
>>
>> Mark Steckel  writes:
>>
>> > Am I missing and or just misunderstanding something here?
>> >
>> > Oh, and does ip_forwarding need to be set in the kernel? (ie
>> > net.ipv4.ip_forward=1)
>>
>> If you expect the host to act as the router for your /29, then yes, it
>> would need to forward packets.  You will also need to set up the
>> firewall on the host to properly forward packets through.
>>
>> It honestly might be easier for you to get an actual router instead of
>> trying to force your host to act as both host+router.  I suspect the
>> hosted-engine --deploy script wouldn't really know how to properly
>> handle the host as a router so it might either break that configuration
>> or at least not know how to set it up.
>
> Agreed. Unfortunately, the hosting company (Hetzner) providing the server
> requires the /29 to be on the host.
>
> Googling "ovirt Hetzner" shows that a number of people have attempted this
> at Hetzner and have run into various problems. Here is one of the more
> relevant examples:
>
> http://lists.ovirt.org/pipermail/users/2014-January/019785.html
> (check out the first link)
> http://lists.ovirt.org/pipermail/users/2014-February/020913.html
>
> So it seems this is doable, but needs a bit more finesse than I've used so
> far.

Yeah, I suspect you will need to set up your engine NOT using the
appliance, but instead install CentOS and then the engine inside the VM. 
This will give you more direct access to the engine VM, and should give
you the opportunity to set up the bridge routing during the process.

> Mark

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

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

Re: [ovirt-users] Single server hosted engine... almost there

[Mark Steckel]

- Derek Atkins  wrote:
> Hi,
> 
> Mark Steckel  writes:
> 
> > Am I missing and or just misunderstanding something here?
> >
> > Oh, and does ip_forwarding need to be set in the kernel? (ie
> > net.ipv4.ip_forward=1)
> 
> If you expect the host to act as the router for your /29, then yes, it
> would need to forward packets.  You will also need to set up the
> firewall on the host to properly forward packets through.
> 
> It honestly might be easier for you to get an actual router instead of
> trying to force your host to act as both host+router.  I suspect the
> hosted-engine --deploy script wouldn't really know how to properly
> handle the host as a router so it might either break that configuration
> or at least not know how to set it up.

Agreed. Unfortunately, the hosting company (Hetzner) providing the server 
requires the /29 to be on the host.

Googling "ovirt Hetzner" shows that a number of people have attempted this at 
Hetzner and have run into various problems. Here is one of the more relevant 
examples:

http://lists.ovirt.org/pipermail/users/2014-January/019785.html  (check out 
the first link)
http://lists.ovirt.org/pipermail/users/2014-February/020913.html

So it seems this is doable, but needs a bit more finesse than I've used so far. 

Mark




> 
> > Thanks
> > Mark
> 
> -derek
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant

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

Re: [ovirt-users] Single server hosted engine... almost there

[Derek Atkins]

Hi,

Mark Steckel  writes:

> Am I missing and or just misunderstanding something here?
>
> Oh, and does ip_forwarding need to be set in the kernel? (ie
> net.ipv4.ip_forward=1)

If you expect the host to act as the router for your /29, then yes, it
would need to forward packets.  You will also need to set up the
firewall on the host to properly forward packets through.

It honestly might be easier for you to get an actual router instead of
trying to force your host to act as both host+router.  I suspect the
hosted-engine --deploy script wouldn't really know how to properly
handle the host as a router so it might either break that configuration
or at least not know how to set it up.

> Thanks
> Mark

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Single server hosted engine... almost there

[Mark Steckel]

[Apologize. Accidentally hit send instead of save. Continuing below...]

> - Yedidyah Bar David  wrote:
> > On Thu, Dec 8, 2016 at 12:42 AM, Mark Steckel  wrote:
> > > Hi,
> > >
> > > OK, I reset things and tried again but was more more careful regarding 
> > > the DNS setup which I believe was correct this. In other words, the FQDNs 
> > > were resolved from both the host and the HE VM.
> > >
> > > After the latest failure I execute 'ip address' to see the state of the 
> > > interfaces. And lo and behold the /29 IP I had on eth0:1 no longer exists.
> > >
> > > So some context.
> > >
> > > The server's primary IP is a /24 with the gw being the x.y.z.1.
> > >
> > > I have have a /29 subnet to use for the VMs.
> > >
> > > I have been presuming that I place the a.b.c.1/29 on eth0:1 for the 
> > > subnet's gw and OVirt will ether keep it in place or migrate it to the 
> > > ovirtmgmt device. Instead it is deleted during "hosted-engine 
> > > --deploy".(Note, when the .1/29 is assigned to eth0:1, the IP address is 
> > > reachable from the the Internet.)
> > >
> > > Dnsmasq is configured to a) serve a.b.c.2/29 a.b.c.6/29 via DHCP and b) 
> > > to resolve unique FQDNs for each IP. The he VM set to receive the 
> > > a.b.c.2/29 address.
> > >
> > > Am I missing and or just misunderstanding something here?
> > 
> > "eth0:1" is not really a different interface.
> > 
> > Part of the deploy process is to take the interface you have chosen,
> > create a new bridge, copy part of the configuration from the nic to
> > the bridge, and add the nic to the bridge. This is one of the most
> > delicate parts of the process, the one that if fails might leave you
> > with no network access, the one due to which we recommend to run this
> > inside 'screen'. You can't do this to "eth0" and keep "eth0:1"
> > untouched. You need either a vlan interface or a separate physical
> > nic. If you feel like this, please open a bug to make 'hosted-engine
> > --deploy' notice and prevent what you tried to do. Currently it does
> > not check IP aliases.

I was creating the /29 gw IP on eth0:1 because it seems the simplest thing to 
do. There is no requirement for it to hang off of eth0.

Given that I have to hang the entire /29 subnet on the host (and VMs), and I am 
presuming that the gw IP of the /29 must be on the host, do you have a 
suggestion of how to configure this? (And to be explicit about it, do I need 
the /29 gw IP on the host to ensure the vm networking operates?)

Without the vm engine logs it is difficult to determine why the engine vm fails 
when resolving its fqdn. At this point I'm presuming it's due to a 
networking/routing issue, but am open to suggestions.


> > Another point - the script that failed is 'engine-setup'. This one
> > runs inside the engine vm, and keeps its logs in
> > /var/log/ovirt-engine/setup. If it fails again, please check/post also
> > these, if at all possible (that is, if you can access the vm).
> > Thinking about this, it might be possible for 'hosted-engine --deploy'
> > to get this log, perhaps through the virtual serial connection it
> > opens to show you the output, and save it on the host side, for easier
> > debugging. Please open a bug for this too :-)
> 

When the engine vm setup fails I am unable to connect to it via "hosted-engine 
--console". Should console access to the engine vm exist at this point? If so, 
what is the best way to access the engine vm console?

The lack access to the engine vm logs is very painful for trying to diagnose 
what is going wrong. Ideas welcomed!

Thanks
Mark



> 
> 
> 
> > 
> > Thanks, and good luck!
> > 
> > >
> > > Oh, and does ip_forwarding need to be set in the kernel? (ie 
> > > net.ipv4.ip_forward=1)
> > >
> > > Thanks
> > > Mark
> > >
> > >
> > >
> > > - Derek Atkins  wrote:
> > >> Hi,
> > >>
> > >> You need to make sure resolv.conf is correct (both on the host AND on the
> > >> engine vm).
> > >>
> > >> So:   dig hostname
> > >> (without the @local-ip)
> > >>
> > >> As for the VM not coming up...  I'm not sure how to delay "engine-setup"
> > >> run.  I presume you're running an engine appliance -- I ran my own CentOS
> > >> install on the engine.  The logs imply it's suggesting you can access the
> > >> engine VM console, but maybe it's exiting quickly?
> > >>
> > >> -derek
> > >>
> > >> On Wed, December 7, 2016 3:52 pm, Mark Steckel wrote:
> > >> > I tested dnsmasq from the host by
> > >> >
> > >> >dig hostname @local-ip
> > >> >
> > >> > Worked fine.
> > >> >
> > >> > The engine VM never comes up to the point where I can access it via the
> > >> > console...
> > >> >
> > >> >
> > >> > - Derek Atkins  wrote:
> > >> >> Hi,
> > >> >>
> > >> >> Ensure dnsmasq is working and can be accessed by the engine VM?
> > >> >> Log in to the engine VM and test from there?
> > >> >> Maybe set up *real* DNS?
> > >> >>
> > >> >> -derek
> > >> >>
> > >> >> On Wed, December 7, 2016 

Re: [ovirt-users] Single server hosted engine... almost there

[Mark Steckel]

- Yedidyah Bar David  wrote:
> On Thu, Dec 8, 2016 at 12:42 AM, Mark Steckel  wrote:
> > Hi,
> >
> > OK, I reset things and tried again but was more more careful regarding the 
> > DNS setup which I believe was correct this. In other words, the FQDNs were 
> > resolved from both the host and the HE VM.
> >
> > After the latest failure I execute 'ip address' to see the state of the 
> > interfaces. And lo and behold the /29 IP I had on eth0:1 no longer exists.
> >
> > So some context.
> >
> > The server's primary IP is a /24 with the gw being the x.y.z.1.
> >
> > I have have a /29 subnet to use for the VMs.
> >
> > I have been presuming that I place the a.b.c.1/29 on eth0:1 for the 
> > subnet's gw and OVirt will ether keep it in place or migrate it to the 
> > ovirtmgmt device. Instead it is deleted during "hosted-engine 
> > --deploy".(Note, when the .1/29 is assigned to eth0:1, the IP address is 
> > reachable from the the Internet.)
> >
> > Dnsmasq is configured to a) serve a.b.c.2/29 a.b.c.6/29 via DHCP and b) to 
> > resolve unique FQDNs for each IP. The he VM set to receive the a.b.c.2/29 
> > address.
> >
> > Am I missing and or just misunderstanding something here?
> 
> "eth0:1" is not really a different interface.
> 
> Part of the deploy process is to take the interface you have chosen,
> create a new bridge, copy part of the configuration from the nic to
> the bridge, and add the nic to the bridge. This is one of the most
> delicate parts of the process, the one that if fails might leave you
> with no network access, the one due to which we recommend to run this
> inside 'screen'. You can't do this to "eth0" and keep "eth0:1"
> untouched. You need either a vlan interface or a separate physical
> nic. If you feel like this, please open a bug to make 'hosted-engine
> --deploy' notice and prevent what you tried to do. Currently it does
> not check IP aliases.

I was creating the /29 gw IP on eth0:1 because it seems the simplest thing to 
do. There is no requirement for it to hang off of eth0.

Without the vm engine logs it is difficult to determine why the engine vm fails 
when resolving its fqdn. At this point I'm presuming it's due to a 
networking/routing issue, but am open to suggestions.


> Another point - the script that failed is 'engine-setup'. This one
> runs inside the engine vm, and keeps its logs in
> /var/log/ovirt-engine/setup. If it fails again, please check/post also
> these, if at all possible (that is, if you can access the vm).
> Thinking about this, it might be possible for 'hosted-engine --deploy'
> to get this log, perhaps through the virtual serial connection it
> opens to show you the output, and save it on the host side, for easier
> debugging. Please open a bug for this too :-)

When the engine vm setup fails I am unable to connect to it via "hosted-engine 
--console". Is there an way to tell "hosted-engine --deploy"



> 
> Thanks, and good luck!
> 
> >
> > Oh, and does ip_forwarding need to be set in the kernel? (ie 
> > net.ipv4.ip_forward=1)
> >
> > Thanks
> > Mark
> >
> >
> >
> > - Derek Atkins  wrote:
> >> Hi,
> >>
> >> You need to make sure resolv.conf is correct (both on the host AND on the
> >> engine vm).
> >>
> >> So:   dig hostname
> >> (without the @local-ip)
> >>
> >> As for the VM not coming up...  I'm not sure how to delay "engine-setup"
> >> run.  I presume you're running an engine appliance -- I ran my own CentOS
> >> install on the engine.  The logs imply it's suggesting you can access the
> >> engine VM console, but maybe it's exiting quickly?
> >>
> >> -derek
> >>
> >> On Wed, December 7, 2016 3:52 pm, Mark Steckel wrote:
> >> > I tested dnsmasq from the host by
> >> >
> >> >dig hostname @local-ip
> >> >
> >> > Worked fine.
> >> >
> >> > The engine VM never comes up to the point where I can access it via the
> >> > console...
> >> >
> >> >
> >> > - Derek Atkins  wrote:
> >> >> Hi,
> >> >>
> >> >> Ensure dnsmasq is working and can be accessed by the engine VM?
> >> >> Log in to the engine VM and test from there?
> >> >> Maybe set up *real* DNS?
> >> >>
> >> >> -derek
> >> >>
> >> >> On Wed, December 7, 2016 3:41 pm, Mark Steckel wrote:
> >> >> > Hi Derek,
> >> >> >
> >> >> > - Derek Atkins  wrote:
> >> >> >> Hi Mark,
> >> >> >>
> >> >> >> The error is correct, hosted-engine-1.pcstrac.com is not a valid
> >> >> >> hostname:
> >> >> >>
> >> >> >> $ host hosted-engine-1.pcstrac.com
> >> >> >> $
> >> >> >>
> >> >> >> I'm lost, tho -- was this an error that occurred on the host during
> >> >> >> hosted-engine --deploy, or was it an error that occurred in the
> >> >> hosted
> >> >> >> enging VM when running engine-setup?
> >> >> >
> >> >> > I believe when it occurred when the running the engine-setup.
> >> >> >
> >> >> >
> >> >> >> If the former, you need to ensure that you have a real DNS name for
> >> >> your
> >> >> >> ovirt engine.  It's unclear (to me) 

Re: [ovirt-users] Single server hosted engine... almost there

[Yedidyah Bar David]

On Thu, Dec 8, 2016 at 12:42 AM, Mark Steckel  wrote:
> Hi,
>
> OK, I reset things and tried again but was more more careful regarding the 
> DNS setup which I believe was correct this. In other words, the FQDNs were 
> resolved from both the host and the HE VM.
>
> After the latest failure I execute 'ip address' to see the state of the 
> interfaces. And lo and behold the /29 IP I had on eth0:1 no longer exists.
>
> So some context.
>
> The server's primary IP is a /24 with the gw being the x.y.z.1.
>
> I have have a /29 subnet to use for the VMs.
>
> I have been presuming that I place the a.b.c.1/29 on eth0:1 for the subnet's 
> gw and OVirt will ether keep it in place or migrate it to the ovirtmgmt 
> device. Instead it is deleted during "hosted-engine --deploy".(Note, when the 
> .1/29 is assigned to eth0:1, the IP address is reachable from the the 
> Internet.)
>
> Dnsmasq is configured to a) serve a.b.c.2/29 a.b.c.6/29 via DHCP and b) to 
> resolve unique FQDNs for each IP. The he VM set to receive the a.b.c.2/29 
> address.
>
> Am I missing and or just misunderstanding something here?

"eth0:1" is not really a different interface.

Part of the deploy process is to take the interface you have chosen,
create a new bridge, copy part of the configuration from the nic to
the bridge, and add the nic to the bridge. This is one of the most
delicate parts of the process, the one that if fails might leave you
with no network access, the one due to which we recommend to run this
inside 'screen'. You can't do this to "eth0" and keep "eth0:1"
untouched. You need either a vlan interface or a separate physical
nic. If you feel like this, please open a bug to make 'hosted-engine
--deploy' notice and prevent what you tried to do. Currently it does
not check IP aliases.

Another point - the script that failed is 'engine-setup'. This one
runs inside the engine vm, and keeps its logs in
/var/log/ovirt-engine/setup. If it fails again, please check/post also
these, if at all possible (that is, if you can access the vm).
Thinking about this, it might be possible for 'hosted-engine --deploy'
to get this log, perhaps through the virtual serial connection it
opens to show you the output, and save it on the host side, for easier
debugging. Please open a bug for this too :-)

Thanks, and good luck!

>
> Oh, and does ip_forwarding need to be set in the kernel? (ie 
> net.ipv4.ip_forward=1)
>
> Thanks
> Mark
>
>
>
> - Derek Atkins  wrote:
>> Hi,
>>
>> You need to make sure resolv.conf is correct (both on the host AND on the
>> engine vm).
>>
>> So:   dig hostname
>> (without the @local-ip)
>>
>> As for the VM not coming up...  I'm not sure how to delay "engine-setup"
>> run.  I presume you're running an engine appliance -- I ran my own CentOS
>> install on the engine.  The logs imply it's suggesting you can access the
>> engine VM console, but maybe it's exiting quickly?
>>
>> -derek
>>
>> On Wed, December 7, 2016 3:52 pm, Mark Steckel wrote:
>> > I tested dnsmasq from the host by
>> >
>> >dig hostname @local-ip
>> >
>> > Worked fine.
>> >
>> > The engine VM never comes up to the point where I can access it via the
>> > console...
>> >
>> >
>> > - Derek Atkins  wrote:
>> >> Hi,
>> >>
>> >> Ensure dnsmasq is working and can be accessed by the engine VM?
>> >> Log in to the engine VM and test from there?
>> >> Maybe set up *real* DNS?
>> >>
>> >> -derek
>> >>
>> >> On Wed, December 7, 2016 3:41 pm, Mark Steckel wrote:
>> >> > Hi Derek,
>> >> >
>> >> > - Derek Atkins  wrote:
>> >> >> Hi Mark,
>> >> >>
>> >> >> The error is correct, hosted-engine-1.pcstrac.com is not a valid
>> >> >> hostname:
>> >> >>
>> >> >> $ host hosted-engine-1.pcstrac.com
>> >> >> $
>> >> >>
>> >> >> I'm lost, tho -- was this an error that occurred on the host during
>> >> >> hosted-engine --deploy, or was it an error that occurred in the
>> >> hosted
>> >> >> enging VM when running engine-setup?
>> >> >
>> >> > I believe when it occurred when the running the engine-setup.
>> >> >
>> >> >
>> >> >> If the former, you need to ensure that you have a real DNS name for
>> >> your
>> >> >> ovirt engine.  It's unclear (to me) that using /etc/hosts is
>> >> sufficient.
>> >> >> However looking at the logs, it looks like it can locally resolve (to
>> >> >> xx.yy.18.122).
>> >> >
>> >> > Yep. I tested things to make sure it could resolve before I started
>> >> the
>> >> > 'hosted-engine --deploy'.
>> >> >
>> >> >> You might need to answer "Yes" to the /etc/hosts question..
>> >> >
>> >> > I did answer "Yes".
>> >> >
>> >> >
>> >> >> The log seems to get far enough along that it presents you the engine
>> >> vm
>> >> >> console URL?  It looks like the issue is that the engine vm cannot
>> >> >> resolve
>> >> >> its own name.
>> >> >
>> >> > That is my take as well.
>> >> >
>> >> > Scratching my head as I config'ed dnsmasq to provide local dns and to
>> >> read
>> >> > from /etc/hosts for 

Re: [ovirt-users] Single server hosted engine... almost there

[Mark Steckel]

Hi,

OK, I reset things and tried again but was more more careful regarding the DNS 
setup which I believe was correct this. In other words, the FQDNs were resolved 
from both the host and the HE VM.

After the latest failure I execute 'ip address' to see the state of the 
interfaces. And lo and behold the /29 IP I had on eth0:1 no longer exists. 

So some context.

The server's primary IP is a /24 with the gw being the x.y.z.1.

I have have a /29 subnet to use for the VMs.

I have been presuming that I place the a.b.c.1/29 on eth0:1 for the subnet's gw 
and OVirt will ether keep it in place or migrate it to the ovirtmgmt device. 
Instead it is deleted during "hosted-engine --deploy".(Note, when the .1/29 is 
assigned to eth0:1, the IP address is reachable from the the Internet.)

Dnsmasq is configured to a) serve a.b.c.2/29 a.b.c.6/29 via DHCP and b) to 
resolve unique FQDNs for each IP. The he VM set to receive the a.b.c.2/29 
address.

Am I missing and or just misunderstanding something here?

Oh, and does ip_forwarding need to be set in the kernel? (ie 
net.ipv4.ip_forward=1)

Thanks
Mark



- Derek Atkins  wrote:
> Hi,
> 
> You need to make sure resolv.conf is correct (both on the host AND on the
> engine vm).
> 
> So:   dig hostname
> (without the @local-ip)
> 
> As for the VM not coming up...  I'm not sure how to delay "engine-setup"
> run.  I presume you're running an engine appliance -- I ran my own CentOS
> install on the engine.  The logs imply it's suggesting you can access the
> engine VM console, but maybe it's exiting quickly?
> 
> -derek
> 
> On Wed, December 7, 2016 3:52 pm, Mark Steckel wrote:
> > I tested dnsmasq from the host by
> >
> >dig hostname @local-ip
> >
> > Worked fine.
> >
> > The engine VM never comes up to the point where I can access it via the
> > console...
> >
> >
> > - Derek Atkins  wrote:
> >> Hi,
> >>
> >> Ensure dnsmasq is working and can be accessed by the engine VM?
> >> Log in to the engine VM and test from there?
> >> Maybe set up *real* DNS?
> >>
> >> -derek
> >>
> >> On Wed, December 7, 2016 3:41 pm, Mark Steckel wrote:
> >> > Hi Derek,
> >> >
> >> > - Derek Atkins  wrote:
> >> >> Hi Mark,
> >> >>
> >> >> The error is correct, hosted-engine-1.pcstrac.com is not a valid
> >> >> hostname:
> >> >>
> >> >> $ host hosted-engine-1.pcstrac.com
> >> >> $
> >> >>
> >> >> I'm lost, tho -- was this an error that occurred on the host during
> >> >> hosted-engine --deploy, or was it an error that occurred in the
> >> hosted
> >> >> enging VM when running engine-setup?
> >> >
> >> > I believe when it occurred when the running the engine-setup.
> >> >
> >> >
> >> >> If the former, you need to ensure that you have a real DNS name for
> >> your
> >> >> ovirt engine.  It's unclear (to me) that using /etc/hosts is
> >> sufficient.
> >> >> However looking at the logs, it looks like it can locally resolve (to
> >> >> xx.yy.18.122).
> >> >
> >> > Yep. I tested things to make sure it could resolve before I started
> >> the
> >> > 'hosted-engine --deploy'.
> >> >
> >> >> You might need to answer "Yes" to the /etc/hosts question..
> >> >
> >> > I did answer "Yes".
> >> >
> >> >
> >> >> The log seems to get far enough along that it presents you the engine
> >> vm
> >> >> console URL?  It looks like the issue is that the engine vm cannot
> >> >> resolve
> >> >> its own name.
> >> >
> >> > That is my take as well.
> >> >
> >> > Scratching my head as I config'ed dnsmasq to provide local dns and to
> >> read
> >> > from /etc/hosts for hosted-engine-1.pcstrac.com.
> >> >
> >> > The only thing I think I flubbed was neglecting to add the host's IP
> >> to
> >> > the host's /etc/resolv.conf.
> >> >
> >> > Scrubbing and staring again.
> >> >
> >> > Mark
> >> >
> >> >
> >> >>
> >> >> -derek
> >> >>
> >> >> On Wed, December 7, 2016 3:13 pm, Mark Steckel wrote:
> >> >> > Folks,
> >> >> >
> >> >> > Thanks to Didi in another thread I'm making progress. (Lesson
> >> learned,
> >> >> > choose 'disk' and not 'cdrom' when using the he-appliance.)
> >> >> >
> >> >> > So I reset to a fresh CentOS 7, installed various software packages
> >> >> > including ovirt.
> >> >> >
> >> >> > I configed eth0 with a /32 public IP. I also added an alias for a
> >> >> > x.x.x.1/29 on eth0:1.
> >> >> >
> >> >> > Finally I config'ed dnsmasq to provide both dhcp and dns (ensuring
> >> >> that it
> >> >> > will read from /etc/hosts before forwarding dns requests) and added
> >> >> the
> >> >> > IPs and hostsnames to /etc/hosts from the /29 IPs which are to be
> >> used
> >> >> by
> >> >> > the VMs.
> >> >> >
> >> >> > Things proceeded nicely till resolving the he vm fqdn. (I tested to
> >> >> make
> >> >> > sure that the he vm fqdm would resolve **Before** I ran
> >> 'hosted-engine
> >> >> > --deploy'.)
> >> >> >
> >> >> >   |-   --== NETWORK CONFIGURATION ==--
> >> >> >   |-
> >> >> >   |- [ ERROR ] Host name is not valid:
> 

Re: [ovirt-users] Single server hosted engine... almost there

[Derek Atkins]

Hi,

You need to make sure resolv.conf is correct (both on the host AND on the
engine vm).

So:   dig hostname
(without the @local-ip)

As for the VM not coming up...  I'm not sure how to delay "engine-setup"
run.  I presume you're running an engine appliance -- I ran my own CentOS
install on the engine.  The logs imply it's suggesting you can access the
engine VM console, but maybe it's exiting quickly?

-derek

On Wed, December 7, 2016 3:52 pm, Mark Steckel wrote:
> I tested dnsmasq from the host by
>
>dig hostname @local-ip
>
> Worked fine.
>
> The engine VM never comes up to the point where I can access it via the
> console...
>
>
> - Derek Atkins  wrote:
>> Hi,
>>
>> Ensure dnsmasq is working and can be accessed by the engine VM?
>> Log in to the engine VM and test from there?
>> Maybe set up *real* DNS?
>>
>> -derek
>>
>> On Wed, December 7, 2016 3:41 pm, Mark Steckel wrote:
>> > Hi Derek,
>> >
>> > - Derek Atkins  wrote:
>> >> Hi Mark,
>> >>
>> >> The error is correct, hosted-engine-1.pcstrac.com is not a valid
>> >> hostname:
>> >>
>> >> $ host hosted-engine-1.pcstrac.com
>> >> $
>> >>
>> >> I'm lost, tho -- was this an error that occurred on the host during
>> >> hosted-engine --deploy, or was it an error that occurred in the
>> hosted
>> >> enging VM when running engine-setup?
>> >
>> > I believe when it occurred when the running the engine-setup.
>> >
>> >
>> >> If the former, you need to ensure that you have a real DNS name for
>> your
>> >> ovirt engine.  It's unclear (to me) that using /etc/hosts is
>> sufficient.
>> >> However looking at the logs, it looks like it can locally resolve (to
>> >> xx.yy.18.122).
>> >
>> > Yep. I tested things to make sure it could resolve before I started
>> the
>> > 'hosted-engine --deploy'.
>> >
>> >> You might need to answer "Yes" to the /etc/hosts question..
>> >
>> > I did answer "Yes".
>> >
>> >
>> >> The log seems to get far enough along that it presents you the engine
>> vm
>> >> console URL?  It looks like the issue is that the engine vm cannot
>> >> resolve
>> >> its own name.
>> >
>> > That is my take as well.
>> >
>> > Scratching my head as I config'ed dnsmasq to provide local dns and to
>> read
>> > from /etc/hosts for hosted-engine-1.pcstrac.com.
>> >
>> > The only thing I think I flubbed was neglecting to add the host's IP
>> to
>> > the host's /etc/resolv.conf.
>> >
>> > Scrubbing and staring again.
>> >
>> > Mark
>> >
>> >
>> >>
>> >> -derek
>> >>
>> >> On Wed, December 7, 2016 3:13 pm, Mark Steckel wrote:
>> >> > Folks,
>> >> >
>> >> > Thanks to Didi in another thread I'm making progress. (Lesson
>> learned,
>> >> > choose 'disk' and not 'cdrom' when using the he-appliance.)
>> >> >
>> >> > So I reset to a fresh CentOS 7, installed various software packages
>> >> > including ovirt.
>> >> >
>> >> > I configed eth0 with a /32 public IP. I also added an alias for a
>> >> > x.x.x.1/29 on eth0:1.
>> >> >
>> >> > Finally I config'ed dnsmasq to provide both dhcp and dns (ensuring
>> >> that it
>> >> > will read from /etc/hosts before forwarding dns requests) and added
>> >> the
>> >> > IPs and hostsnames to /etc/hosts from the /29 IPs which are to be
>> used
>> >> by
>> >> > the VMs.
>> >> >
>> >> > Things proceeded nicely till resolving the he vm fqdn. (I tested to
>> >> make
>> >> > sure that the he vm fqdm would resolve **Before** I ran
>> 'hosted-engine
>> >> > --deploy'.)
>> >> >
>> >> >   |-   --== NETWORK CONFIGURATION ==--
>> >> >   |-
>> >> >   |- [ ERROR ] Host name is not valid:
>> >> hosted-engine-1.pcstrac.com
>> >> > did not resolve into an IP address
>> >> >   |- [ ERROR ] Failed to execute stage 'Environment
>> >> > customization': Host name is not valid:
>> >> > hosted-engine-1.pcstrac.com did not resolve into an IP address
>> >> >   |- [ INFO  ] Stage: Clean up
>> >> >   |-   Log file is located at
>> >> > /var/log/ovirt-engine/setup/ovirt-engine-setup-20161207193757-6i03xg.log
>> >> >   |- [ INFO  ] Generating answer file
>> >> > '/var/lib/ovirt-engine/setup/answers/20161207193758-setup.conf'
>> >> >   |- [ INFO  ] Stage: Pre-termination
>> >> >   |- [ INFO  ] Stage: Termination
>> >> >   |- [ ERROR ] Execution of setup failed
>> >> >   |- HE_APPLIANCE_ENGINE_SETUP_FAIL
>> >> > [ ERROR ] Engine setup failed on the appliance
>> >> > [ ERROR ] Failed to execute stage 'Closing up': Engine setup
>> >> failed on
>> >> > the appliance Please check its log on the appliance.
>> >> >
>> >> >
>> >> > The one thing I forgot is to update /etc/resolv.conf to include the
>> >> host
>> >> > though I don't know if this matters...
>> >> >
>> >> > Logs attached.
>> >> >
>> >> > I suspect I've very close to having this working but am admittedly
>> >> > stumped.
>> >> >
>> >> > Pointers appreciated.
>> >> >
>> >> > Thanks
>> >> > Mark
>> >> >
>> >> >
>> >> > 

Re: [ovirt-users] Single server hosted engine... almost there

[Mark Steckel]

I tested dnsmasq from the host by

   dig hostname @local-ip

Worked fine.

The engine VM never comes up to the point where I can access it via the 
console...


- Derek Atkins  wrote:
> Hi,
> 
> Ensure dnsmasq is working and can be accessed by the engine VM?
> Log in to the engine VM and test from there?
> Maybe set up *real* DNS?
> 
> -derek
> 
> On Wed, December 7, 2016 3:41 pm, Mark Steckel wrote:
> > Hi Derek,
> >
> > - Derek Atkins  wrote:
> >> Hi Mark,
> >>
> >> The error is correct, hosted-engine-1.pcstrac.com is not a valid
> >> hostname:
> >>
> >> $ host hosted-engine-1.pcstrac.com
> >> $
> >>
> >> I'm lost, tho -- was this an error that occurred on the host during
> >> hosted-engine --deploy, or was it an error that occurred in the hosted
> >> enging VM when running engine-setup?
> >
> > I believe when it occurred when the running the engine-setup.
> >
> >
> >> If the former, you need to ensure that you have a real DNS name for your
> >> ovirt engine.  It's unclear (to me) that using /etc/hosts is sufficient.
> >> However looking at the logs, it looks like it can locally resolve (to
> >> xx.yy.18.122).
> >
> > Yep. I tested things to make sure it could resolve before I started the
> > 'hosted-engine --deploy'.
> >
> >> You might need to answer "Yes" to the /etc/hosts question..
> >
> > I did answer "Yes".
> >
> >
> >> The log seems to get far enough along that it presents you the engine vm
> >> console URL?  It looks like the issue is that the engine vm cannot
> >> resolve
> >> its own name.
> >
> > That is my take as well.
> >
> > Scratching my head as I config'ed dnsmasq to provide local dns and to read
> > from /etc/hosts for hosted-engine-1.pcstrac.com.
> >
> > The only thing I think I flubbed was neglecting to add the host's IP to
> > the host's /etc/resolv.conf.
> >
> > Scrubbing and staring again.
> >
> > Mark
> >
> >
> >>
> >> -derek
> >>
> >> On Wed, December 7, 2016 3:13 pm, Mark Steckel wrote:
> >> > Folks,
> >> >
> >> > Thanks to Didi in another thread I'm making progress. (Lesson learned,
> >> > choose 'disk' and not 'cdrom' when using the he-appliance.)
> >> >
> >> > So I reset to a fresh CentOS 7, installed various software packages
> >> > including ovirt.
> >> >
> >> > I configed eth0 with a /32 public IP. I also added an alias for a
> >> > x.x.x.1/29 on eth0:1.
> >> >
> >> > Finally I config'ed dnsmasq to provide both dhcp and dns (ensuring
> >> that it
> >> > will read from /etc/hosts before forwarding dns requests) and added
> >> the
> >> > IPs and hostsnames to /etc/hosts from the /29 IPs which are to be used
> >> by
> >> > the VMs.
> >> >
> >> > Things proceeded nicely till resolving the he vm fqdn. (I tested to
> >> make
> >> > sure that the he vm fqdm would resolve **Before** I ran 'hosted-engine
> >> > --deploy'.)
> >> >
> >> >   |-   --== NETWORK CONFIGURATION ==--
> >> >   |-
> >> >   |- [ ERROR ] Host name is not valid:
> >> hosted-engine-1.pcstrac.com
> >> > did not resolve into an IP address
> >> >   |- [ ERROR ] Failed to execute stage 'Environment
> >> > customization': Host name is not valid:
> >> > hosted-engine-1.pcstrac.com did not resolve into an IP address
> >> >   |- [ INFO  ] Stage: Clean up
> >> >   |-   Log file is located at
> >> > /var/log/ovirt-engine/setup/ovirt-engine-setup-20161207193757-6i03xg.log
> >> >   |- [ INFO  ] Generating answer file
> >> > '/var/lib/ovirt-engine/setup/answers/20161207193758-setup.conf'
> >> >   |- [ INFO  ] Stage: Pre-termination
> >> >   |- [ INFO  ] Stage: Termination
> >> >   |- [ ERROR ] Execution of setup failed
> >> >   |- HE_APPLIANCE_ENGINE_SETUP_FAIL
> >> > [ ERROR ] Engine setup failed on the appliance
> >> > [ ERROR ] Failed to execute stage 'Closing up': Engine setup
> >> failed on
> >> > the appliance Please check its log on the appliance.
> >> >
> >> >
> >> > The one thing I forgot is to update /etc/resolv.conf to include the
> >> host
> >> > though I don't know if this matters...
> >> >
> >> > Logs attached.
> >> >
> >> > I suspect I've very close to having this working but am admittedly
> >> > stumped.
> >> >
> >> > Pointers appreciated.
> >> >
> >> > Thanks
> >> > Mark
> >> >
> >> >
> >> > ___
> >> > Users mailing list
> >> > Users@ovirt.org
> >> > http://lists.ovirt.org/mailman/listinfo/users
> >> >
> >>
> >>
> >> --
> >>Derek Atkins 617-623-3745
> >>de...@ihtfp.com www.ihtfp.com
> >>Computer and Internet Security Consultant
> >>
> >
> >
> 
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> 

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

Re: [ovirt-users] Single server hosted engine... almost there

[Derek Atkins]

Hi,

Ensure dnsmasq is working and can be accessed by the engine VM?
Log in to the engine VM and test from there?
Maybe set up *real* DNS?

-derek

On Wed, December 7, 2016 3:41 pm, Mark Steckel wrote:
> Hi Derek,
>
> - Derek Atkins  wrote:
>> Hi Mark,
>>
>> The error is correct, hosted-engine-1.pcstrac.com is not a valid
>> hostname:
>>
>> $ host hosted-engine-1.pcstrac.com
>> $
>>
>> I'm lost, tho -- was this an error that occurred on the host during
>> hosted-engine --deploy, or was it an error that occurred in the hosted
>> enging VM when running engine-setup?
>
> I believe when it occurred when the running the engine-setup.
>
>
>> If the former, you need to ensure that you have a real DNS name for your
>> ovirt engine.  It's unclear (to me) that using /etc/hosts is sufficient.
>> However looking at the logs, it looks like it can locally resolve (to
>> xx.yy.18.122).
>
> Yep. I tested things to make sure it could resolve before I started the
> 'hosted-engine --deploy'.
>
>> You might need to answer "Yes" to the /etc/hosts question..
>
> I did answer "Yes".
>
>
>> The log seems to get far enough along that it presents you the engine vm
>> console URL?  It looks like the issue is that the engine vm cannot
>> resolve
>> its own name.
>
> That is my take as well.
>
> Scratching my head as I config'ed dnsmasq to provide local dns and to read
> from /etc/hosts for hosted-engine-1.pcstrac.com.
>
> The only thing I think I flubbed was neglecting to add the host's IP to
> the host's /etc/resolv.conf.
>
> Scrubbing and staring again.
>
> Mark
>
>
>>
>> -derek
>>
>> On Wed, December 7, 2016 3:13 pm, Mark Steckel wrote:
>> > Folks,
>> >
>> > Thanks to Didi in another thread I'm making progress. (Lesson learned,
>> > choose 'disk' and not 'cdrom' when using the he-appliance.)
>> >
>> > So I reset to a fresh CentOS 7, installed various software packages
>> > including ovirt.
>> >
>> > I configed eth0 with a /32 public IP. I also added an alias for a
>> > x.x.x.1/29 on eth0:1.
>> >
>> > Finally I config'ed dnsmasq to provide both dhcp and dns (ensuring
>> that it
>> > will read from /etc/hosts before forwarding dns requests) and added
>> the
>> > IPs and hostsnames to /etc/hosts from the /29 IPs which are to be used
>> by
>> > the VMs.
>> >
>> > Things proceeded nicely till resolving the he vm fqdn. (I tested to
>> make
>> > sure that the he vm fqdm would resolve **Before** I ran 'hosted-engine
>> > --deploy'.)
>> >
>> >   |-   --== NETWORK CONFIGURATION ==--
>> >   |-
>> >   |- [ ERROR ] Host name is not valid:
>> hosted-engine-1.pcstrac.com
>> > did not resolve into an IP address
>> >   |- [ ERROR ] Failed to execute stage 'Environment
>> > customization': Host name is not valid:
>> > hosted-engine-1.pcstrac.com did not resolve into an IP address
>> >   |- [ INFO  ] Stage: Clean up
>> >   |-   Log file is located at
>> > /var/log/ovirt-engine/setup/ovirt-engine-setup-20161207193757-6i03xg.log
>> >   |- [ INFO  ] Generating answer file
>> > '/var/lib/ovirt-engine/setup/answers/20161207193758-setup.conf'
>> >   |- [ INFO  ] Stage: Pre-termination
>> >   |- [ INFO  ] Stage: Termination
>> >   |- [ ERROR ] Execution of setup failed
>> >   |- HE_APPLIANCE_ENGINE_SETUP_FAIL
>> > [ ERROR ] Engine setup failed on the appliance
>> > [ ERROR ] Failed to execute stage 'Closing up': Engine setup
>> failed on
>> > the appliance Please check its log on the appliance.
>> >
>> >
>> > The one thing I forgot is to update /etc/resolv.conf to include the
>> host
>> > though I don't know if this matters...
>> >
>> > Logs attached.
>> >
>> > I suspect I've very close to having this working but am admittedly
>> > stumped.
>> >
>> > Pointers appreciated.
>> >
>> > Thanks
>> > Mark
>> >
>> >
>> > ___
>> > Users mailing list
>> > Users@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
>> >
>>
>>
>> --
>>Derek Atkins 617-623-3745
>>de...@ihtfp.com www.ihtfp.com
>>Computer and Internet Security Consultant
>>
>
>


-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

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

Re: [ovirt-users] Single server hosted engine... almost there

[Mark Steckel]

Hi Derek,

- Derek Atkins  wrote:
> Hi Mark,
> 
> The error is correct, hosted-engine-1.pcstrac.com is not a valid hostname:
> 
> $ host hosted-engine-1.pcstrac.com
> $
> 
> I'm lost, tho -- was this an error that occurred on the host during
> hosted-engine --deploy, or was it an error that occurred in the hosted
> enging VM when running engine-setup?

I believe when it occurred when the running the engine-setup.


> If the former, you need to ensure that you have a real DNS name for your
> ovirt engine.  It's unclear (to me) that using /etc/hosts is sufficient.
> However looking at the logs, it looks like it can locally resolve (to
> xx.yy.18.122).

Yep. I tested things to make sure it could resolve before I started the 
'hosted-engine --deploy'.

> You might need to answer "Yes" to the /etc/hosts question..

I did answer "Yes".


> The log seems to get far enough along that it presents you the engine vm
> console URL?  It looks like the issue is that the engine vm cannot resolve
> its own name.

That is my take as well.

Scratching my head as I config'ed dnsmasq to provide local dns and to read from 
/etc/hosts for hosted-engine-1.pcstrac.com.

The only thing I think I flubbed was neglecting to add the host's IP to the 
host's /etc/resolv.conf.

Scrubbing and staring again. 

Mark


> 
> -derek
> 
> On Wed, December 7, 2016 3:13 pm, Mark Steckel wrote:
> > Folks,
> >
> > Thanks to Didi in another thread I'm making progress. (Lesson learned,
> > choose 'disk' and not 'cdrom' when using the he-appliance.)
> >
> > So I reset to a fresh CentOS 7, installed various software packages
> > including ovirt.
> >
> > I configed eth0 with a /32 public IP. I also added an alias for a
> > x.x.x.1/29 on eth0:1.
> >
> > Finally I config'ed dnsmasq to provide both dhcp and dns (ensuring that it
> > will read from /etc/hosts before forwarding dns requests) and added the
> > IPs and hostsnames to /etc/hosts from the /29 IPs which are to be used by
> > the VMs.
> >
> > Things proceeded nicely till resolving the he vm fqdn. (I tested to make
> > sure that the he vm fqdm would resolve **Before** I ran 'hosted-engine
> > --deploy'.)
> >
> >   |-   --== NETWORK CONFIGURATION ==--
> >   |-
> >   |- [ ERROR ] Host name is not valid: hosted-engine-1.pcstrac.com
> > did not resolve into an IP address
> >   |- [ ERROR ] Failed to execute stage 'Environment
> > customization': Host name is not valid:
> > hosted-engine-1.pcstrac.com did not resolve into an IP address
> >   |- [ INFO  ] Stage: Clean up
> >   |-   Log file is located at
> > /var/log/ovirt-engine/setup/ovirt-engine-setup-20161207193757-6i03xg.log
> >   |- [ INFO  ] Generating answer file
> > '/var/lib/ovirt-engine/setup/answers/20161207193758-setup.conf'
> >   |- [ INFO  ] Stage: Pre-termination
> >   |- [ INFO  ] Stage: Termination
> >   |- [ ERROR ] Execution of setup failed
> >   |- HE_APPLIANCE_ENGINE_SETUP_FAIL
> > [ ERROR ] Engine setup failed on the appliance
> > [ ERROR ] Failed to execute stage 'Closing up': Engine setup failed on
> > the appliance Please check its log on the appliance.
> >
> >
> > The one thing I forgot is to update /etc/resolv.conf to include the host
> > though I don't know if this matters...
> >
> > Logs attached.
> >
> > I suspect I've very close to having this working but am admittedly
> > stumped.
> >
> > Pointers appreciated.
> >
> > Thanks
> > Mark
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
> 
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> 

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

Re: [ovirt-users] Single server hosted engine... almost there

[Derek Atkins]

Hi Mark,

The error is correct, hosted-engine-1.pcstrac.com is not a valid hostname:

$ host hosted-engine-1.pcstrac.com
$

I'm lost, tho -- was this an error that occurred on the host during
hosted-engine --deploy, or was it an error that occurred in the hosted
enging VM when running engine-setup?

If the former, you need to ensure that you have a real DNS name for your
ovirt engine.  It's unclear (to me) that using /etc/hosts is sufficient.
However looking at the logs, it looks like it can locally resolve (to
xx.yy.18.122).

You might need to answer "Yes" to the /etc/hosts question..

The log seems to get far enough along that it presents you the engine vm
console URL?  It looks like the issue is that the engine vm cannot resolve
its own name.

-derek

On Wed, December 7, 2016 3:13 pm, Mark Steckel wrote:
> Folks,
>
> Thanks to Didi in another thread I'm making progress. (Lesson learned,
> choose 'disk' and not 'cdrom' when using the he-appliance.)
>
> So I reset to a fresh CentOS 7, installed various software packages
> including ovirt.
>
> I configed eth0 with a /32 public IP. I also added an alias for a
> x.x.x.1/29 on eth0:1.
>
> Finally I config'ed dnsmasq to provide both dhcp and dns (ensuring that it
> will read from /etc/hosts before forwarding dns requests) and added the
> IPs and hostsnames to /etc/hosts from the /29 IPs which are to be used by
> the VMs.
>
> Things proceeded nicely till resolving the he vm fqdn. (I tested to make
> sure that the he vm fqdm would resolve **Before** I ran 'hosted-engine
> --deploy'.)
>
>   |-   --== NETWORK CONFIGURATION ==--
>   |-
>   |- [ ERROR ] Host name is not valid: hosted-engine-1.pcstrac.com
> did not resolve into an IP address
>   |- [ ERROR ] Failed to execute stage 'Environment
> customization': Host name is not valid:
> hosted-engine-1.pcstrac.com did not resolve into an IP address
>   |- [ INFO  ] Stage: Clean up
>   |-   Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-setup-20161207193757-6i03xg.log
>   |- [ INFO  ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20161207193758-setup.conf'
>   |- [ INFO  ] Stage: Pre-termination
>   |- [ INFO  ] Stage: Termination
>   |- [ ERROR ] Execution of setup failed
>   |- HE_APPLIANCE_ENGINE_SETUP_FAIL
> [ ERROR ] Engine setup failed on the appliance
> [ ERROR ] Failed to execute stage 'Closing up': Engine setup failed on
> the appliance Please check its log on the appliance.
>
>
> The one thing I forgot is to update /etc/resolv.conf to include the host
> though I don't know if this matters...
>
> Logs attached.
>
> I suspect I've very close to having this working but am admittedly
> stumped.
>
> Pointers appreciated.
>
> Thanks
> Mark
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>


-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

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