Ocata Cinder volume based instance creation fails
Hello, need some help, The instance creation fails with error unable to establish a connection with CInder api. Below is the nova-compute.log
2018-07-24 08:53:02.842 1838689 WARNING nova.virt.libvirt.driver [req-3c5133fe-b91d-42a4-bb5f-a99bb5139cc8 95e942fee3ef40b39c0c7a17f4cd15bb 281cec8c977b4fff8e5bbc5ca008e2c6 - - -] [instance: 0ab8b94f-ba6e-4f62-b429-549ad02ca9a3] Ignoring supplied device name: /dev/vda. Libvirt can't honour user-supplied dev names
2018-07-24 08:57:47.916 1838689 ERROR nova.compute.manager [instance: 0ab8b94f-ba6e-4f62-b429-549ad02ca9a3] CinderConnectionFailed: Connection to cinder host failed: Unable to establish connection to
http://10.150.0.33:8776/v2/281cec8c977b4fff8e5bbc5ca008e2c6/volumes/c9a7026c-c380-4a24-a583-6aa9cc25407c/action
: ('Connection aborted.', BadStatusLine("''",)) 2018-07-24 08:57:47.916 1838689 ERROR nova.compute.manager [instance: 0ab8b94f-ba6e-4f62-b429-549ad02ca9a3] 2018-07-24 08:57:48.083 1838689 ERROR nova.compute.manager [req-3c5133fe-b91d-42a4-bb5f-a99bb5139cc8 95e942fee3ef40b39c0c7a17f4cd15bb
281cec8c977b4fff8e5bbc5ca008e2c6 - - -] [instance: 0ab8b94f-ba6e-4f62-b429-549ad02ca9a3] Build of instance 0ab8b94f-ba6e-4f62-b429-549ad02ca9a3 aborted: Block Device Mapping is Invalid.
User@Openstack Server:~$ openstack endpoint show cinderv2
+--------------+------------------------------------------+
| Field | Value |
+--------------+------------------------------------------+
| adminurl | http://10.150.0.33:8776/v2/$(tenant_id)s |
| enabled | True |
| id | 01313f59746e25463c887982aee0900 |
| internalurl | http://10.150.0.33:8776/v2/$(tenant_id)s |
| publicurl | http://10.150.0.33:8776/v2/$(tenant_id)s |
| region | RegionOne |
| service_id | 10eed35d922c4r34desf8f350402e06 |
| service_name | cinderv2 |
| service_type | volumev2 |
+--------------+------------------------------------------+
User@Openstack Server:~$
How did you create the instance?
Block Device Mapping is Invalidindicates that instance storage is not specified correctly. It could be the image, a volume or instance's ephemeral storage.I guess that BadStatusLine and connection failed are Nova's misinterpretation of Cinder's error.
Perhaps you find more in the Cinder logs.
Hello Bernd, not seeing any warning or error on the cinder logs, but on the cinder server syslogs i am seeing few.. The issue exact here is I can create volumes and on instance creation it creates volumes but fail to attach that volume to instance and instance fails on creation.
Please see the logs attached https://files.fm/u/357j8buj
Now I think the connection problem is the cause and the invalid block mapping an effect. If Cinder is deployed behind a web server, the web server log should show you how it's accessed, otherwise the Cinder API log. Perhaps you get better info with debug logging.