Well, if all you guys say this is not a bug, it's not a bug. But it's
sadly that Nova cannot guarantee device names even in this simple case.
** Changed in: nova
Status: New => Invalid
** Changed in: nova
Assignee: Feodor Tersin (ftersin) => (unassigned)
--
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/1489442
Title:
Invalid order of volumes with adding a volume in boot operation
Status in OpenStack Compute (nova):
Invalid
Bug description:
If an image has several volume in bdm, and a user adds one more volume
for boot operation, then the new volume is not just added to a volume
list, but becomes the second device. This can lead to problems if the
image root device has various soft which settings point to other
volumes.
For example:
1 the image is a snapshot of a volume backed instance which had vda and vdb
volumes
2 the instance had an sql server, which used both vda and vdb for its database
3 if a user runs a new instance from the image, either device names are
restored (with xen), or they're reassigned (libvirt) to the same names, because
the order of devices, which are passed in libvirt, is the same as it was for
the original instance
4 if a user runs a new instance, adding a new volume, the volume list becomes
vda, new, vdb
5 in this case libvirt reassings device names to vda=vda, new=vdb, vdb=vdc
6 as a result the sql server will not find its data on vdb
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1489442/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
