© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Steps to recreate:
1. Create instance based on a flavor that includes swap on a Xen-based openstack installation.
2. See that in the database the instance has a BDM for swap at /dev/xvdb, but nothing for /dev/xvdc.
3. See that on the instance it has swap at /dev/xvdc, but nothing at /dev/xvdb.
4. Try to attach a volume at /dev/xvdb, but fail because the database has swap at /dev/xvdb.
5. Try to attach a volume at /dev/xvdc, but fail because the instance has swap at /dev/xvdc.
The above problem was introduced with http://
The below explanation is relative to a Nova Git commit as of today (and therefor won't changed).
A BDM for swap, based on the flavor, is created in nova/compute/api.py (pseudo call-stack: [1][2][3][4]), which is incorrectly (based on Xen and historical behavior) assigned to /dev/xvdb (pseudo call-stack: [5][6][
[1] https:/
[2] https:/
[3] https:/
[4] https:/
[5] https:/
[6] https:/
[7] https:/
[8] https:/
[9] https:/
[10] https:/
[11] https:/
[12] https:/
The swap is actually created in nova/virt/
[13] https:/
[14] https:/
[15] https:/