Bug 1489001
| Summary: | nova boot --block-device-mapping wrong order | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Eduardo Minguez <eminguez> |
| Component: | python-novaclient | Assignee: | Eoghan Glynn <eglynn> |
| Status: | CLOSED NOTABUG | QA Contact: | Joe H. Rahme <jhakimra> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 10.0 (Newton) | CC: | berrange, dasmith, eglynn, jruzicka, kchamart, mbooth, sbauza, sferdjao, sgordon, srevivo, vromanso |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-09-08 11:12:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Eduardo Minguez
2017-09-06 14:57:02 UTC
(In reply to Eduardo Minguez from comment #0) Sorry, copy & paste issues... When it says "master-0-*" it is "master-1-*" > 2. blkid1=$(openstack volume show master-0-docker -f value -c id) > 3. blkid2=$(openstack volume show master-0-etcd -f value -c id) > 4. blkid3=$(openstack volume show master-0-openshift-local -f value -c id) Using --block-device to create the volume at boot time seems to work tho: $ nova boot --flavor m1.medium --image rhel7 --key-name ocp3kp --user-data ./user-data/master-1.yaml --security-groups master-sg,node-sg --block-device source=blank,dest=volume,device=vdb,size=25,shutdown=preserve --block-device source=blank,dest=volume,device=vdc,size=20,shutdown=preserve --block-device source=blank,dest=volume,device=vdd,size=30,shutdown=preserve --nic net-id=$netid1 master-1.$domain ... $ openstack volume list +--------------------------------------+------------------------------------------------+--------+------+-----------------------------------------------------------+ | ID | Display Name | Status | Size | Attached to | +--------------------------------------+------------------------------------------------+--------+------+-----------------------------------------------------------+ | 924dc148-5b57-4bdf-8740-232c832fc81a | 36be1cb7-cbd6-4092-b1fe-fb57e4cbaf0d-blank-vol | in-use | 30 | Attached to master-1.control.edu.example.com on /dev/vdd | | a5dc0736-7967-46fe-ac42-25aef97e9066 | 36be1cb7-cbd6-4092-b1fe-fb57e4cbaf0d-blank-vol | in-use | 20 | Attached to master-1.control.edu.example.com on /dev/vdc | | ff220008-e07d-4664-ac65-40e4cb917abe | 36be1cb7-cbd6-4092-b1fe-fb57e4cbaf0d-blank-vol | in-use | 25 | Attached to master-1.control.edu.example.com on /dev/vdb | +--------------------------------------+------------------------------------------------+--------+------+-----------------------------------------------------------+ For an array of reasons Nova doesn't make any guarantees about the order that devices are presented to the guest. The order can even change within the lifecycle of the instance, for example across a reboot. Similarly Linux doesn't even make any guarantees about the order devices presented to the guest are presented to the user. Relying on this is never going to be robust. This problem is fixed in OSP10 onwards with device tagging: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/networking_guide/use-tagging It also supports vifs, which have a similar issue. |