Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1186662

Summary: Can't deploy on bare metal machines, provisioning state is "wait call-back"
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: openstack-ironicAssignee: Lucas Alvares Gomes <lmartins>
Status: CLOSED CURRENTRELEASE QA Contact: Toure Dunnon <tdunnon>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0 (Juno)CC: calfonso, kbasil, yeylon
Target Milestone: ---Keywords: TechPreview, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Technology Preview
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-15 19:20:09 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-01-28 09:28:00 UTC
Description of problem:
When registering 2 servers and trying to make a deployment with 1 controller and 1 compute, both roles don't deploy.


Version-Release number of selected component (if applicable):
openstack-ironic-common-2014.2-3.el7ost.noarch
openstack-ironic-discoverd-0.2.5-1.el7ost.noarch
openstack-ironic-api-2014.2-3.el7ost.noarch
python-ironicclient-0.3.1-1.el7ost.noarch
openstack-ironic-conductor-2014.2-3.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Install TripleO on a physical machine with its own network (to avoid dhcp problems in the lab)
2. Register 2 other physical servers, and provide their parameters so they will skip the discovery and go immediately to the "Free" nodes (this is to work around a bug where they get stuck in "discovering" state)
3. Make a deployment of 1 controller and 1 compute only


Actual results:
ironic node-list shows 1 node stuck in "wait call-back" and another in "None"