Bug 1223667

Summary: When using 'tripleo wait_for' with the command 'nova hypervisor-stats' it hangs forever
Product: [Community] RDO Reporter: Udi Kalifon <ukalifon>
Component: openstack-tripleoAssignee: James Slagle <jslagle>
Status: CLOSED EOL QA Contact: Shai Revivo <srevivo>
Severity: high Docs Contact:
Priority: unspecified    
Version: trunk   
Target Milestone: ---   
Target Release: Kilo   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-19 15:39:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Udi Kalifon 2015-05-21 07:49:13 UTC
Description of problem:
I am trying to install on bare metals. I successfully registered and discovered my nodes, and now I am at the stage where I run the overcloud deployment. The instack-deploy-overcloud script times out on this line:

tripleo wait_for 180 1 wait_for_hypervisor_stats $expected_nodes $expected_memory $expected_vcpus

When I run 'nova hypervisor-stats' manually it doesn't hang, and when I run '/usr/libexec/openstack-tripleo/wait_for_hypervisor_stats 2 65536 24' like the script does it also works fine. Only when calling 'tripleo wait_for 180 1 wait_for_hypervisor_stats 2 65536 24' like the script does it hangs...

WORKAROUND: I changed my instackenv.json and set the memory, disk and number of cpus to 0. After re-registering the nodes I could start a deployment.


Version-Release number of selected component (if applicable):
instack-0.0.6-1.el7ost.noarch
instack-undercloud-2.1.1-dev14.el7.centos.noarch


How reproducible:
100%


Steps to Reproduce:
1. Install on bare metals
2. Register nodes using an instackenv.json file like in my example: http://file.tlv.redhat.com/~ukalifon/instackenv.json
3. Discover nodes
4. start a deployment with "instack-deploy-overcloud --tuskar"
 

Actual results:
The deploy script hangs right on the beginning

Comment 3 Chandan Kumar 2016-05-19 15:39:43 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.