Bug 1210023

Summary: instack-ironic-deployment --nodes-json instackenv.json --register-nodes fails
Product: [Community] RDO Reporter: wes hayutin <whayutin>
Component: rdo-managerAssignee: James Slagle <jslagle>
Status: CLOSED CURRENTRELEASE QA Contact: yeylon <yeylon>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: trunkCC: jslagle, mburns, srevivo
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-03-30 23:00:14 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:
Attachments:
Description Flags
logs bzip2 none

Description wes hayutin 2015-04-08 17:13:03 UTC
Created attachment 1012322 [details]
logs bzip2

Description of problem:

instack-ironic-deployment --nodes-json instackenv.json --register-nodes fails

Details:
[stack@localhost ~]$ source /home/stack/stackrc; instack-ironic-deployment --nodes-json instackenv.json --register-nodes -x
/usr/lib/python2.7/site-packages/keystoneclient/shell.py:65: DeprecationWarning: The keystone CLI is deprecated in favor of python-openstackclient. For a Python library, continue using python-keystoneclient.
  'python-keystoneclient.', DeprecationWarning)
+ STDERR=/dev/stderr
+ shift 1
+ true
+ case "$1" in
+ shift
+ break
+ echo 'Preparing for deployment...'
Preparing for deployment...
+ '[' 1 = 1 ']'
+ register_nodes
+ NODES_JSON=instackenv.json
+ NULL_STATS=0
+ tmp_json=instackenv.json
+ '[' 0 = 1 ']'
+ echo '  Registering nodes from instackenv.json'
  Registering nodes from instackenv.json
+ register-nodes --service-host undercloud --nodes /dev/fd/63
++ jq .nodes instackenv.json
[stack@localhost ~]$ echo $?
1

Comment 2 James Slagle 2015-04-08 17:42:25 UTC
delorean trunk-mgt was pulling an old version of the ironic package b/c the commit hash is the same between 2 packaging changes. I forced and ironic package rebuild with a newer commit hash, so it should be fixed now.