Issues creating volumes with storage node [closed]

asked 2014-12-16 14:29:48 -0500

mickt gravatar image

updated 2014-12-17 02:29:06 -0500

I have 1x controller/neutron server, qa-openstack04 & 3x compute servers, qa-openstack01 has storage attached for cinder.  I initially created cinder volume of only 1G during installation, which was on controller node.  Storage not attached or configured at that time and was later added.  Can/should this initial cinder specification be increased or omitted during installation?

I can create instances and volumes (seems so in UI but volume not created in DB) but I cannot create instances with Boot from image (creates new volume).

Error in UI while creating instance with Boot from image (creates new volume):
Error: Failed to launch instance "test": Please try again later [Error: Build of instance 3b266754-cca8-42a7-90d6-debc8895868b aborted: Failure prepping block device.]. 

Compute/storage server cinder scheduler log during above:
tail -f /var/log/cinder/scheduler.log
2014-12-16 19:29:46.781 64159 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on 10.10.12.9:5672
2014-12-16 19:55:16.032 64159 WARNING cinder.scheduler.filters.capacity_filter [req-3c817de2-6923-4ff9-be49-9364f81a46f7 987ea97f073d49ebb33f03ece2a23b7f eeb5ff6dcc3c4763a3b92173d79d872b - - -] Insufficient free space for volume creation on host qa-openstack04#LVM_iSCSI (requested / avail): 20/1.0

Controller/neutron server cinder scheduler log during volume attach to instance:
tail -f /var/log/cinder/scheduler.log
2014-12-16 19:29:43.724 17151 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on 10.10.12.9:5672

Trying to attach volume to instance:
Controller/neutron server cinder volume log during volume attach to instance:
tail -f /var/log/cinder/volume.log

Compute/storage server cinder volume log during volume attach to instance:
tail -f /var/log/cinder/volume.log
2014-12-16 20:05:15.174 64271 INFO cinder.brick.iscsi.iscsi [req-540d7fe8-1e08-4117-8910-21c6007bca70 987ea97f073d49ebb33f03ece2a23b7f eeb5ff6dcc3c4763a3b92173d79d872b - - -] Creating iscsi_target for volume: volume-13e82102-0698-405d-a178-ccb4151e6143
2014-12-16 20:05:15.417 64271 ERROR cinder.brick.iscsi.iscsi [req-540d7fe8-1e08-4117-8910-21c6007bca70 987ea97f073d49ebb33f03ece2a23b7f eeb5ff6dcc3c4763a3b92173d79d872b - - -] Failed to create iscsi target for volume id:volume-13e82102-0698-405d-a178-ccb4151e6143.
2014-12-16 20:05:15.418 64271 ERROR oslo.messaging.rpc.dispatcher [req-540d7fe8-1e08-4117-8910-21c6007bca70 987ea97f073d49ebb33f03ece2a23b7f eeb5ff6dcc3c4763a3b92173d79d872b - - -] Exception during message handling: Resource could not be found.

I also see Error deleting on volume in UI probably because it doesn't really exist.

nova-manage service list
Binary           Host                                 Zone             Status     State Updated_At
nova-consoleauth qa-openstack04                       internal         enabled    :-)   2014-12-16 19:42:08
nova-scheduler   qa-openstack04                       internal         enabled    :-)   2014-12-16 19:42:10
nova-conductor   qa-openstack04                       internal         enabled    :-)   2014-12-16 19:42:10
nova-cert        qa-openstack04                       internal         enabled    :-)   2014-12-16 19:42:08
nova-compute     qa-openstack01                       nova             enabled    :-)   2014-12-16 19:42:03
nova-compute     qa-openstack02                       nova             enabled    :-)   2014-12-16 19:42:10
nova-compute     qa-openstack03                       nova             enabled    :-)   2014-12-16 19:42:07

Unsure if the following is correct, should qa-openstack04 have cinder-volume?  Can anyone confirm?
cinder-manage service list
Binary           Host                                 Zone             Status     State Updated At
cinder-scheduler qa-openstack01                       nova             enabled    :-)   2014-12-16 19:42:17
cinder-volume    qa-openstack01@lvm01                 nova             enabled    :-)   2014-12-16 19:42:07
cinder-scheduler qa-openstack04                       nova             enabled    :-)   2014-12-16 19:42:14
cinder-volume    qa-openstack04                       nova             enabled    :-)   2014-12-16 19:42:15    

There is one volume in dashboard and on target but I do not see it with cinder list command:
cinder type-list
+--------------------------------------+------+
|                  ID                  | Name |
+--------------------------------------+------+
| c526fed1-d1b5-4ebd-8ed6-980ca2c31c1b | lvm  |
+--------------------------------------+------+
cinder list
+----+--------+--------------+------+-------------+----------+-------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by mickt
close date 2015-01-19 02:35:30.234969

Comments

As far as I understand http://docs.openstack.org/trunk/insta...

 service cinder-scheduler
 service cinder-api

run only on Controller.

dbaxps gravatar imagedbaxps ( 2014-12-17 02:51:50 -0500 )edit

As far as I understand http://docs.openstack.org/trunk/insta...

cinder-volume

run only on Storage node

dbaxps gravatar imagedbaxps ( 2014-12-17 02:55:46 -0500 )edit

Per your report

    qa-openstack04 is Controller
    qa-openstack01 is Compute

Unsure if the following is correct, should qa-openstack04 have cinder-volume? Can anyone confirm?

If it is Controller && not Storage Node cinder-volume is not needed.
dbaxps gravatar imagedbaxps ( 2014-12-17 02:57:10 -0500 )edit

This is as I would understand it too but I think it was created during installation with packstack and if I set CONFIG_CINDER_INSTALL=n then openstack failed to install.

mickt gravatar imagemickt ( 2014-12-17 03:14:12 -0500 )edit

I would test disabling service cinder-volume on Controller && enabling on Storage Node.

dbaxps gravatar imagedbaxps ( 2014-12-17 03:39:47 -0500 )edit