Bug 1256752

Summary:	Cannot import nodes from multiple files that share an IPMI IP
Product:	Red Hat OpenStack	Reporter:	Ryan Brown <rybrown>
Component:	rhosp-director	Assignee:	Angus Thomas <athomas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Arik Chernetsky <achernet>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	apevec, dbecker, dtantsur, hbrock, lhh, mburns, morazi, rhel-osp-director-maint, rybrown
Target Milestone:	---
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-22 11:10:53 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 Ryan Brown 2015-08-25 12:03:31 UTC

Description of problem:
I encountered this problem when trying to import HP Moonshot nodes. Importing a single node [moonshot-solo.json) succeeded, and I attempted to import a second file (moonshot-all.json) but the second import failed.

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. Make two inventory JSON files, with one IPMI-bridged node in each
2. Import the first JSON file
3. Attempt to import the second

Actual results:
Exception due to the nodes in the second file sharing an IPMI IP address with an existing ironic node. When importing all nodes in a single file, this works fine and they are allowed to share IPs. 

Expected results:
Import all the nodes

Additional info:
It may be valuable to validate that nodes sharing an IPMI address have a MAC address present, or that they have IPMI bridging information (once that's supported in instackenv.json).

Comment 5 Mike Burns 2016-04-07 20:47:27 UTC

This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 7 Lucas Alvares Gomes 2016-05-19 10:14:21 UTC

How was the files being imported? 

I'm afraid this bug should be against the tooling that helps with enrolling nodes in Ironic because Ironic does not natively support importing nodes from files.

Comment 8 Dmitry Tantsur 2016-05-19 10:16:51 UTC

There are 2 problems here: with importing and with introspection. I believe both are fixed, could you please check it?

Comment 10 Dmitry Tantsur 2016-08-22 11:10:53 UTC

Closing as fixed, until proved otherwise :)

Comment 11 Red Hat Bugzilla 2023-09-14 03:04:13 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days