Hi Simone,
Sorry for my late reply. I've tried to attempt this all a few more times
on my own, and have gotten a bit further but am about ready to call it
quits. The last step I now get to is when the service httpd is
restarting. It fails right after that.
I tried to manually install httpd myself because it didn't appear to be
installed (I never saw it as a prerequisite) and then rerun the deployment
via the answer file, but I was never able to resume the deployment.
Unfortunately I have 4 logs now from retrying the deployment, however I am
fairly certain this is most important one:
Here are the others that most likely contain my attempts at resuming the
deployment, which probably won't be as useful:
Side note: the first log was done from a freshly imaged CentOS 7 machine.
If there's a better way to restart the deployment from scratch aside from
reinstalling the OS - please let me know! It takes a lot of time to get
everything back up and running again.
Thanks so much,
Jon
On Mon, Jun 19, 2017 at 4:04 AM, Simone Tiraboschi <stirabos(a)redhat.com>
wrote:
On Fri, Jun 16, 2017 at 5:00 AM, Jon Bornstein <
bornstein.jonathan(a)gmail.com> wrote:
> Thanks - makes sense.
>
> I've worked on this a bit more and have pushed a bit further, but from
> looking through my new log, it looks like the engine is error-ing out
> because my engine FQDN is cannot be resolved to an IP address.
>
> *The error: *
> [ ERROR ] Host name is not valid: *engine.example.rocks* did not resolve
> into an IP address
>
> *engine.example.rocks* is the FQDN I supplied when answering the
> following:
>
> Please provide the FQDN you would like to use for the engine appliance.
>> Note: This will be the FQDN of the engine VM you are now going to
>> launch.
>> It should not point to the base host or to any other existing machine.
>> Engine VM FQDN: (leave it empty to skip):
>
>
>
>
> *My /etc/hosts file: *
> 192.168.1.44 host.example.rocks host
> 192.168.1.45 engine.example.rocks engine
>
>
> I can see why it's erroring, but I'm not sure what I need to do now to
> get it working. The IP 192.168.1.45 is one I just made up, because the
> only system I have access to is the one I'm currently using (192.168.1.44)
>
Could you please share your hosted-engine-setup log file from the latest
attempt?
>
> Jon
>
> On Thu, Jun 15, 2017 at 12:01 PM, Simone Tiraboschi <stirabos(a)redhat.com>
> wrote:
>
>>
>>
>> On Thu, Jun 15, 2017 at 4:08 PM, Jon Bornstein <
>> bornstein.jonathan(a)gmail.com> wrote:
>>
>>> My lack of Linux proficiency is going to show here, but..
>>>
>>> I guess I'm a bit confused on how to correctly configure my network
>>> interface(s) for oVirt.
>>>
>>> I currently have two network interfaces:
>>>
>>> enp0s25 -
>>> This is my Ethernet interface, but it is unused. It currently is set
>>> to DHCP and has no IP address. However, it is the only interface that
>>> oVirt suggests I use when configuring which nic to set the bridge on.
>>>
>>> wlo1 -
>>> My wireless interface, and IS how i'm connecting to the internet. This
>>> is the IP address that I was using in my /etc/hosts file.
>>>
>>> Is it it not possible have a system that can run oVirt as well as
>>> maintain an internet connection?
>>>
>>>
>> oVirt by default works in bridge mode.
>> This means that is going to create a bridge on your hosts and the vnic
>> of your VMs will be connected to that bridge as well.
>>
>> oVirt is composed by a central engine managing physical hosts trough an
>> agent deployed on each host.
>> So the engine has to be able to reach the managed hosts, this happens
>> though what we call management network.
>>
>> hosted-engine is special deployment where for ha reasons the oVirt
>> engine is going to run on a VM hosted on the host that it's managing.
>> So, wrapping up, with hosted-engine setup you are going to create a VM
>> for the engine, the engine VM will have a nic on the management network and
>> this mean that you have a management bridge on your host.
>> The host has to have an address over the management network in order to
>> have the engine able to reach your host.
>>
>> That's why hosted-engine-setup is checking the address of the interface
>> you choose for the management network.
>>
>>
>>
>>>
>>> On Thu, Jun 15, 2017 at 9:02 AM, Simone Tiraboschi <stirabos(a)redhat.com
>>> > wrote:
>>>
>>>>
>>>>
>>>> On Thu, Jun 15, 2017 at 2:55 PM, Jon Bornstein <
>>>> bornstein.jonathan(a)gmail.com> wrote:
>>>>
>>>>> Hi Marton,
>>>>>
>>>>> Here is the log:
https://gist.github.com/a
>>>>> nonymous/ac777a70b8e8fc23016c0b6731f24706
>>>>>
>>>>
>>>>
>>>> You tried to create the management bridge over enp0s25 but it wasn't
>>>> configured with an IP address for your host.
>>>> Could you please configure it or choose a correctly configured
>>>> interface?
>>>>
>>>>
>>>> 2017-06-14 16:32:22 DEBUG otopi.plugins.gr_he_common.vm.cloud_init
>>>> cloud_init._getMyIPAddress:115 Acquiring 'enp0s25' address
>>>> 2017-06-14 16:32:22 DEBUG otopi.plugins.gr_he_common.vm.cloud_init
>>>> plugin.executeRaw:813 execute: ('/sbin/ip', 'addr',
'show', 'enp0s25'),
>>>> executable='None', cwd='None', env=None
>>>> 2017-06-14 16:32:22 DEBUG otopi.plugins.gr_he_common.vm.cloud_init
>>>> plugin.executeRaw:863 execute-result: ('/sbin/ip',
'addr', 'show',
>>>> 'enp0s25'), rc=0
>>>> 2017-06-14 16:32:22 DEBUG otopi.plugins.gr_he_common.vm.cloud_init
>>>> plugin.execute:921 execute-output: ('/sbin/ip', 'addr',
'show', 'enp0s25')
>>>> stdout:
>>>> 2: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
>>>> pfifo_fast state DOWN qlen 1000
>>>> link/ether c4:34:6b:26:6a:d1 brd ff:ff:ff:ff:ff:ff
>>>>
>>>> 2017-06-14 16:32:22 DEBUG otopi.plugins.gr_he_common.vm.cloud_init
>>>> plugin.execute:926 execute-output: ('/sbin/ip', 'addr',
'show', 'enp0s25')
>>>> stderr:
>>>>
>>>>
>>>> 2017-06-14 16:32:22 DEBUG otopi.plugins.gr_he_common.vm.cloud_init
>>>> cloud_init._getMyIPAddress:132 address: None
>>>> 2017-06-14 16:32:22 DEBUG otopi.context context._executeMethod:142
>>>> method exception
>>>> Traceback (most recent call last):
>>>> File "/usr/lib/python2.7/site-packages/otopi/context.py",
line 132,
>>>> in _executeMethod
>>>> method['method']()
>>>> File
"/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/vm/cloud_init.py",
>>>> line 781, in _customize_vm_networking
>>>> self._customize_vm_addressing()
>>>> File
"/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/vm/cloud_init.py",
>>>> line 215, in _customize_vm_addressing
>>>> my_ip = self._getMyIPAddress()
>>>> File
"/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/vm/cloud_init.py",
>>>> line 136, in _getMyIPAddress
>>>> _('Cannot acquire nic/bridge address')
>>>> RuntimeError: Cannot acquire nic/bridge address
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> On Thu, Jun 15, 2017 at 4:13 AM, Maton, Brett <
>>>>> matonb(a)ltresources.co.uk> wrote:
>>>>>
>>>>>> Hi Jon,
>>>>>>
>>>>>> There will be people on this list far more able to help you
than I
>>>>>> can, but the contents of the engine setup log
(/var/log/ovirt-hosted-engine-
>>>>>> setup/ovirt-hosted-engine-setup-20170614160653-2vuu7h.log) would
>>>>>> help
>>>>>>
>>>>>> On 14 June 2017 at 21:56, Jon Bornstein <
>>>>>> bornstein.jonathan(a)gmail.com> wrote:
>>>>>>
>>>>>>> This is roughly my 10th attempt at installing some version of
oVirt
>>>>>>> and I think where I get stuck every time is with the
networking aspect.
>>>>>>>
>>>>>>> I'm simply trying to test out oVirt on an old laptop wiht
16GB RAM
>>>>>>> and an external HDD. I'm connected via WiFi.
>>>>>>>
>>>>>>> After failing 100 times with the regular ovirt engine, It
was
>>>>>>> recommended I try the self-hosted engine.
>>>>>>>
>>>>>>> **
>>>>>>>
>>>>>>> Anyway, here are the contents of my /etc/hosts file:
>>>>>>> 127.0.0.1 localhost localhost.localdomain localhost4
>>>>>>> localhost4.localdomain4
>>>>>>> ::1 localhost localhost.localdomain localhost6
>>>>>>> localhost6.localdomain6
>>>>>>> 10.114.13.144 host.example.rocks host
>>>>>>> 10.114.13.145 engine.example.rocks engine
>>>>>>>
>>>>>>> **
>>>>>>>
>>>>>>> After running hosted-engine --deploy, I get to the prompt
below in
>>>>>>> which the installer fails afterwards:
>>>>>>>
>>>>>>> You may specify a unicast MAC address for the VM or accept a
>>>>>>> randomly generated default [00:16:3e:5b:3a:73]:
>>>>>>>
>>>>>>> [ ERROR ] Failed to execute stage 'Environment
customization':
>>>>>>> Cannot acquire nic/bridge address
>>>>>>> [ INFO ] Stage: Clean up
>>>>>>> [ INFO ] Generating answer file
'/var/lib/ovirt-hosted-engine-
>>>>>>> setup/answers/answers-20170614163222.conf'
>>>>>>> [ INFO ] Stage: Pre-termination
>>>>>>> [ INFO ] Stage: Termination
>>>>>>> [ ERROR ] Hosted Engine deployment failed
>>>>>>> Log file is located at
/var/log/ovirt-hosted-engine-s
>>>>>>> etup/ovirt-hosted-engine-setup-20170614160653-2vuu7h.log
>>>>>>>
>>>>>>> **
>>>>>>>
>>>>>>> Here is a tail of the log:
>>>>>>>
>>>>>>> [root@engine /]# tail /var/log/ovirt-hosted-engine-s
>>>>>>> etup/ovirt-hosted-engine-setup-20170614160653-2vuu7h.log
>>>>>>> 2017-06-14 16:32:22 DEBUG otopi.context
context._executeMethod:134
>>>>>>> condition False
>>>>>>> 2017-06-14 16:32:22 INFO otopi.context
context.runSequence:687
>>>>>>> Stage: Termination
>>>>>>> 2017-06-14 16:32:22 DEBUG otopi.context
context.runSequence:691
>>>>>>> STAGE terminate
>>>>>>> 2017-06-14 16:32:22 DEBUG otopi.context
context._executeMethod:128
>>>>>>> Stage terminate METHOD otopi.plugins.gr_he_common.cor
>>>>>>> e.misc.Plugin._terminate
>>>>>>> 2017-06-14 16:32:22 ERROR
otopi.plugins.gr_he_common.core.misc
>>>>>>> misc._terminate:178 Hosted Engine deployment failed
>>>>>>> 2017-06-14 16:32:22 DEBUG otopi.plugins.otopi.dialog.human
>>>>>>> dialog.__logString:204 DIALOG:SEND Log file
is located at
>>>>>>> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup
>>>>>>> -20170614160653-2vuu7h.log
>>>>>>> 2017-06-14 16:32:22 DEBUG otopi.context
context._executeMethod:128
>>>>>>> Stage terminate METHOD otopi.plugins.otopi.dialog.hum
>>>>>>> an.Plugin._terminate
>>>>>>> 2017-06-14 16:32:22 DEBUG otopi.context
context._executeMethod:128
>>>>>>> Stage terminate METHOD otopi.plugins.otopi.dialog.mac
>>>>>>> hine.Plugin._terminate
>>>>>>> 2017-06-14 16:32:22 DEBUG otopi.context
context._executeMethod:134
>>>>>>> condition False
>>>>>>> 2017-06-14 16:32:22 DEBUG otopi.context
context._executeMethod:128
>>>>>>> Stage terminate METHOD otopi.plugins.otopi.core.log.P
>>>>>>> lugin._terminate
>>>>>>>
>>>>>>> **
>>>>>>>
>>>>>>> This is my first time writing to this list, so hopefully
I'm doing
>>>>>>> it right. Thanks in advance - this is driving me crazy!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Users mailing list
>>>>>>> Users(a)ovirt.org
>>>>>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users(a)ovirt.org
>>>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>>>
>>>>>
>>>>
>>>
>>
>