Public bug reported: This is a followup to the regression reported in https://bugs.launchpad.net/nova/+bug/1464239 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. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1478065 Title: Block device metadata may be bogus with Ironic driver Status in OpenStack Compute (nova): New Bug description: This is a followup to the regression reported in https://bugs.launchpad.net/nova/+bug/1464239 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. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1478065/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp