Bug 1186662 - Can't deploy on bare metal machines, provisioning state is "wait call-back"
Summary: Can't deploy on bare metal machines, provisioning state is "wait call-back"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 6.0 (Juno)
Assignee: Lucas Alvares Gomes
QA Contact: Toure Dunnon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-28 09:28 UTC by Udi Kalifon
Modified: 2015-06-15 19:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Technology Preview
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-15 19:20:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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"
Note You need to log in before you can comment on or make changes to this bug.