Bug 1256752 - Cannot import nodes from multiple files that share an IPMI IP
Summary: Cannot import nodes from multiple files that share an IPMI IP
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 10.0 (Newton)
Assignee: Angus Thomas
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-25 12:03 UTC by Ryan Brown
Modified: 2023-09-14 03:04 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-22 11:10:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.