[RFE] Check duplicate nodes associated with the same BMC
Bug #1549664 reported by
Zhenguo Niu
This bug report is a duplicate of:
Bug #1519605: [RFE] Check for duplicates when enrolling a node.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
As I understand, one BMC should only be associated to one ironic node, but currently we can enroll any node with the BMC information which already used by another node, then assume node-A is deployed, and the new enrolled node-B becomes 'available' after node verifying, that means node-A can be override if a new nova boot request schedules to node-B, it's unacceptable.
I plan to add some check during node verifying process, then we can enroll a duplicate node but it can't be available.
Changed in ironic: | |
assignee: | nobody → Zhenguo Niu (niu-zglinux) |
description: | updated |
summary: |
- Different nodes can associate the same physical BMC + [RFE]Different nodes can associate the same physical BMC |
summary: |
- [RFE]Different nodes can associate the same physical BMC + [RFE] Check duplicate nodes associated with the same BMC |
Changed in ironic: | |
assignee: | Zhenguo Niu (niu-zglinux) → nobody |
status: | In Progress → Confirmed |
To post a comment you must log in.
This is a good call, but it's not as easy as it may seem, cause e.g. with IPMI bridging several nodes will have the same IPMI address. So maybe we should leave this check up to driver. Meaning this bug is actually an RFE.