Bug 1415822 - RHV self hosted deployment fails during ansible task [self_hosted_first_host : Execute hosted-engine setup] Failed to execute stage 'Environment setup': Cannot setup Hosted Engine with other VMs running
Summary: RHV self hosted deployment fails during ansible task [self_hosted_first_host ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: Installation - RHEV
Version: 1.1
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: ---
: 1.1
Assignee: Derek Whatley
QA Contact: Tasos Papaioannou
Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-23 20:02 UTC by Landon LaSmith
Modified: 2020-05-14 15:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-28 01:45:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Deployment logs (15.22 MB, application/zip)
2017-01-23 20:02 UTC, Landon LaSmith
no flags Details
self-hosted engine yum update output (47.53 KB, text/plain)
2017-01-30 14:39 UTC, Derek Whatley
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:0335 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.1 2017-02-28 06:36:13 UTC

Description Landon LaSmith 2017-01-23 20:02:25 UTC
Created attachment 1243756 [details]
Deployment logs

Description of problem: During a clean deployment of RHV self hosted, the deployment fails during the ansible task 
[self_hosted_first_host : Execute hosted-engine setup] with the error below

[ INFO  ] Stage: Initializing                                                                                         
[ INFO  ] Generating a temporary VNC password.                                                                        
[ INFO  ] Stage: Environment setup                                                                                    
          During customization use CTRL-D to abort.                                                                   
[ INFO  ] Hardware supports virtualization                                                                            
          Configuration files: ['/etc/qci//answers']                                                                  
          Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170123133110-h66rr6.log            
          Version: otopi-1.5.2 (otopi-1.5.2-1.el7ev)                                                                  
[ INFO  ] Stage: Environment packages setup                                                                           
[ INFO  ] Stage: Programs detection                                                                                   
[ INFO  ] Stage: Environment setup                                                                                    
[WARNING] Cannot locate gluster packages, Hyper Converged setup support will be disabled.                             
[ INFO  ] Please abort the setup and install vdsm-gluster, gluster-server >= 3.7.2 and restart vdsmd service in order 
to gain Hyper Converged setup support.                                                                                
[ ERROR ] The following VMs have been found: 26e0c0b5-431c-4b39-b90c-b60ad4a6c093                                     
[ ERROR ] Failed to execute stage 'Environment setup': Cannot setup Hosted Engine with other VMs running              
[ INFO  ] Stage: Clean up                                                                                             
[ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20170123133121.conf'             
[ INFO  ] Stage: Pre-termination                                                                                      
[ INFO  ] Stage: Termination                                                                                          
[ ERROR ] Hosted Engine deployment failed                                                                             
Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170123133110-h66rr6.log


QCI Media Version: QCI-1.1-RHEL-7-20170120.t.0

How reproducible: A few occurrences during automated runs

Steps to Reproduce:
1. Install QCI from ISO
2. Start a RHV selfhosted deployment

Actual results: RHV deployment fails during hosted engine setup


Expected results: RHV deployment foreman task succeeds in setting up the hosted engine VM

Comment 2 Fabian von Feilitzsch 2017-01-27 16:44:45 UTC
Just to note, it seems the "other VMs detected" issue is actually due to fusor repeatedly + automatically retrying the ansible-ovirt deployment. The original error that caused the failure comes after the engine VM has been successfully set up (hence the vm detection in future runs):

[ INFO  ] Engine-setup successfully completed 
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ INFO  ] Engine is still not reachable, waiting...
[ INFO  ] Engine is still unreachable
[ ERROR ] Engine is still not reachable
[ ERROR ] Failed to execute stage 'Closing up': Engine is still not reachable
[ INFO  ] Stage: Clean up
[ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20170123113113.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Hosted Engine deployment failed: this system is not reliable, please check the issue,fix and redeploy
          Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170123105043-kvzx84.log

It seems the engine VM fails to come back up after being launched, though I don't yet see any reason for that to happen.

Comment 3 Derek Whatley 2017-01-30 14:39:13 UTC
Created attachment 1245909 [details]
self-hosted engine yum update output

Issue may be related to self-hosted engine being updated via `yum update` command  during VM bringup.

Comment 4 Derek Whatley 2017-01-30 20:17:30 UTC
Moved self-hosted engine provisioning from cloud-init to Ansible.

https://github.com/fusor/ansible-ovirt/pull/23
https://github.com/fusor/fusor/pull/1289

Comment 5 Dylan Murray 2017-01-30 21:14:43 UTC
This fix is in QCI-1.1-RHEL-7-20170130.t.0.

Comment 6 Tasos Papaioannou 2017-01-31 21:41:19 UTC
Verified on QCI-1.1-RHEL-7-20170130.t.0.

Comment 8 errata-xmlrpc 2017-02-28 01:45:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:0335


Note You need to log in before you can comment on or make changes to this bug.