Created attachment 938389 [details] logs Description of problem: After yum install ovirt-hosted-engine-setup, screen hosted-engine --deploy fails (I get out of screen, so don't know much). Log file does seem to have an exception. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.2.0-0.1.master.20140908073913.git480e272.fc20.noarch How reproducible: Happened 1/1. Steps to Reproduce: 1. yum install ovirt-hosted-engine-setup 2. screen hosted-engine --deploy Went through the entire process. Chose iscsi target, anything that COULD be default WAS default other than iscsi and boot (set to PXE). Verified the settings I chose. Actual results: Found myself out of screen. Looking at the logs found and exception. Couldn't find an IP assignment/VM creation in the logs. Expected results: Get an IP assignment for the VM and see it in the output. Additional info: I don't think this is related in any way, but just to be sure: I had troubles with FQDN, got errors that there's no IP. I finally added '10.10.10.10 hosted-engine.host' to /etc/hosts while deploying. Then I could get on with it.
(In reply to Vered Volansky from comment #0) > Created attachment 938389 [details] > logs > > Description of problem: > After yum install ovirt-hosted-engine-setup, screen hosted-engine --deploy > fails (I get out of screen, so don't know much). Log file does seem to have > an exception. > > Version-Release number of selected component (if applicable): > ovirt-hosted-engine-setup-1.2.0-0.1.master.20140908073913.git480e272.fc20. > noarch > > How reproducible: > Happened 1/1. > > Steps to Reproduce: > 1. yum install ovirt-hosted-engine-setup > 2. screen hosted-engine --deploy > > Went through the entire process. > Chose iscsi target, anything that COULD be default WAS default other than > iscsi and boot (set to PXE). > Verified the settings I chose. > > Actual results: > Found myself out of screen. > Looking at the logs found and exception. Couldn't find an IP assignment/VM > creation in the logs. > > Expected results: > Get an IP assignment for the VM and see it in the output. I'm not sure what you're expecting here. 1) Have your network a DHCP configured and running? 2) Did you setup the OS inside the VM configuring the NIC for using DHCP and being enabled on boot? > > Additional info: > I don't think this is related in any way, but just to be sure: > I had troubles with FQDN, got errors that there's no IP. > I finally added '10.10.10.10 hosted-engine.host' to /etc/hosts while > deploying. Then I could get on with it. Other than that, I can see in your logs: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 935, in _misc self._storagePoolConnection() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 583, in _storagePoolConnection raise RuntimeError(message) RuntimeError: Wrong Master domain or its version: 'SD=24a36e43-8244-4b1b-9d58-8a72fab451d8, pool=d7bb1d90-29a0-47b3-bde8-d4758b408de0' 2014-09-17 11:15:52 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Misc configuration': Wrong Master domain or its version: 'SD=24a36e43-8244-4b1b-9d58-8a72fab451d8, pool=d7bb1d90-29a0-47b3-bde8-d4758b408de0' which is a storage issue and should be addressed in a separate BZ, please open one for it.
Changing the subject accordingly to expected results.
> I'm not sure what you're expecting here. > 1) Have your network a DHCP configured and running? > 2) Did you setup the OS inside the VM configuring the NIC for using DHCP and > being enabled on boot? Well, actually, like I said, I just blinked and was out of screen. Maybe I should have said that I expect the process to complete successfully. I wasn't able to configue anything since I hadn't got any output from the command. Maybe I should have expected it not to fail... Anyway, I never did get to successfully deploy a hosted engine, so I didn't really know what to expect. > which is a storage issue and should be addressed in a separate BZ, please > open one for it. Ack.
Dropping 1144797 from blockers, having the ip of the vm displayed shouldn't block the solution of a storage issue.
Just noting that the common way to run deploy inside screen is 1. screen 2. In the shell that opens inside screen 'hosted-engine --deploy' So that if it fails you do not loose the output.
We simply rely on the FQDN, no really need to show the engine VM IP