Block Device Mapping is Invalid (first instance with volume))

asked 2014-10-27 10:18:12 -0600

98 ●21 ●26 ●35

updated 2014-10-27 10:19:31 -0600

hi people, i want create a instance like physical pc and install some os!

I try to run my first instance with volume, but i'm occurred in this error "Block Device Mapping is Invalid" if i do this operation from dashboard.

This is the log file cinder.conf if i try to attached a preexisting volume the operation failed. if i try to run

cinder volume-create --displayname myTEST 1

the image is created without error

I have tried when run nova boot whit

--block-device source=image,id=id_image_in_glance,dest=volume,size=15,shutdown=preserve,bootindex=0

but the problem is the same! Some idea?

thanks at all

edit retag flag offensive close merge delete

Comments

I believe in IceHouse the command to succeed is :-

  $ nova boot --flavor 2  --key_name oskey1 --block-device  \
    source=image,id=f20-glance-image-id ,dest=volume,size=5,shutdown=preserve,bootindex=0 VF20RS012

dbaxps ( 2014-10-27 10:34:13 -0600 )edit

Volume will be created automatically, don't prepare cinder volume. No pre-existing volume needed

dbaxps ( 2014-10-27 10:38:41 -0600 )edit

whats is f20-glance-image-id? the normal id of my image?

your sintax is wrong, but thanks :)

New-stack ( 2014-10-27 10:49:47 -0600 )edit

Yes, it is normal id of corresponding glance image && I fixed syntax.

dbaxps ( 2014-10-27 10:56:59 -0600 )edit

thank's... I try to run your command on controller node, but i get this error

ERROR: It is not allowed to create an interface on external network ....

I suppose which nova need to set --nic = id_demo_network, but i have the same error "Block Device Mapping is Invalid."

New-stack ( 2014-10-27 11:26:10 -0600 )edit

see more comments

0

answered 2016-04-02 01:59:36 -0600

rackerstacker
26 ●1 ●3 ●4

Facing similar issue with Liberty. I am unable to attach an existing volume to an existing VM instance. Here is the error i get: [root@controller-01 logs]# nova boot --flavor rhel6.medium --key-name mykey --block-device-mapping vda=f78f46ed-aed6-48ba-bcaf-ea75a717a3be:::0 boot-from-vol-test ERROR (BadRequest): Block Device Mapping is Invalid: failed to get volume f78f46ed-aed6-48ba-bcaf-ea75a717a3be. (HTTP 400) (Request-ID: req-4486ebae-2bc0-48c3-9d8b-29ced20c9261)

Any support will be helpful

Thanks

edit flag offensive delete link

add a comment

0

answered 2014-10-27 11:29:22 -0600

dbaxps

10788 ●57 ●112 ●224 http://bderzhavets.blo...

Option for launching new instance 'boot from image (creates a new volume)'  works fine via dashboard.
No pre-existing volume is needed

edit flag offensive delete link

Comments

thanks, but in my case i receive the error.... some idea about?

New-stack ( 2014-10-27 11:41:12 -0600 )edit

What is your backend for Cinder ? Is it thin LVM ?

dbaxps ( 2014-10-27 11:43:11 -0600 )edit

yes, i suppose... i followed the installation guide where at this step i set in /etc/lvm/lvm.conf the following row

filter = [ "a/.*/","a/sdb/" ]

and the result of fdisk -l is here

New-stack ( 2014-10-28 05:07:14 -0600 )edit

Try create volume via image and boot from this volume. Does it work ?

dbaxps ( 2014-10-28 05:11:18 -0600 )edit

Please, run vgs also.

dbaxps ( 2014-10-28 05:20:39 -0600 )edit

see more comments

Block Device Mapping is Invalid (first instance with volume))

Comments

2 answers

Comments

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

Block Device Mapping is Invalid (first instance with volume)) edit

Comments

2 answers

Comments

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

Block Device Mapping is Invalid (first instance with volume))