Ask Your Question

Persistent Boot Volume from CLI [closed]

asked 2018-09-19 07:46:43 -0500

jkrah gravatar image

Hi guys, Ive create a volume based off the cirros image with the following command..

volume create --image cirros --size 10 volboot

And from horizon I can successfully start an instance based of this volume.. I'm just a lttle stuck on how to do it from the CLI.. Im running "centos-release-openstack-queens" .. and have read somewhere that this old syntax is deprecated..

 --block-device source=volume,id=volboot,dest=volume,size=10,shutdown=preserve,bootindex=0

So Im now trying.. .

--block-device-mapping vda=volboot:volume:10:false

But my instances wont start..

(openstack) server create --volume volboot --flavor m1.small --block-device-mapping vda=volboot --key-name jkkey --nic net-id=dmz-net1 --wait pers01  
Error creating server: pers01
Error creating server

In /var/log/nova/nova-compute.log it seems to be complaining ..

fe4ca08 - default default] Couldn't find iscsi sessions because iscsiadm err: iscsiadm: No active sessions.
: libvirtError: internal error: qemu unexpectedly closed the monitor: 2018-09-19T12:32:14.658201Z qemu-kvm: -drive file=/dev/sda,format=raw,if=none,id=drive-virtio-disk0,serial=b4f16154-f277-441c-b4c0-86456edde4da,cache=none,aio=native: 'serial' is deprecated, please use the corresponding option of '-device' instead
2018-09-19 22:32:18.998 1421 WARNING os_brick.initiator.connectors.iscsi [req-3215b049-f577-46ab-bac6-5886c0af0d9e 6da09935e104459da638bc8d590f5bda 7920780309f34695a70fc5a37fe4ca08 - default default] Couldn't find iSCSI nodes because iscsiadm err: iscsiadm: No records found

I was hoping someone might be able to confirm I am using the correct syntack in the CLI to start my instance.. Thanks in advance..

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by jkrah
close date 2018-09-20 03:30:58.933719

1 answer

Sort by » oldest newest most voted

answered 2018-09-19 08:36:53 -0500

updated 2018-09-19 08:38:14 -0500

While I can’t say anything about the errors, the --volume option includes block mapping. In other words, all you need to do is removing the block-device-mapping option:

server create --volume volboot --flavor m1.small --key-name jkkey --nic net-id=dmz-net1 --wait pers01
edit flag offensive delete link more


Thanks so much Bernd .. works like a charm.. I should have thought to try that :-)

jkrah gravatar imagejkrah ( 2018-09-20 03:30:31 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2018-09-19 07:46:43 -0500

Seen: 701 times

Last updated: Sep 19 '18