Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Yngvi Páll Þorfinnsson]

Can anyone advise on or provide a documentation for Octavia installation ?

Rgds
Yngvi


-Original Message-
From: Yngvi Páll Þorfinnsson 
Sent: 23. júní 2016 15:42
To: Turbo Fredriksson ; openstack@lists.openstack.org
Subject: Re: [Openstack] Create instance fails on creating block device - Block 
Device Mapping is Invalid

I think it's possible we're far away from the correct path ;-) It's not 
mentioned at all in the openstack lbaas V2 documentation, but I think it's 
necessary to install Octavia on the controller machine first.
Then configure neutron on all compute nodes to support lbaas ...
Someone please correct me, if I'm wrong on this

Cheers
Yngvi

-Original Message-
From: Turbo Fredriksson [mailto:tu...@bayour.com]
Sent: 23. júní 2016 13:36
To: openstack@lists.openstack.org
Subject: Re: [Openstack] Create instance fails on creating block device - Block 
Device Mapping is Invalid

On Jun 23, 2016, at 2:10 PM, Turbo Fredriksson wrote:

> But even after disabling them, they're still show as 
> "status=disabled,state=up"
> with a "cinder service-list".. ?

I tried anyway, but creating a volume (empty or from an image) gave the host 
field as empty. And the status was Error!

So apparently I need to figure out a way to configure "local storage".


The LVM volume shows:

- s n i p -
bladeA01b:~# openstack volume show test | grep host
| os-vol-host-attr:host | bladeA01b@lvm#LVM_iSCSI |
- s n i p -
--
Build a man a fire, and he will be warm for the night.
Set a man on fire and he will be warm for the rest of his life.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

On Jun 23, 2016, at 4:30 PM, Eugen Block wrote:

> They are running because you didn't stop the services, you just disabled them.

I kind'a expected a disable to stop the service.. But what if I wanted to
stop only ONE service (of several)? For example the "nfs" backend but leave
the "lvm" online. I can't shutdown cinder-volume, that would stop all of them..

> You could stop them for now if you don't intend using cinder until you get an 
> instance up and running, but I would take care of cinder after that. It 
> doesn't affect you if you while trying to boot an instance on local storage 
> because cinder is not required for that.

Well. I can create Cinder volumes without any problems it seems:

bladeA01b:~# openstack volume list
+--+--+---+--+-+
| ID   | Display Name | Status| Size | 
Attached to |
+--+--+---+--+-+
| 0a0929e6-cf4d-40b3-9ba3-9575290993e6 | test2| available |5 |  
   |
| c16975ad-dd45-41d7-b0a9-cbd0849f80e4 | test | available |5 |  
   |
+--+--+---+--+-+
bladeA01b:~# openstack volume show test | grep host
| os-vol-host-attr:host  | bladeA01b@lvm#LVM_iSCSI
bladeA01b:~# openstack volume show test2 | grep host
| os-vol-host-attr:host  | bladeA01b@nfs#nfsbackend

> From your latest logs I assume that you are still trying to boot from volume, 
> I recommend to ignore cinder for now and focus on launching an instance at 
> all.

That doesn't seem to be possible. I've looked over some of the code for
Cinder, and if you don't configure "enabled_backends", then no volume
can be created. Well, they can be created, but they end up in Error state
right away!

> Have you fixed your glance issue?

I don't know. I don't know what's wrong with it :(


But I touch one thing and two other things break :( :( :(. Dang, dang, dang,
I'm getting really tired of this s**t!

- s n i p -
2016-06-23 17:00:21.511 18347 INFO cinder.api.openstack.wsgi 
[req-35b7eb35-997c-4149-a975-aba921d86182 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd03aa23 - - -] HTTP exception thrown: Volume test2 
could not be found.
2016-06-23 17:00:21.513 18347 INFO cinder.api.openstack.wsgi 
[req-35b7eb35-997c-4149-a975-aba921d86182 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd03aa23 - - -] 
http://10.0.4.1:8776/v2/2985b96e27f048cd92a18db0dd03aa23/volumes/test2 returned 
with HTTP 404
2016-06-23 17:00:21.514 18347 INFO eventlet.wsgi.server 
[req-35b7eb35-997c-4149-a975-aba921d86182 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd03aa23 - - -] 10.0.4.1 "GET 
/v2/2985b96e27f048cd92a18db0dd03aa23/volumes/test2 HTTP/1.1" status: 404  len: 
419 time: 0.6278081
2016-06-23 17:00:21.524 18347 INFO cinder.api.openstack.wsgi 
[req-a37ee53f-6910-4411-8260-dd615a722318 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd03aa23 - - -] GET 
http://10.0.4.1:8776/v2/2985b96e27f048cd92a18db0dd03aa23/volumes/detail?all_tenants=1&name=test2
2016-06-23 17:00:21.600 18347 INFO cinder.volume.api 
[req-a37ee53f-6910-4411-8260-dd615a722318 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd03aa23 - - -] Get all volumes completed successfully.
2016-06-23 17:00:21.609 18347 INFO cinder.api.openstack.wsgi 
[req-a37ee53f-6910-4411-8260-dd615a722318 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd03aa23 - - -] 
http://10.0.4.1:8776/v2/2985b96e27f048cd92a18db0dd03aa23/volumes/detail?all_tenants=1&name=test2
 returned with HTTP 200
2016-06-23 17:00:21.611 18347 INFO eventlet.wsgi.server 
[req-a37ee53f-6910-4411-8260-dd615a722318 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd03aa23 - - -] 10.0.4.1 "GET 
/v2/2985b96e27f048cd92a18db0dd03aa23/volumes/detail?all_tenants=1&name=test2 
HTTP/1.1" status: 200  len: 1607 time: 0.0912130
- s n i p -

And yet it's right there! See top of email.
--
Att inse sin egen betydelse är som att få ett kvalster att
fatta att han bara syns i mikroskop
- Arne Anka


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Yngvi Páll Þorfinnsson]

I think it's possible we're far away from the correct path ;-)
It's not mentioned at all in the openstack lbaas V2 documentation, 
but I think it's necessary to install Octavia on the controller machine first.
Then configure neutron on all compute nodes to support lbaas ...
Someone please correct me, if I'm wrong on this

Cheers 
Yngvi

-Original Message-
From: Turbo Fredriksson [mailto:tu...@bayour.com] 
Sent: 23. júní 2016 13:36
To: openstack@lists.openstack.org
Subject: Re: [Openstack] Create instance fails on creating block device - Block 
Device Mapping is Invalid

On Jun 23, 2016, at 2:10 PM, Turbo Fredriksson wrote:

> But even after disabling them, they're still show as 
> "status=disabled,state=up"
> with a "cinder service-list".. ?

I tried anyway, but creating a volume (empty or from an image) gave the host 
field as empty. And the status was Error!

So apparently I need to figure out a way to configure "local storage".


The LVM volume shows:

- s n i p -
bladeA01b:~# openstack volume show test | grep host
| os-vol-host-attr:host | bladeA01b@lvm#LVM_iSCSI |
- s n i p -
--
Build a man a fire, and he will be warm for the night.
Set a man on fire and he will be warm for the rest of his life.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Eugen Block]

"rbd"?


It's a different storage backend, something like a network RAID. But  
don't mind it right now ;-)


But even after disabling them, they're still show as  
"status=disabled,state=up"


They are running because you didn't stop the services, you just  
disabled them. You could stop them for now if you don't intend using  
cinder until you get an instance up and running, but I would take care  
of cinder after that. It doesn't affect you if you while trying to  
boot an instance on local storage because cinder is not required for  
that.


From your latest logs I assume that you are still trying to boot from  
volume, I recommend to ignore cinder for now and focus on launching an  
instance at all. Have you fixed your glance issue? Because that is  
required, otherwise it won't work at all.



Zitat von Turbo Fredriksson :


On Jun 23, 2016, at 12:26 PM, Eugen Block wrote:

/etc/cinder/cinder.conf:enabled_backends = rbd--> that's what I  
use currently


"rbd"?

I'm not sure if it would work, it's been a while since I used local  
storage, but if you just comment the enabled_backend option out and  
restart cinder services, I believe it would create local volumes.


Shouldn't it be enough just to "disable" those services/backends?

I guess I have to, because just commenting that out didn't help, they still
show as enabled and running.

But even after disabling them, they're still show as  
"status=disabled,state=up"

with a "cinder service-list".. ?

Ok, that's different! I'm not running Glance on my Compute, only  
on my Control.


Glance is not supposed to run on a compute node, it runs on a control node.


Ok, good! I thought I missed something fundamental.


What's the output of "openstack endpoint list | grep glance"?


| 57b10556b7bf47eaa019c603a0f6b34f | europe-london | glance | image  
| True | public   | http://10.0.4.1:9292
| 8672f6de1673470d93ab6ccee1c1a2bb | europe-london | glance | image  
| True | internal | http://10.0.4.1:9292
| e45c3e83fe744e7db949cdd89dfe5654 | europe-london | glance | image  
| True | admin| http://10.0.4.1:9292


That's the Control node..


[waited a little while]


How long did you wait?


10-15 seconds perhaps. At least less than (half?) a minute..

 "This section describes how to install and configure the Image  
service, code-named glance, on the controller node."


It is not obvious from that that that (!! :) should only be done on the
Controller! It just say "do this on the controller". It does not make it
clear that you shouldn't do something on the compute as well.

"This section describes how to install and configure the Compute  
service, code-named nova, on the controller node."
"This section describes how to install and configure the Compute  
service on a compute node."


Neither of which distinguish the different parts - what if I
have/want a separate compute and control node? It does not
make things obvious!


And that's why I have a problem with HOWTOs! They _assume_ to much.
And a _BAD_ HOWTO (which all of them on Openstack are!) doesn't even
attempt to explain the different options you have, so if you deviate
even the very slightest, you're f**ked!

There's a _HUMONGOS_ difference between a "HOWTO" and "Documentation"!

Timeout problem? Make sure that nothing blocks the requests  
(proxy?), what response do you get if you execute

control1:~ # curl http://:9292


I was doing that ON the Control. Worked just fine.

And The Control and Compute is on the same switch.
--
Det är när man känner doften av sin egen avföring
som man börjar undra vem man egentligen är.
- Arne Anka


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

I'm starting to think that it might have something to do with the
networking after all:

- s n i p -
2016-06-23 15:52:13.775 25419 DEBUG nova.compute.manager 
[req-87a08e39-96ac-4c23-96dd-5227c972b865 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd
03aa23 - - -] [instance: d75bd127-c554-4d79-bb9e-157c752628f4] Instance 
network_info: |[VIF({'profile': {}, 'ovs_interfaceid': 
u'9c23c0b8-1e96-4e73-b048-55c73
80b2425', 'preserve_on_delete': False, 'network': Network({'bridge': 
'br-provider', 'subnets': [Subnet({'ips': [FixedIP({'meta': {}, 'version': 4, 
'type': 'fi
xed', 'floating_ips': [], 'address': u'10.99.0.4'})], 'version': 4, 'meta': 
{'dhcp_server': u'10.99.0.2'}, 'dns': [IP({'meta': {}, 'version': 4, 'type': 
'dns'
, 'address': u'10.0.0.254'})], 'routes': [], 'cidr': u'10.99.0.0/24', 
'gateway': IP({'meta': {}, 'version': 4, 'type': 'gateway', 'address': 
u'10.99.0.1'})})]
, 'meta': {'injected': False, 'tenant_id': u'2985b96e27f048cd92a18db0dd03aa23', 
'mtu': 1458}, 'id': u'2bb7b8e2-188f-4e46-bf4d-ef5ec81ddb4d', 'label': u'networ
k-99'}), 'devname': u'tap9c23c0b8-1e', 'vnic_type': u'normal', 'qbh_params': 
None, 'meta': {}, 'details': {u'port_filter': True, u'ovs_hybrid_plug': True}, 
'a
ddress': u'fa:16:3e:4c:04:17', 'active': False, 'type': u'ovs', 'id': 
u'9c23c0b8-1e96-4e73-b048-55c7380b2425', 'qbg_params': None})]| 
_allocate_network_async
/usr/lib/python2.7/dist-packages/nova/compute/manager.py:1572
2016-06-23 15:52:13.776 25419 DEBUG nova.compute.claims 
[req-87a08e39-96ac-4c23-96dd-5227c972b865 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd0
3aa23 - - -] [instance: d75bd127-c554-4d79-bb9e-157c752628f4] Aborting claim: 
[Claim: 1024 MB memory, 5 GB disk] abort /usr/lib/python2.7/dist-packages/nova/c
ompute/claims.py:120
2016-06-23 15:52:13.777 25419 DEBUG oslo_concurrency.lockutils 
[req-87a08e39-96ac-4c23-96dd-5227c972b865 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a1
8db0dd03aa23 - - -] Lock "compute_resources" acquired by 
"nova.compute.resource_tracker.abort_instance_claim" :: waited 0.000s inner 
/usr/lib/python2.7/dist-p
ackages/oslo_concurrency/lockutils.py:273
2016-06-23 15:52:14.017 25419 DEBUG oslo_concurrency.lockutils 
[req-87a08e39-96ac-4c23-96dd-5227c972b865 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a1
8db0dd03aa23 - - -] Lock "compute_resources" released by 
"nova.compute.resource_tracker.abort_instance_claim" :: held 0.240s inner 
/usr/lib/python2.7/dist-pac
kages/oslo_concurrency/lockutils.py:285
2016-06-23 15:52:14.018 25419 DEBUG nova.compute.manager 
[req-87a08e39-96ac-4c23-96dd-5227c972b865 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd
03aa23 - - -] [instance: d75bd127-c554-4d79-bb9e-157c752628f4] Build of 
instance d75bd127-c554-4d79-bb9e-157c752628f4 aborted: Block Device Mapping is 
Invalid
. _build_and_run_instance 
/usr/lib/python2.7/dist-packages/nova/compute/manager.py:2081
2016-06-23 15:52:14.019 25419 DEBUG nova.compute.utils 
[req-87a08e39-96ac-4c23-96dd-5227c972b865 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd03
aa23 - - -] [instance: d75bd127-c554-4d79-bb9e-157c752628f4] Build of instance 
d75bd127-c554-4d79-bb9e-157c752628f4 aborted: Block Device Mapping is Invalid.
notify_about_instance_usage 
/usr/lib/python2.7/dist-packages/nova/compute/utils.py:284
2016-06-23 15:52:14.020 25419 ERROR nova.compute.manager 
[req-87a08e39-96ac-4c23-96dd-5227c972b865 0b7e5b0653084efdad5d67b66f2cf949 
2985b96e27f048cd92a18db0dd03aa23 - - -] [instance: 
d75bd127-c554-4d79-bb9e-157c752628f4] Build of instance 
d75bd127-c554-4d79-bb9e-157c752628f4 aborted: Block Device Mapping is Invalid.
- s n i p -
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

On Jun 23, 2016, at 2:10 PM, Turbo Fredriksson wrote:

> But even after disabling them, they're still show as 
> "status=disabled,state=up"
> with a "cinder service-list".. ?

I tried anyway, but creating a volume (empty or from an image) gave
the host field as empty. And the status was Error!

So apparently I need to figure out a way to configure "local storage".


The LVM volume shows:

- s n i p -
bladeA01b:~# openstack volume show test | grep host
| os-vol-host-attr:host | bladeA01b@lvm#LVM_iSCSI |
- s n i p -
--
Build a man a fire, and he will be warm for the night.
Set a man on fire and he will be warm for the rest of his life.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

On Jun 23, 2016, at 12:26 PM, Eugen Block wrote:

> /etc/cinder/cinder.conf:enabled_backends = rbd--> that's what I use 
> currently

"rbd"?

> I'm not sure if it would work, it's been a while since I used local storage, 
> but if you just comment the enabled_backend option out and restart cinder 
> services, I believe it would create local volumes.

Shouldn't it be enough just to "disable" those services/backends?

I guess I have to, because just commenting that out didn't help, they still
show as enabled and running.

But even after disabling them, they're still show as "status=disabled,state=up"
with a "cinder service-list".. ?

>> Ok, that's different! I'm not running Glance on my Compute, only on my 
>> Control.
> 
> Glance is not supposed to run on a compute node, it runs on a control node.

Ok, good! I thought I missed something fundamental.

> What's the output of "openstack endpoint list | grep glance"?

| 57b10556b7bf47eaa019c603a0f6b34f | europe-london | glance | image | True | 
public   | http://10.0.4.1:9292
| 8672f6de1673470d93ab6ccee1c1a2bb | europe-london | glance | image | True | 
internal | http://10.0.4.1:9292
| e45c3e83fe744e7db949cdd89dfe5654 | europe-london | glance | image | True | 
admin| http://10.0.4.1:9292

That's the Control node..

>> [waited a little while]
> 
> How long did you wait?

10-15 seconds perhaps. At least less than (half?) a minute..

>  "This section describes how to install and configure the Image service, 
> code-named glance, on the controller node."

It is not obvious from that that that (!! :) should only be done on the
Controller! It just say "do this on the controller". It does not make it
clear that you shouldn't do something on the compute as well.

> "This section describes how to install and configure the Compute service, 
> code-named nova, on the controller node."
> "This section describes how to install and configure the Compute service on a 
> compute node."

Neither of which distinguish the different parts - what if I
have/want a separate compute and control node? It does not
make things obvious!


And that's why I have a problem with HOWTOs! They _assume_ to much.
And a _BAD_ HOWTO (which all of them on Openstack are!) doesn't even
attempt to explain the different options you have, so if you deviate
even the very slightest, you're f**ked!

There's a _HUMONGOS_ difference between a "HOWTO" and "Documentation"!

> Timeout problem? Make sure that nothing blocks the requests (proxy?), what 
> response do you get if you execute
> control1:~ # curl http://:9292

I was doing that ON the Control. Worked just fine.

And The Control and Compute is on the same switch.
-- 
Det är när man känner doften av sin egen avföring
som man börjar undra vem man egentligen är.
- Arne Anka


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Eugen Block]

How can I create a local volume?


You have probably configured your cinder.conf to use lvm as backend:

control1:~ # grep -r enabled_backends /etc/cinder/
/etc/cinder/cinder.conf:#enabled_backends = lvm
/etc/cinder/cinder.conf:enabled_backends = rbd--> that's what I  
use currently


I'm not sure if it would work, it's been a while since I used local  
storage, but if you just comment the enabled_backend option out and  
restart cinder services, I believe it would create local volumes. But  
still, I would postpone volumes for now if you want to bring an  
instance up at all and try to get nova to work with glance.


Ok, that's different! I'm not running Glance on my Compute, only on  
my Control.


Glance is not supposed to run on a compute node, it runs on a control  
node. Reading the error message it seems that you have configured your  
glance host as it tries to connect, but do you also have configured  
the endpoints according to  
http://docs.openstack.org/draft/install-guide-debconf/debconf/debconf-api-endpoints.html? What's the output of "openstack endpoint list | grep  
glance"?



[waited a little while]


How long did you wait? Timeout problem? Make sure that nothing blocks  
the requests (proxy?), what response do you get if you execute

control1:~ # curl http://:9292


Which of these should I run on the Compute and which one on the Control?


On top of every "install and configure" page there is a statement  
where to install the required services, for example the glance page  
says:


  "This section describes how to install and configure the Image  
service, code-named glance, on the controller node."


Or if you continue to the compute service, which has several  
components, it differs between control and compute node:


"This section describes how to install and configure the Compute  
service, code-named nova, on the controller node."


and

"This section describes how to install and configure the Compute  
service on a compute node."


Now, this might be a stupid question, but it actually only occurred  
to me just now

when I looking at that missing net error.


I don't think this should be a problem if you have at least a subnet  
assigned to the network, which is true in your case. I just tested  
that, the instance boots into a newly created network without any  
further configuration. So in your case it's the missing connection to  
glance, if you fix that we'll see what's next ;-)



Zitat von Turbo Fredriksson :

Now that my authentication problems seems to be fixed, it's back on  
track with

trying to boot my first instance..

On Jun 21, 2016, at 3:17 PM, Cynthia Lopes wrote:


If not, the command is: openstack volume create --size (size in GB) --image
(image name or id) volume_name



Just for info the cinder command was not exact, it should be: cinder create
--image*-id * *--display-name*  


Thanx.


I agree with Eugen that you should make sure you can create a volume and
attach to a VM to help understand what your problem is.


Ok, so I created an empty, bootable volume. Worked just fine it seems.

I then used that when creating the instance (from Horizon).

Still the same error - Block Device Mapping is Invalid.

- s n i p -
bladeA01b:~# openstack volume list
+--+--+---+--+-+
| ID   | Display Name | Status|  
Size | Attached to |

+--+--+---+--+-+
| c16975ad-dd45-41d7-b0a9-cbd0849f80e4 | test | available |   
  5 | |

+--+--+---+--+-+
bladeA01b:~# openstack volume show test
++--+
| Field  | Value|
++--+
| attachments| []   |
| availability_zone  | nova |
| bootable   | true |
| consistencygroup_id| None |
| created_at | 2016-06-22T20:48:31.00   |
| description|  |
| encrypted  | False|
| id | c16975ad-dd45-41d7-b0a9-cbd0849f80e4 |
| migration_status   | None |
| multiattach| False|
| name   | test |
| os-vol-host-attr:host  | bladeA01b@lvm#LVM_iSCSI  |
| os-vol-mig-status-attr:migstat | None |
| os-vol-mig-status-attr:name_id | None 

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

Now that my authentication problems seems to be fixed, it's back on track with
trying to boot my first instance..

On Jun 21, 2016, at 3:17 PM, Cynthia Lopes wrote:

> If not, the command is: openstack volume create --size (size in GB) --image
> (image name or id) volume_name

> Just for info the cinder command was not exact, it should be: cinder create
> --image*-id * *--display-name*  

Thanx.

> I agree with Eugen that you should make sure you can create a volume and
> attach to a VM to help understand what your problem is.

Ok, so I created an empty, bootable volume. Worked just fine it seems.

I then used that when creating the instance (from Horizon).

Still the same error - Block Device Mapping is Invalid.

- s n i p -
bladeA01b:~# openstack volume list
+--+--+---+--+-+
| ID   | Display Name | Status| Size | 
Attached to |
+--+--+---+--+-+
| c16975ad-dd45-41d7-b0a9-cbd0849f80e4 | test | available |5 |  
   |
+--+--+---+--+-+
bladeA01b:~# openstack volume show test
++--+
| Field  | Value|
++--+
| attachments| []   |
| availability_zone  | nova |
| bootable   | true |
| consistencygroup_id| None |
| created_at | 2016-06-22T20:48:31.00   |
| description|  |
| encrypted  | False|
| id | c16975ad-dd45-41d7-b0a9-cbd0849f80e4 |
| migration_status   | None |
| multiattach| False|
| name   | test |
| os-vol-host-attr:host  | bladeA01b@lvm#LVM_iSCSI  |
| os-vol-mig-status-attr:migstat | None |
| os-vol-mig-status-attr:name_id | None |
| os-vol-tenant-attr:tenant_id   | 2985b96e27f048cd92a18db0dd03aa23 |
| properties |  |
| replication_status | disabled |
| size   | 5|
| snapshot_id| None |
| source_volid   | None |
| status | available|
| type   | None |
| updated_at | 2016-06-22T20:48:48.00   |
| user_id| 0b7e5b0653084efdad5d67b66f2cf949 |
++--+
- s n i p -

If I understand you correctly, this is a Cinder volume, right? Because of
the "@lvm.." part?

How can I create a local volume?

Looking under "System Information -> Block Storage Services" I see only
Cinder services..

- s n i p -
Name Host   ZoneStatus  State   Last Updated
cinder-backupbladeA01b  novaEnabled Up  0 minutes
cinder-scheduler bladeA01b  novaEnabled Up  0 minutes
cinder-volumebladeA01b@lvm  novaEnabled Up  0 minutes
cinder-volumebladeA01b@nfs  novaEnabled Down4 hours, 13 minutes
- s n i p -

> This guide explains about ephemeral storage options:
> https://platform9.com/support/openstack-tutorial-storage-options-and-use-cases/

Thanx, I've read something similar so I'm aware of the differences and
what they do. This one I'm going to read in more detail, because it HAD
more detail! :)

> Usually you can specify the directory where VM instances disks will be
> stored in the compute node on nova.conf option 'instances_path' in
> [DEFAULT] session.

It was commented out, but just for the sake of it I un-commented it..

> Nova compute config options:
> http://docs.openstack.org/liberty/config-reference/content/list-of-compute-config-options.html

Thanx. That was actually halfway to actually be "documentation". I'll bookmark
that.

> The command to create the VM with an ephemeral disk (nova local storage and
> not cinder) is:
> openstack server create --image (image id or name) --flavor (flavor id or
> name) vm_name

- s n i p -
bladeA01b:/var/tmp# wget --quiet 
http://download.cirros-cloud.net/0.3.4/cir

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Cynthia Lopes]

Hi,

First of all, think dis question did no get answered:

-I'll try that thanx. How do you do that with the "openstack" command?

If not, the command is: openstack volume create --size (size in GB) --image
(image name or id) volume_name

Just for info the cinder command was not exact, it should be: cinder create
--image*-id * *--display-name*  


I agree with Eugen that you should make sure you can create a volume and
attach to a VM to help understand what your problem is.
This guide explains about ephemeral storage options:
https://platform9.com/support/openstack-tutorial-storage-options-and-use-cases/

By default you should be able to create VMs with ephemeral disks (not
cinder one).
Usually you can specify the directory where VM instances disks will be
stored in the compute node on nova.conf option 'instances_path' in
[DEFAULT] session. By default it should point to
'/var/lib/nova/instances/'. It is default option so, even if it is not
there, this should work.
Nova compute config options:
http://docs.openstack.org/liberty/config-reference/content/list-of-compute-config-options.html


The command to create the VM with an ephemeral disk (nova local storage and
not cinder) is:
openstack server create --image (image id or name) --flavor (flavor id or
name) vm_name


Concerning the flavor, I think the flavor you use should have the same disk
size as the disk. At least, for me when I try to boot a VM from a volume
that is not the same size of the flavor, I get BadRequest error.

Let us know if you manage to boot a VM so you can try to attach a volume to
it.

Good luck with all that.

Kind regards,
Cynthia


2016-06-21 13:36 GMT+01:00 Eugen Block :

> If it was the flavor, you would get different errors, something like
> "flavor disk too small" or "out of memory". Again, I recommend to launch an
> instance on local disk to see if that is working, then fix the iscsi issue
> to be able to create volumes at all, first empty volumes, then from an
> image and so on.
>
>
> Zitat von Turbo Fredriksson :
>
> On Jun 21, 2016, at 12:19 PM, Abhishek Shrivastava wrote:
>>
>> ​Have you tried any other flavors?
>>>
>>
>> No, I never saw the point. The resources I specified was well within
>> the flavors rules. And the error was "Block Device Mapping is Invalid"
>> I can not see how changing the flavor would change that.
>> --
>> System administrators motto:
>> You're either invisible or in trouble.
>> - Unknown
>>
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>
>
>
> --
> Eugen Block voice   : +49-40-559 51 75
> NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
> Postfach 61 03 15
> D-22423 Hamburg e-mail  : ebl...@nde.ag
>
> Vorsitzende des Aufsichtsrates: Angelika Mozdzen
>   Sitz und Registergericht: Hamburg, HRB 90934
>   Vorstand: Jens-U. Mozdzen
>USt-IdNr. DE 814 013 983
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Eugen Block]

If it was the flavor, you would get different errors, something like  
"flavor disk too small" or "out of memory". Again, I recommend to  
launch an instance on local disk to see if that is working, then fix  
the iscsi issue to be able to create volumes at all, first empty  
volumes, then from an image and so on.



Zitat von Turbo Fredriksson :


On Jun 21, 2016, at 12:19 PM, Abhishek Shrivastava wrote:


​Have you tried any other flavors?


No, I never saw the point. The resources I specified was well within
the flavors rules. And the error was "Block Device Mapping is Invalid"
I can not see how changing the flavor would change that.
--
System administrators motto:
You're either invisible or in trouble.
- Unknown


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

On Jun 21, 2016, at 12:19 PM, Abhishek Shrivastava wrote:

> ​Have you tried any other flavors?

No, I never saw the point. The resources I specified was well within
the flavors rules. And the error was "Block Device Mapping is Invalid"
I can not see how changing the flavor would change that.
-- 
System administrators motto:
You're either invisible or in trouble.
- Unknown


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Abhishek Shrivastava]

​Have you tried any other flavors?

For instance if you are creating a 1GB volume then you can go for flavor
m1.tiny flavor.

So try creating a VM having boot volume size 1GB​ and use flavor m1.tiny
and see if it works.

On Tue, Jun 21, 2016 at 4:36 PM, Turbo Fredriksson  wrote:

> On Jun 21, 2016, at 11:40 AM, Abhishek Shrivastava wrote:
>
> > The first thing I want to know
> >
> >   - Which VM are you creating(i.e; which OS image are you taking)?
>
> I've tried both the CirrOS and Debian GNU/Linux Jessie images.
>
>   http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
>
> http://cdimage.debian.org/cdimage/openstack/8.5.0/debian-8.5.0-openstack-amd64.qcow2
>
> >   - What size are you using and all?
>
> Size? I've tried creating a volume from those images from 2GB to 20GB.
>
> >   - Which flavor are you using for VM creation.?
>
> My own take on the m1.flavor:
>
>   openstack flavor create --ram  1024 --disk 10 --vcpus 1 --disk  5 m1.tiny
> --
> I love deadlines. I love the whooshing noise they
> make as they go by.
> - Douglas Adams
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>



-- 


*Thanks & Regards,*
*Abhishek*
*Cloudbyte Inc. *
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

On Jun 21, 2016, at 11:40 AM, Abhishek Shrivastava wrote:

> The first thing I want to know
> 
>   - Which VM are you creating(i.e; which OS image are you taking)?

I've tried both the CirrOS and Debian GNU/Linux Jessie images.

  http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
  
http://cdimage.debian.org/cdimage/openstack/8.5.0/debian-8.5.0-openstack-amd64.qcow2

>   - What size are you using and all?

Size? I've tried creating a volume from those images from 2GB to 20GB.

>   - Which flavor are you using for VM creation.?

My own take on the m1.flavor:

  openstack flavor create --ram  1024 --disk 10 --vcpus 1 --disk  5 m1.tiny
-- 
I love deadlines. I love the whooshing noise they
make as they go by.
- Douglas Adams


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Abhishek Shrivastava]

Hi Turbo,

The first thing I want to know

   - Which VM are you creating(i.e; which OS image are you taking)?
   - What size are you using and all?

Secondly,

   - Which flavor are you using for VM creation.?


On Tue, Jun 21, 2016 at 12:56 PM, Eugen Block  wrote:

> Can't you boot an instance without cinder?
>>>
>>
>> Don't know, can I??
>>
>
> Well, you should ;-) How do you try to boot your instance, from CLI or
> Horizon? If it's Horizon, you would have to NOT klick the button "Create a
> new volume --> Yes" ;-) If it's CLI it's sufficient to only execute "nova
> boot --flavor  --image  --nic net-id= (optional:
> only if you have multiple networks available) "
> This way you avoid creating a volume.
>
> You could edit nova.conf
>>>
>> How?
>>
>
> It's usually the default, although I'm really not an expert in Openstack.
> But if you simply try to set up nova on control and compute node following
> an install guide, it should bring you there.
> I followed
> http://docs.openstack.org/mitaka/install-guide-obs/nova-controller-install.html,
> there aren't many options to configure and it defaults to local file
> storage.
>
> From what I can see, it doesn't even start sharing via iSCSI
>>
>
> You should try to fix that before you try to use it with openstack.
>
> Didn't even knew you could do that. Thought you HAD to use cinder/swift..
>>
>> Please point me to a faq/howto/doc on how to do that, thanx!
>>
>
> I used this guide:
>
> http://docs.openstack.org/mitaka/install-guide-obs/environment-networking-storage-cinder.html
> In the section for block storage it says "Block storage node (Optional)",
> so you wouldn't have to, but I guess it makes sense in the longterm. But as
> I already said, first you should try to get an instance running at all
> before using another backend.
>
>
> Regards,
> Eugen
>
> Zitat von Turbo Fredriksson :
>
> On Jun 20, 2016, at 3:27 PM, Eugen Block wrote:
>>
>> Can't you boot an instance without cinder?
>>>
>>
>> Don't know, can I??
>>
>> You could edit nova.conf to use local file system, just to have a running
>>> instance. If that works you can switch to another backend.
>>>
>>
>> How?
>>
>> cinder create --image  --name  
>>>
>>
>> I'll try that thanx. How do you do that with the "openstack" command?
>>
>> Try debugging your iscsi connection, maybe first without openstack.
>>>
>>
>> From what I can see, it doesn't even start sharing via iSCSI..
>>
>> In my environment, I first tried to get all services running and working
>>> without external backends, cinder, glance and nova all ran on local storage.
>>>
>>
>> Didn't even knew you could do that. Thought you HAD to use cinder/swift..
>>
>> Please point me to a faq/howto/doc on how to do that, thanx!
>>
>> Then I tried other backends for cinder (iscsi), now all services use ceph.
>>>
>>
>> ceph?
>> --
>> Life sucks and then you die
>>
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>
>
>
> --
> Eugen Block voice   : +49-40-559 51 75
> NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
> Postfach 61 03 15
> D-22423 Hamburg e-mail  : ebl...@nde.ag
>
> Vorsitzende des Aufsichtsrates: Angelika Mozdzen
>   Sitz und Registergericht: Hamburg, HRB 90934
>   Vorstand: Jens-U. Mozdzen
>USt-IdNr. DE 814 013 983
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>



-- 


*Thanks & Regards,*
*Abhishek*
*Cloudbyte Inc. *
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Eugen Block]

Can't you boot an instance without cinder?


Don't know, can I??


Well, you should ;-) How do you try to boot your instance, from CLI or  
Horizon? If it's Horizon, you would have to NOT klick the button  
"Create a new volume --> Yes" ;-) If it's CLI it's sufficient to only  
execute "nova boot --flavor  --image  --nic  
net-id= (optional: only if you have multiple networks  
available) "

This way you avoid creating a volume.


You could edit nova.conf

How?


It's usually the default, although I'm really not an expert in  
Openstack. But if you simply try to set up nova on control and compute  
node following an install guide, it should bring you there.
I followed  
http://docs.openstack.org/mitaka/install-guide-obs/nova-controller-install.html, there aren't many options to configure and it defaults to local file  
storage.



From what I can see, it doesn't even start sharing via iSCSI


You should try to fix that before you try to use it with openstack.


Didn't even knew you could do that. Thought you HAD to use cinder/swift..

Please point me to a faq/howto/doc on how to do that, thanx!


I used this guide:
http://docs.openstack.org/mitaka/install-guide-obs/environment-networking-storage-cinder.html
In the section for block storage it says "Block storage node  
(Optional)", so you wouldn't have to, but I guess it makes sense in  
the longterm. But as I already said, first you should try to get an  
instance running at all before using another backend.



Regards,
Eugen

Zitat von Turbo Fredriksson :


On Jun 20, 2016, at 3:27 PM, Eugen Block wrote:


Can't you boot an instance without cinder?


Don't know, can I??

You could edit nova.conf to use local file system, just to have a  
running instance. If that works you can switch to another backend.


How?


cinder create --image  --name  


I'll try that thanx. How do you do that with the "openstack" command?


Try debugging your iscsi connection, maybe first without openstack.


From what I can see, it doesn't even start sharing via iSCSI..

In my environment, I first tried to get all services running and  
working without external backends, cinder, glance and nova all ran  
on local storage.


Didn't even knew you could do that. Thought you HAD to use cinder/swift..

Please point me to a faq/howto/doc on how to do that, thanx!


Then I tried other backends for cinder (iscsi), now all services use ceph.


ceph?
--
Life sucks and then you die


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

On Jun 20, 2016, at 3:27 PM, Eugen Block wrote:

> Can't you boot an instance without cinder?

Don't know, can I??

> You could edit nova.conf to use local file system, just to have a running 
> instance. If that works you can switch to another backend.

How?

> cinder create --image  --name  

I'll try that thanx. How do you do that with the "openstack" command?

> Try debugging your iscsi connection, maybe first without openstack.

>From what I can see, it doesn't even start sharing via iSCSI..

> In my environment, I first tried to get all services running and working 
> without external backends, cinder, glance and nova all ran on local storage.

Didn't even knew you could do that. Thought you HAD to use cinder/swift..

Please point me to a faq/howto/doc on how to do that, thanx!

> Then I tried other backends for cinder (iscsi), now all services use ceph.

ceph?
--
Life sucks and then you die


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Eugen Block]

Can't start any instances because I can't create volumes


Can't you boot an instance without cinder? You could edit nova.conf to  
use local file system, just to have a running instance. If that works  
you can switch to another backend.



How do i do that from the shell?


cinder create --image  --name  


Do you see the iscsi session on your compute node?


No.


Try debugging your iscsi connection, maybe first without openstack. If  
you aren't able to login to a session then openstack will also fail, I  
guess...


In my environment, I first tried to get all services running and  
working without external backends, cinder, glance and nova all ran on  
local storage. Then I tried other backends for cinder (iscsi), now all  
services use ceph.



Zitat von Turbo Fredriksson :


On Jun 20, 2016, at 1:01 PM, Eugen Block wrote:


Is it possible to create an empty volume?


Yes.


try to attach it to a running instance


Can't start any instances because I can't create volumes.. :(


Do you see the iscsi session on your compute node?


No.

Then you could try to create a volume from an image, that way you  
see if glance and cinder are working properly together.


How do i do that from the shell?
--
Michael Jackson is not going to buried or cremated
but recycled into shopping bags so he can remain white,
plastic and dangerous for kids to play with.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

On Jun 20, 2016, at 1:01 PM, Eugen Block wrote:

> Is it possible to create an empty volume?

Yes.

> try to attach it to a running instance

Can't start any instances because I can't create volumes.. :(

> Do you see the iscsi session on your compute node?

No.

> Then you could try to create a volume from an image, that way you see if 
> glance and cinder are working properly together.

How do i do that from the shell?
--
Michael Jackson is not going to buried or cremated
but recycled into shopping bags so he can remain white,
plastic and dangerous for kids to play with.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Eugen Block]

Is it possible to create an empty volume? Without nova or glance, just  
a volume. If that works and the volume is not deleted immediately, you  
could try to attach it to a running instance to see if nova can handle  
it.

Do you see the iscsi session on your compute node?
Then you could try to create a volume from an image, that way you see  
if glance and cinder are working properly together. If that also works  
it could be an issue with nova, maybe come misconfiguration.



Zitat von Turbo Fredriksson :


On Jun 17, 2016, at 2:38 PM, Eugen Block wrote:

I don't even see the attempt to attach it. If it works, these steps  
should be processed:


Neither can I! And running with debugging doesn't
show anything either :(

The log literally say (no changes, no additions or removal!):

- s n i p -
2016-06-17 15:12:39.335 8046 DEBUG cinder.volume.manager  
[req-b9a6a699-c178-427b-b1f2-bf62dce2578e  
067a3363c5984f81a7cfa2eda5d1ebf3 d524c8dfd9e9449798ebac9b025f8de6 -  
- -] Task  
'cinder.volume.flows.manager.create_volume.CreateVolumeOnFinishTask;volume:create, create.end' (54ad7ada-38eb-4fe1-9efd-53e6f2d35f26) transitioned into state 'RUNNING' from state 'PENDING' _task_receiver  
/usr/lib/python2.7/dist-packages/taskflow/listeners/logging.py:189
2016-06-17 15:12:39.583 8046 INFO  
cinder.volume.flows.manager.create_volume  
[req-b9a6a699-c178-427b-b1f2-bf62dce2578e  
067a3363c5984f81a7cfa2eda5d1ebf3 d524c8dfd9e9449798ebac9b025f8de6 -  
- -] Volume 8892642a-6e12-48ae-ba94-8cc897a4acd5  
(8892642a-6e12-48ae-ba94-8cc897a4acd5): created successfully
2016-06-17 15:12:39.585 8046 DEBUG cinder.volume.manager  
[req-b9a6a699-c178-427b-b1f2-bf62dce2578e  
067a3363c5984f81a7cfa2eda5d1ebf3 d524c8dfd9e9449798ebac9b025f8de6 -  
- -] Task  
'cinder.volume.flows.manager.create_volume.CreateVolumeOnFinishTask;volume:create, create.end' (54ad7ada-38eb-4fe1-9efd-53e6f2d35f26) transitioned into state 'SUCCESS' from state 'RUNNING' with result 'None' _task_receiver  
/usr/lib/python2.7/dist-packages/taskflow/listeners/logging.py:178
2016-06-17 15:12:39.589 8046 DEBUG cinder.volume.manager  
[req-b9a6a699-c178-427b-b1f2-bf62dce2578e  
067a3363c5984f81a7cfa2eda5d1ebf3 d524c8dfd9e9449798ebac9b025f8de6 -  
- -] Flow 'volume_create_manager'  
(45f829ab-d4bd-480a-a78f-c5e8eaa38598) transitioned into state  
'SUCCESS' from state 'RUNNING' _flow_receiver  
/usr/lib/python2.7/dist-packages/taskflow/listeners/logging.py:140
2016-06-17 15:12:39.591 8046 INFO cinder.volume.manager  
[req-b9a6a699-c178-427b-b1f2-bf62dce2578e  
067a3363c5984f81a7cfa2eda5d1ebf3 d524c8dfd9e9449798ebac9b025f8de6 -  
- -] Created volume successfully.

[NOTE: Here everything was a-ok!!]
2016-06-17 15:12:43.378 8046 DEBUG  
oslo_messaging._drivers.amqpdriver [-] received message msg_id: None  
reply to None __call__  
/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:201

[NOTE: And here it starts deleting the volume!]
2016-06-17 15:12:43.383 8046 DEBUG oslo_concurrency.lockutils  
[req-661beca9-723a-4565-99b2-70b5ed862eca  
067a3363c5984f81a7cfa2eda5d1ebf3 d524c8dfd9e9449798ebac9b025f8de6 -  
- -] Lock "8892642a-6e12-48ae-ba94-8cc897a4acd5-delete_volume"  
acquired by "cinder.volume.manager.lvo_inner2" :: waited 0.001s  
inner  
/usr/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:273
2016-06-17 15:12:43.614 8046 INFO cinder.volume.targets.iscsi  
[req-661beca9-723a-4565-99b2-70b5ed862eca  
067a3363c5984f81a7cfa2eda5d1ebf3 d524c8dfd9e9449798ebac9b025f8de6 -  
- -] Skipping remove_export. No iscsi_target is presently exported  
for volume: 8892642a-6e12-48ae-ba94-8cc897a4acd5
2016-06-17 15:12:43.615 8046 DEBUG oslo_concurrency.processutils  
[req-661beca9-723a-4565-99b2-70b5ed862eca  
067a3363c5984f81a7cfa2eda5d1ebf3 d524c8dfd9e9449798ebac9b025f8de6 -  
- -] Running cmd (subprocess): sudo cinder-rootwrap  
/etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o  
vg_name,name,size --nosuffix  
blade_center/8892642a-6e12-48ae-ba94-8cc897a4acd5 execute  
/usr/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:326
2016-06-17 15:12:43.780 8046 DEBUG oslo_concurrency.processutils  
[req-661beca9-723a-4565-99b2-70b5ed862eca  
067a3363c5984f81a7cfa2eda5d1ebf3 d524c8dfd9e9449798ebac9b025f8de6 -  
- -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf env  
LC_ALL=C lvs --noheadings --unit=g -o vg_name,name,size --nosuffix  
blade_center/8892642a-6e12-48ae-ba94-8cc897a4acd5" returned: 0 in  
0.166s execute  
/usr/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:356
2016-06-17 15:12:43.783 8046 DEBUG oslo_concurrency.processutils  
[req-661beca9-723a-4565-99b2-70b5ed862eca  
067a3363c5984f81a7cfa2eda5d1ebf3 d524c8dfd9e9449798ebac9b025f8de6 -  
- -] Running cmd (subprocess): sudo cinder-rootwrap  
/etc/cinder/rootwrap.conf env LC_ALL=C lvdisplay --noheading -C -o  
Attr blade_center/8892642a-6e12-48ae-ba94-8cc897a4acd5 execute  
/usr/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:326
2

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

On Jun 17, 2016, at 2:38 PM, Eugen Block wrote:

> I don't even see the attempt to attach it. If it works, these steps should be 
> processed:

Neither can I! And running with debugging doesn't
show anything either :(

The log literally say (no changes, no additions or removal!):

- s n i p -
2016-06-17 15:12:39.335 8046 DEBUG cinder.volume.manager 
[req-b9a6a699-c178-427b-b1f2-bf62dce2578e 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] Task 
'cinder.volume.flows.manager.create_volume.CreateVolumeOnFinishTask;volume:create,
 create.end' (54ad7ada-38eb-4fe1-9efd-53e6f2d35f26) transitioned into state 
'RUNNING' from state 'PENDING' _task_receiver 
/usr/lib/python2.7/dist-packages/taskflow/listeners/logging.py:189
2016-06-17 15:12:39.583 8046 INFO cinder.volume.flows.manager.create_volume 
[req-b9a6a699-c178-427b-b1f2-bf62dce2578e 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] Volume 
8892642a-6e12-48ae-ba94-8cc897a4acd5 (8892642a-6e12-48ae-ba94-8cc897a4acd5): 
created successfully
2016-06-17 15:12:39.585 8046 DEBUG cinder.volume.manager 
[req-b9a6a699-c178-427b-b1f2-bf62dce2578e 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] Task 
'cinder.volume.flows.manager.create_volume.CreateVolumeOnFinishTask;volume:create,
 create.end' (54ad7ada-38eb-4fe1-9efd-53e6f2d35f26) transitioned into state 
'SUCCESS' from state 'RUNNING' with result 'None' _task_receiver 
/usr/lib/python2.7/dist-packages/taskflow/listeners/logging.py:178
2016-06-17 15:12:39.589 8046 DEBUG cinder.volume.manager 
[req-b9a6a699-c178-427b-b1f2-bf62dce2578e 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] Flow 'volume_create_manager' 
(45f829ab-d4bd-480a-a78f-c5e8eaa38598) transitioned into state 'SUCCESS' from 
state 'RUNNING' _flow_receiver 
/usr/lib/python2.7/dist-packages/taskflow/listeners/logging.py:140
2016-06-17 15:12:39.591 8046 INFO cinder.volume.manager 
[req-b9a6a699-c178-427b-b1f2-bf62dce2578e 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] Created volume successfully.
[NOTE: Here everything was a-ok!!]
2016-06-17 15:12:43.378 8046 DEBUG oslo_messaging._drivers.amqpdriver [-] 
received message msg_id: None reply to None __call__ 
/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:201
[NOTE: And here it starts deleting the volume!]
2016-06-17 15:12:43.383 8046 DEBUG oslo_concurrency.lockutils 
[req-661beca9-723a-4565-99b2-70b5ed862eca 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] Lock 
"8892642a-6e12-48ae-ba94-8cc897a4acd5-delete_volume" acquired by 
"cinder.volume.manager.lvo_inner2" :: waited 0.001s inner 
/usr/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:273
2016-06-17 15:12:43.614 8046 INFO cinder.volume.targets.iscsi 
[req-661beca9-723a-4565-99b2-70b5ed862eca 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] Skipping remove_export. No iscsi_target 
is presently exported for volume: 8892642a-6e12-48ae-ba94-8cc897a4acd5
2016-06-17 15:12:43.615 8046 DEBUG oslo_concurrency.processutils 
[req-661beca9-723a-4565-99b2-70b5ed862eca 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] Running cmd (subprocess): sudo 
cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings 
--unit=g -o vg_name,name,size --nosuffix 
blade_center/8892642a-6e12-48ae-ba94-8cc897a4acd5 execute 
/usr/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:326
2016-06-17 15:12:43.780 8046 DEBUG oslo_concurrency.processutils 
[req-661beca9-723a-4565-99b2-70b5ed862eca 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] CMD "sudo cinder-rootwrap 
/etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o 
vg_name,name,size --nosuffix blade_center/8892642a-6e12-48ae-ba94-8cc897a4acd5" 
returned: 0 in 0.166s execute 
/usr/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:356
2016-06-17 15:12:43.783 8046 DEBUG oslo_concurrency.processutils 
[req-661beca9-723a-4565-99b2-70b5ed862eca 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] Running cmd (subprocess): sudo 
cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvdisplay --noheading -C 
-o Attr blade_center/8892642a-6e12-48ae-ba94-8cc897a4acd5 execute 
/usr/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:326
2016-06-17 15:12:43.948 8046 DEBUG oslo_concurrency.processutils 
[req-661beca9-723a-4565-99b2-70b5ed862eca 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e9449798ebac9b025f8de6 - - -] CMD "sudo cinder-rootwrap 
/etc/cinder/rootwrap.conf env LC_ALL=C lvdisplay --noheading -C -o Attr 
blade_center/8892642a-6e12-48ae-ba94-8cc897a4acd5" returned: 0 in 0.165s 
execute /usr/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:356
2016-06-17 15:12:43.950 8046 INFO cinder.volume.utils 
[req-661beca9-723a-4565-99b2-70b5ed862eca 067a3363c5984f81a7cfa2eda5d1ebf3 
d524c8dfd9e94497

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Eugen Block]

Then I would turn on debug logs for cinder and see if there is more  
information on why it's deleting the volumes before attaching them. I  
don't even see the attempt to attach it. If it works, these steps  
should be processed:


 - Created volume successfully.
 - Initialize volume connection completed successfully.
 - Attach volume completed successfully.
 - Deleted volume successfully.

Regards,
Eugen

Zitat von Turbo Fredriksson :


On Jun 17, 2016, at 1:12 PM, Eugen Block wrote:


Have you nova-compute.logs?


They don't say a thing, so I'm guessing it never gets
that far.

If I'm quick, i can see the LVM volume being created
successfully (which the log also indicates).

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Turbo Fredriksson]

On Jun 17, 2016, at 1:12 PM, Eugen Block wrote:

> Have you nova-compute.logs?

They don't say a thing, so I'm guessing it never gets
that far.

If I'm quick, i can see the LVM volume being created
successfully (which the log also indicates).

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Create instance fails on creating block device - Block Device Mapping is Invalid

[Eugen Block]

I had also some trouble getting volume backed instances to boot. I use  
xen hypervisor and found out that the instance was assigned a device  
name of "vda" (which is set by default) instead of xvda, I filed a bug  
report for this. Have you nova-compute.logs? I can't find them in your  
link. They should give a hint about the device name or other possible  
causes. Since the volume is created but immediately destroyed, I guess  
nova has a problem with the block device.


Regards,
Eugen

Zitat von Turbo Fredriksson :


I'm trying my newly installed Openstack system and I'm getting
problem in starting my first instance.

- s n i p -
Build of instance 5193c2d9-0aaf-4f84-b108-f6884d97b571 aborted:  
Block Device Mapping is Invalid.
File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py",  
line 1926, in _do_build_and_run_instance filter_properties) File  
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line  
2083, in _build_and_run_instance 'create.error', fault=e) File  
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220,  
in __exit__ self.force_reraise() File  
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196,  
in force_reraise six.reraise(self.type_, self.value, self.tb) File  
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line  
2048, in _build_and_run_instance block_device_mapping) as resources:  
File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__  
return self.gen.next() File  
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line  
2206, in _build_resources reason=e.format_message())

- s n i p -

Cleaning up all the logs for irrelevant stuff, I see:

- s n i p -
INFO cinder.api.v2.volumes  Create volume of 5 GB
INFO cinder.volume.api  Volume created successfully.
INFO cinder.volume.flows.manager.create_volume  Volume  
6b1dace4-78e1-452b-a455-c0fc882374f3: being created as image with  
specification: {'status': u'creating', 'image_location': (None,  
None), 'volume_size': 5, 'volume_name':  
'volume-6b1dace4-78e1-452b-a455-c0fc882374f3', 'image_id':  
u'8c15b5e8-9a67-4784-ad7a-0b1cc7b0bdec', 'image_service':  
,  
'image_meta': {'status': u'active', 'name': u'fedora23', 'deleted':  
False, 'container_format': u'docker', 'created_at':  
datetime.datetime(2016, 6, 15, 20, 38, 43, tzinfo=),  
'disk_format': u'qcow2', 'updated_at': datetime.datetime(2016, 6,  
15, 20, 38, 45, tzinfo=), 'id':  
u'8c15b5e8-9a67-4784-ad7a-0b1cc7b0bdec', 'owner':  
u'd524c8dfd9e9449798ebac9b025f8de6', 'min_ram': 0, 'checksum':  
u'38d62e2e1909c89f72ba4d5f5c0005d5', 'min_disk': 0, 'is_public':  
True, 'deleted_at': None, 'properties': {u'hypervisor_type':  
u'docker', u'architecture': u'x86_64'}, 'size': 23436

 3392}}
INFO cinder.image.image_utils  Image download 223.00 MB at 35.35 MB/s
WARN manila.context [-] Arguments dropped when creating context:  
{u'read_only': False, u'domain': None, u'show_deleted': False,  
u'user_identity': u'- - - - -', u'project_domain': None,  
u'resource_uuid': None, u'user_domain': None}.
WARN manila.context [-] Arguments dropped when creating context:  
{u'read_only': False, u'domain': None, u'show_deleted': False,  
u'user_identity': u'- - - - -', u'project_domain': None,  
u'resource_uuid': None, u'user_domain': None}.

INFO cinder.image.image_utils  Converted 3072.00 MB image at 31.59 MB/s
INFO cinder.volume.flows.manager.create_volume  Volume  
volume-6b1dace4-78e1-452b-a455-c0fc882374f3  
(6b1dace4-78e1-452b-a455-c0fc882374f3): created successfully

INFO cinder.volume.manager  Created volume successfully.
INFO cinder.api.v2.volumes  Delete volume with id:  
6b1dace4-78e1-452b-a455-c0fc882374f3

INFO cinder.volume.api  Delete volume request issued successfully.
INFO eventlet.wsgi.server  10.0.4.5 "DELETE  
/v2/d524c8dfd9e9449798ebac9b025f8de6/volumes/6b1dace4-78e1-452b-a455-c0fc882374f3 HTTP/1.1" status: 202  len: 211 time:  
0.1300900
INFO cinder.volume.targets.iscsi  Skipping remove_export. No  
iscsi_target is presently exported for volume:  
6b1dace4-78e1-452b-a455-c0fc882374f3
INFO cinder.volume.utils  Performing secure delete on volume:  
/dev/mapper/blade_center-volume--6b1dace4--78e1--452b--a455--c0fc882374f3

- s n i p -

Full log at http://bayour.com/misc/openstack_instance_create-log.txt.


The web GUI say (this might be from another test, but I always
get the same):

- s n i p -
Error: Failed to perform requested operation on instance
"jessie-test", the instance has an error status: Please try again
later [Error: Build of instance a4e1deaa-cdf0-4fc7-8c54-579868c962c3
aborted: Block Device Mapping is Invalid.].
- s n i p -



I can see nothing relevant in this that would make it fail!
The only thing that bought my eye was that it isn't removing
the iSCSI target, because there isn't one..

This is (most of) my cinder.conf file:

- s n i p -
[DEFAULT]
my_ip = 10.0.4.1
storage_availability_zone = nova
default_availability_zone = n