Re: [ovirt-users] HostedEngine Deployment Woes

From: "Jiri Moskovcak" <jmoskovc(a)redhat.com&gt; To: "Mikola Rose" <mrose(a)power-soft.com&gt;, "Yedidyah Bar David" <didi(a)redhat.com&gt; Cc: users(a)ovirt.org Sent: Monday, January 5, 2015 10:09:00 AM Subject: Re: [ovirt-users] HostedEngine Deployment Woes On 01/02/2015 11:27 PM, Mikola Rose wrote: > Hi Didi, > > Thank you for the response. > > I have tried to do a fresh install (RH 6.6) and still ran into the same > problem. > > [root@pws-hv15 rhiso]# hosted-engine --deploy > [ INFO ] Stage: Initializing > Continuing will configure this host for serving as hypervisor > and create a VM where you have to install oVirt Engine afterwards. > Are you sure you want to continue? (Yes, No)[Yes]: > It has been detected that this program is executed through an > SSH connection without using screen. > Continuing with the installation may lead to broken > installation if the network connection fails. > It is highly recommended to abort the installation and run it > inside a screen session using command "screen". > Do you want to continue anyway? (Yes, No)[No]: yes > [ INFO ] Generating a temporary VNC password. > [ INFO ] Stage: Environment setup > Configuration files: [] > Log file: > /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20150102134318-7ougjc.log > Version: otopi-1.2.3 (otopi-1.2.3-1.el6ev) > [ INFO ] Hardware supports virtualization > [ INFO ] Bridge rhevm already created > [ INFO ] Stage: Environment packages setup > [ INFO ] Stage: Programs detection > [ INFO ] Stage: Environment setup > [ INFO ] Stage: Environment customization > > > --== STORAGE CONFIGURATION ==-- > > > During customization use CTRL-D to abort. > Please specify the storage you would like to use (nfs3, > nfs4)[nfs3]: > Please specify the full shared storage connection path to use > (example: host:/path): 192.168.1.32:/Volumes/Raid1 > [ INFO ] Installing on first host > Please provide storage domain name. [hosted_storage]: > Local storage datacenter name is an internal name and > currently will not be shown in engine's admin UI.Please enter local > datacenter name [hosted_datacenter]: > > > --== SYSTEM CONFIGURATION ==-- > > > > --== NETWORK CONFIGURATION ==-- > > > iptables was detected on your computer, do you wish setup to > configure it? (Yes, No)[Yes]: > Please indicate a pingable gateway IP address [192.168.0.3]: > > > --== VM CONFIGURATION ==-- > > > Please specify the device to boot the VM from (cdrom, disk, > pxe) [cdrom]: > The following CPU types are supported by this host: > - model_Westmere: Intel Westmere Family > - model_Nehalem: Intel Nehalem Family > - model_Penryn: Intel Penryn Family > - model_Conroe: Intel Conroe Family > Please specify the CPU type to be used by the VM > [model_Westmere]: > Please specify path to installation media you would like to > use [None]: /mnt/rhiso > Please specify the number of virtual CPUs for the VM > [Defaults to minimum requirement: 2]: > Please specify the disk size of the VM in GB [Defaults to > minimum requirement: 25]: > You may specify a MAC address for the VM or accept a randomly > generated default [00:16:3e:02:7f:c4]: > Please specify the memory size of the VM in MB [Defaults to > minimum requirement: 4096]: > Please specify the console type you would like to use to > connect to the VM (vnc, spice) [vnc]: > > > --== HOSTED ENGINE CONFIGURATION ==-- > > > Enter the name which will be used to identify this host > inside the Administrator Portal [hosted_engine_1]: > Enter 'admin@internal' user password that will be used for > accessing the Administrator Portal: > Confirm 'admin@internal' user password: > Please provide the FQDN for the engine you would like to use. > This needs to match the FQDN that you will use for the engine > installation within the VM. > Note: This will be the FQDN of the VM you are now going to > create, > it should not point to the base host or to any other existing > machine. > Engine FQDN: powerhost1.power-soft.net > <http://powerhost1.power-soft.net> > Please provide the name of the SMTP server through which we > will send notifications [localhost]: > Please provide the TCP port number of the SMTP server [25]: > Please provide the email address from which notifications > will be sent [root@localhost]: > Please provide a comma-separated list of email addresses > which will get notifications [root@localhost]: > [ INFO ] Stage: Setup validation > > > --== CONFIGURATION PREVIEW ==-- > > > Engine FQDN : > powerhost1.power-soft.net <http://powerhost1.power-soft.net> > Bridge name : rhevm > SSH daemon port : 22 > Firewall manager : iptables > Gateway address : 192.168.0.3 > Host name for web application : hosted_engine_1 > Host ID : 1 > Image size GB : 25 > Storage connection : 192.168.1.32:/Volumes/Raid1 > Console type : vnc > Memory size MB : 4096 > MAC address : 00:16:3e:02:7f:c4 > Boot type : cdrom > Number of CPUs : 2 > ISO image (for cdrom boot) : /mnt/rhiso > CPU Type : model_Westmere > > > Please confirm installation settings (Yes, No)[No]: Yes > [ INFO ] Stage: Transaction setup > [ INFO ] Stage: Misc configuration > [ INFO ] Stage: Package installation > [ INFO ] Stage: Misc configuration > [ INFO ] Configuring libvirt > [ INFO ] Configuring VDSM > [ INFO ] Starting vdsmd > [ INFO ] Waiting for VDSM hardware info > [ INFO ] Waiting for VDSM hardware info > [ INFO ] Waiting for VDSM hardware info > [ INFO ] Waiting for VDSM hardware info > [ INFO ] Creating Storage Domain > [ INFO ] Creating Storage Pool > [ INFO ] Connecting Storage Pool > [ INFO ] Verifying sanlock lockspace initialization > [ INFO ] Initializing sanlock lockspace > [ INFO ] Initializing sanlock metadata > [ INFO ] Creating VM Image > [ INFO ] Disconnecting Storage Pool > [ INFO ] Start monitoring domain > [ ERROR ] Failed to execute stage 'Misc configuration': The read > operation timed out > [ INFO ] Stage: Clean up > [ INFO ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf' > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > > > > sanlock status > daemon 4a21a439-cc72-4542-8146-71d0cb754da4.pws-hv15.p > p -1 helper > p -1 listener > p -1 status > p 5365 > s > e7175b6e-bf5a-4723-98f6-0f7972623f4c:1:/rhev/data-center/mnt/192.168.1.32\:_Volumes_Raid1/e7175b6e-bf5a-4723-98f6-0f7972623f4c/dom_md/ids:0 > > > > I am not sure if it is relevant but after subscribing to the relevant > channels listed in the Installation Guid > <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtuali... > I was receiving an error when trying to update via Yum and only after I > installed rhel-6-server-rhev-mgmt-agent-rpms. I have no idea why it > would want to install the i686 augeas items and can not find any info on > how to resolve this. This usually means that you either using broken repo or you have installed some 3rd party packages which require different version of the libs then others (btw, augeas-1.0.0-5.el6_5.1 doesn't seem like clean 6.6 install, the package version suggests it's 6.5). You can try to update the system before you add any 3rd party repos. Now for the read timeout problem: The vdsm log is full of: Thread-62::DEBUG::2015-01-02 14:07:44,218::fileSD::261::Storage.Misc.excCmd::(getReadDelay) SUCCESS: <err> = '0+1 records in\n0+1 records out\n480 bytes (480 B) copied, 0.000351466 s, 1.4 MB/s\n'; <rc> = 0 Thread-62::DEBUG::2015-01-02 14:07:54,228::fileSD::261::Storage.Misc.excCmd::(getReadDelay) '/bin/dd if=/rhev/data-center/mnt/192.168.1.32:_Volumes_Raid1/e7175b6e-bf5a-4723-98f6-0f7972623f4c/dom_md/metadata iflag=direct of=/dev/null bs=40 96 count=1' (cwd None) repeating over and over which doesn't seem healthy to me, but I'm not vdsm expert. Can you please try to run: vdsClient -s 0 getVdsStats on the host you're deploying?