Bug 1367581

Summary: [RFE] Add validation to RHV deployment to verify the discovered hosts are up and usable
Product: Red Hat Quickstart Cloud Installer Reporter: James Olin Oden <joden>
Component: Installation - RHEVAssignee: John Matthews <jmatthew>
Status: NEW --- QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact: Dan Macpherson <dmacpher>
Priority: unspecified    
Version: 1.0CC: bthurber, tcarlin
Target Milestone: ---Keywords: RFE, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1216188    
Bug Blocks:    

Description James Olin Oden 2016-08-16 20:52:37 UTC 
Description of problem:
I had a RHV deployment fail for a different reason.   I removed the storage of the old hosts, deleted the hosts from satellite, and completely removed their the host VMs.   However when I got to the host discovery in the RHV deployment these hosts still showed up.   I thought I knew which ones were gone, and which were the new ones, however I was wrong.   I picked the non-existent hosts, and then it took hours to finally timeout as it was waiting to contact the non-existent host.  In this case this was a self-hosted RHV deployment.

It could potentially save someone lots of time if in this case there was some validation to verify that the hosts were up and usable before the deployment began.

Version-Release number of selected component (if applicable):
QCI-1.0-RHEL-7-20160815.t.0

How reproducible:
Always

Steps to Reproduce:
1.  Start a deployment with some set of hosts.
2.  Stop the deployment
3.  Remove the hosts and their associated storage (including their VM's).
4.  Create new host VM's.
5.  Create a new deployment but select the old hosts in the discovery screen.
6.  Proceed with the deployment.

Actual results:
It will take a good long time timeout.

Expected results:
It not let you select those non-existant or non-booted hosts.
Comment 1 James Olin Oden 2016-08-16 20:55:37 UTC 
This PR was shown as a possible solution to this problem when it was discussed in IRC:  

   https://github.com/fusor/fusor/pull/925
Comment 2 John Matthews 2016-08-16 20:58:14 UTC 
Discussed in IRC and felt we could consider adding this kind of check to the deployment validation.

The check would be to do a basic sanity check on discovered hosts, verify they are reachable.

BZ 1216188 is closely related, that is filtering the list of discovered hosts to only those powered on.

We may want to do both:
 Filter for powered on
 Then also do a validation at deployment time.


Consider case of API deployment, BZ 1216188 is unlikely to help an API only deployment, but this RFE could help.
Comment 3 Sudhir Mallamprabhakara 2016-08-31 19:25:16 UTC 
*** Bug 1371999 has been marked as a duplicate of this bug. ***