Block device metadata may be bogus with Ironic driver

Bug #1478065 reported by Ben Nemec on 2015-07-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)

Bug Description

This is a followup to the regression reported in The problem there was that Nova changed how it does block device mapping for ephemeral partitions, and because Ironic isn't using that block device mapping the ephemeral path returned by the metadata server became incorrect. I'm opening this bug because while it is possible to fix the regression, the behavior is still bad. The ephemeral partition metadata is only valid if Ironic happens to assign the ephemeral partition to /dev/sda1. This is often the case, but there are valid situations where it is not true - consider deploying to a vm where the ephemeral partition ends up on /dev/vda1.

Since I believe this would require a new method of synchronizing the block device mapping between Nova and Ironic, I'm pushing a fix for the regression to unbreak the previously working cases, and opening this bug to document that the situation is still not right.

tags: added: block-device-mapping ironic
Matt Riedemann (mriedem) wrote :

Looks like this is the proposed change:

Michael Davies (mrda) wrote :

Pinged Ben on IRC, to see if we can assign this one to him as well since the patch addresses most (all?) of this.

melanie witt (melwitt) on 2015-09-04
Changed in nova:
importance: Undecided → Medium
status: New → Confirmed
John L. Villalovos (happycamp) wrote :

mrda and I pinged bnemec on IRC:

He thinks his patch does not fix all cases affected by this bug.

Change abandoned by Ben Nemec (<email address hidden>) on branch: master
Reason: Yeah, I keep telling myself I'll come back to this, but at this point I think that's pretty clearly a lie. :-)

I'll restore if I get a chance to revisit it.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers