tripleo

Fencing generation fails with complex NIC setups

Bug #1666989 reported by Chris Jones
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
High
Chris Jones

Bug Description

The current fencing generation code tries to naively identify nodes by MAC address, but in testing this has proven to be insufficient on realistic hardware setups.
Identification via Ironic node name seems to be much more reliable.

Chris Jones (cmsj)
Changed in tripleo:
status: New → Confirmed
importance: Undecided → Medium
importance: Medium → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/437029

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-common (stable/ocata)

Change abandoned by Chris Jones (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/437029
Reason: Apologies Emilien, your point is particularly relevant here since I did need to push a new revision to the master fix.

Changed in tripleo:
status: Confirmed → In Progress
Emilien Macchi (emilienm)
Changed in tripleo:
milestone: none → pike-1
no longer affects: tripleo/ocata
Revision history for this message
Chris Jones (cmsj) wrote :

(this actually turned out to be an issue with incorrect data in instackenv.json)

Changed in tripleo:
status: In Progress → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-common (master)

Change abandoned by Chris Jones (<email address hidden>) on branch: master
Review: https://review.openstack.org/436932
Reason: this didn't actually help as intended.

Steven Hardy (shardy)
Changed in tripleo:
milestone: pike-1 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.