Bug 1198821

Summary: instack-undercloud: "Polling discoverd for discovery results" stage gets stuck.
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: instack-undercloudAssignee: Alexander Chuzhoy <sasha>
Status: CLOSED ERRATA QA Contact: Alexander Chuzhoy <sasha>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: calfonso, mburns, rhel-osp-director-maint, rrosa, sclewis, yeylon
Target Milestone: gaKeywords: TestOnly, Triaged
Target Release: Director   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:50:42 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 Alexander Chuzhoy 2015-03-04 21:30:38 UTC
instack-undercloud: "Polling discoverd for discovery results" stage gets stuck.

Environment:
instack-0.0.6.4-g57c723a.el7.centos.noarch
instack-undercloud-2.0.0-dev1399.g710b7c1.el7.centos.noarch


Steps to reproduce:
1. instack-ironic-deployment --nodes-json instackenv.json --register-nodes 
2. instack-ironic-deployment --discover-nodes


Result:
The discovery gets stuck:

   Polling discoverd for discovery results ...                                               
       Result for node 04b84cc6-6778-4ac5-9378-9244c9e87d09 is ... DISCOVERED.               
       Result for node 3e0bfaff-c7aa-4323-a1f2-274791c0480d is ... DISCOVERED.               
       Result for node 9fb5794c-f23e-4860-8f80-fd0f1b085c1a is ...  


Expected result:
All the nodes should be discovered without getting stuck.


The W/A is to login to the hypervisor and to turn off the baremetal_X instance that's running.

Comment 4 Alexander Chuzhoy 2015-06-01 20:59:00 UTC
Verified:
instack-0.0.6-5.el7ost.noarch
instack-undercloud-2.1.0-3.el7ost.noarch

The reported issue doesn't reproduce.

Comment 8 errata-xmlrpc 2015-08-05 13:50:42 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-2015:1549