Re: [openstack-dev] Can not create cinder volume
On 15 July 2014 11:59, Johnson Cheng wrote: > May I ask you another question that how cinder choose volume node to create > volume if I have multi volume nodes? > > For example, > > when controller node and compute node are alive, the volume will be created > at compute node. > > When I shutdown compute node, the volume will be created at controller node. > > How can I create volume at compute node when both controller node and > compute node are alive? The short answer is: - If you want to manually control which backend is used per volume, then you need to set up volume types - If you want volumes to be automatically distributed between the two backends, look at the weighters (capacity weighter will pick which ever backend has the greatest free capacity for example) The admin guide should be able to explain how to set either of these two up. I suspect you want the later. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Can not create cinder volume
Dear Duncan,
Thanks for your reply.
My rootwrap.conf is correct, but I find there is a garbage file at
/etc/cinder/rootwrap.d/ folder.
When I remove it, everything is right.
May I ask you another question that how cinder choose volume node to create
volume if I have multi volume nodes?
For example,
when controller node and compute node are alive, the volume will be created at
compute node.
When I shutdown compute node, the volume will be created at controller node.
How can I create volume at compute node when both controller node and compute
node are alive?
Regards,
Johnson
From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: Tuesday, July 15, 2014 3:51 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Can not create cinder volume
On 15 July 2014 08:24, Johnson Cheng
mailto:johnson.ch...@qsantechnology.com>>
wrote:
I have two questions here,
1. It still has “Error encountered during initialization of driver:
LVMISCSIDriver” error message in cinder-volume.log, how to fix this issue?
2. From cinder-scheduler.log, it shows “volume service is down or
disabled. (host: Compute)”. How can I modify cinder.conf to create cinder
volume at controller node?
The good news is that you only have one problem. The driver not being
initialized means that that cinder-volume service never signs on with the
scheduler, so is never eligible to create volumes.
The problem you need to fix is this one:
2014-07-15 15:01:59.147 13901 TRACE cinder.volume.manager Stderr: 'Traceback
(most recent call last):\n File "/usr/bin/cinder-rootwrap", line 10, in
\nsys.exit(main())\n File
"/usr/lib/python2.7/dist-packages/oslo/rootwrap/cmd.py", line 107, in main\n
filters = wrapper.load_filters(config.filters_path)\n File
"/usr/lib/python2.7/dist-packages/oslo/rootwrap/wrapper.py", line 119, in
load_filters\nfor (name, value) in filterconfig.items("Filters"):\n File
"/usr/lib/python2.7/ConfigParser.py", line 347, in items\nraise
NoSectionError(section)\nConfigParser.NoSectionError: No section: \'Filters\'\n'
It looks like the config file /etc/cinder/rootwrap.conf has become corrupted on
one node - can you compare this file between the working and not working node
and see if there are any differences?
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Can not create cinder volume
On 15 July 2014 08:24, Johnson Cheng
wrote:
>
>
> I have two questions here,
>
> 1. It still has “Error encountered during initialization of driver:
> LVMISCSIDriver” error message in cinder-volume.log, how to fix this issue?
>
> 2. From cinder-scheduler.log, it shows “volume service is down or
> disabled. (host: Compute)”. How can I modify cinder.conf to create cinder
> volume at controller node?
>
>
>
The good news is that you only have one problem. The driver not being
initialized means that that cinder-volume service never signs on with the
scheduler, so is never eligible to create volumes.
The problem you need to fix is this one:
2014-07-15 15:01:59.147 13901 TRACE cinder.volume.manager Stderr:
'Traceback (most recent call last):\n File "/usr/bin/cinder-rootwrap",
line 10, in \nsys.exit(main())\n File
"/usr/lib/python2.7/dist-packages/oslo/rootwrap/cmd.py", line 107, in
main\nfilters = wrapper.load_filters(config.filters_path)\n File
"/usr/lib/python2.7/dist-packages/oslo/rootwrap/wrapper.py", line 119, in
load_filters\nfor (name, value) in filterconfig.items("Filters"):\n
File "/usr/lib/python2.7/ConfigParser.py", line 347, in items\nraise
NoSectionError(section)\nConfigParser.NoSectionError: No section:
\'Filters\'\n'
It looks like the config file /etc/cinder/rootwrap.conf has become
corrupted on one node - can you compare this file between the working and
not working node and see if there are any differences?
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Can not create cinder volume
oller:5672
>
> 2014-07-15 10:55:49.942 27399 INFO cinder.volume.manager
> [req-2e368031-ee15-428d-8239-2973261f116d - - - - -] Updating volume status
>
> 2014-07-15 10:55:49.943 27399 WARNING cinder.volume.manager
> [req-2e368031-ee15-428d-8239-2973261f116d - - - - -] Unable to update
> stats, LVMISCSIDriver -2.0.0 driver is uninitialized.
>
>
>
> My cinder version is 1.0.8, and “cinder service-list” output is listed as
> below,
>
>
> +--++--+-+---++
>
> | Binary |Host| Zone | Status | State |
> Updated_at |
>
>
> +----------+----+--+-+---++
>
> | cinder-scheduler | controller | nova | enabled | up |
> 2014-07-15T02:57:55.00 |
>
> | cinder-volume | controller | nova | enabled | up |
> 2014-07-15T02:57:51.00 |
>
>
> +--++--+-+---++
>
>
>
>
>
> Regards,
>
> Johnson
>
>
>
>
>
> *From:* John Griffith [mailto:john.griff...@solidfire.com]
> *Sent:* Monday, July 14, 2014 10:26 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] Can not create cinder volume
>
>
>
>
>
>
>
> On Mon, Jul 14, 2014 at 8:13 AM, Duncan Thomas
> wrote:
>
> Please post up more (all) of your cinder-volume.log - something is
> stopping your driver being initialised, but you haven't provided enough
> logs to tell what the issue it.
>
>
>
> On 14 July 2014 12:22, Johnson Cheng
> wrote:
>
> Dear All,
>
>
>
> When I use “cinder create –display-name myVolume 1” to create a cinder
> volume, its status will be error when I use “cinder list” to query it.
>
>
> +--++--+--+-+--+-+
>
> | ID | Status | Display Name | Size |
> Volume Type | Bootable | Attached to |
>
>
> +--++--+--+-+--+-+
>
> | 83059a3e-e66c-4fd8-829e-09ca450b4d70 | error | myVolume | 1
> | None| false | |
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> My Openstack version is Icehouse, and I install it on Ubuntu 14.04 LTS.
>
>
>
> The vgs output,
>
> VG#PV #LV #SN Attr VSize VFree
>
> cinder-volumes 1 0 0 wz--n- 153.38g 153.38g
>
>
>
> Here is my cinder.conf
>
> [DEFAULT]
>
> rootwrap_config = /etc/cinder/rootwrap.conf
>
> api_paste_confg = /etc/cinder/api-paste.ini
>
> iscsi_helper = tgtadm
>
> volume_name_template = volume-%s
>
> volume_group = cinder-volumes
>
> verbose = True
>
> auth_strategy = keystone
>
> state_path = /var/lib/cinder
>
> lock_path = /var/lock/cinder
>
> volumes_dir = /var/lib/cinder/volumes
>
>
>
> rpc_backend = cinder.openstack.common.rpc.impl_kombu
>
> rabbit_host = controller
>
> rabbit_port = 5672
>
> rabbit_userid = guest
>
> rabbit_password = demo
>
>
>
> glance_host = controller
>
>
>
> control_exchange = cinder
>
> notification_driver = cinder.openstack.common.notifier.rpc_notifier
>
>
>
> [database]
>
> connection = mysql://cinder:demo@controller/cinder
>
>
>
> [keystone_authtoken]
>
> auth_uri = http://controller:5000
>
> auth_host = controller
>
> auth_port = 35357
>
> auth_protocol = http
>
> admin_tenant_name = service
>
> admin_user = cinder
>
> admin_password = demo
>
>
>
> Here is my cinder-schedule.log
>
> 2014-07-14 17:34:37.592 7141 INFO oslo.messaging._drivers.impl_rabbit [-]
> Connected to AMQP server on controller:5672
>
> 2014-07-14 17:34:44.769 7141 WARNING cinder.context [-] Arguments dropped
> when creating context: {'user': u'1149275f4ea84690a9da5b7f442ab48f',
> 'tenant': u'4e898758e77c4d3c8d0b0eecf5ae0957', 'user_identity':
> u'1149275f4ea84690a9da5b7f442ab48f 4e898758e77c4d3c8d0b0eecf5ae0957 - - -'}
>
> 2014-07-14 17:34:45.004 7141 ERROR
> cinder.scheduler.filters.capacity_filter
> [req-ebae9974-8741-4a6d-af44-456e506e5612 1149275f4ea84690a9da5b7f442ab48f
> 4e898758e77c4d3c8d0b0eecf5ae0957 - - -] Free capacity not set: volume node
> info collection broken.
>
> 2014-07-14 17:34:45.030 7141 ERROR cinder.scheduler.flows.create_volume
> [req-ebae9974-8741-4a6d-af44-456e506e5612 1149275f4ea84690a9da5b7f442ab4
Re: [openstack-dev] Can not create cinder volume
On Mon, Jul 14, 2014 at 8:13 AM, Duncan Thomas
wrote:
> Please post up more (all) of your cinder-volume.log - something is
> stopping your driver being initialised, but you haven't provided enough
> logs to tell what the issue it.
>
>
> On 14 July 2014 12:22, Johnson Cheng
> wrote:
>
>> Dear All,
>>
>>
>>
>> When I use “cinder create –display-name myVolume 1” to create a cinder
>> volume, its status will be error when I use “cinder list” to query it.
>>
>>
>> +--++--+--+-+--+-+
>>
>> | ID | Status | Display Name | Size |
>> Volume Type | Bootable | Attached to |
>>
>>
>> +--++--+--+-+--+-+
>>
>> | 83059a3e-e66c-4fd8-829e-09ca450b4d70 | error | myVolume | 1
>> | None| false | |
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> My Openstack version is Icehouse, and I install it on Ubuntu 14.04 LTS.
>>
>>
>>
>> The vgs output,
>>
>> VG#PV #LV #SN Attr VSize VFree
>>
>> cinder-volumes 1 0 0 wz--n- 153.38g 153.38g
>>
>>
>>
>> Here is my cinder.conf
>>
>> [DEFAULT]
>>
>> rootwrap_config = /etc/cinder/rootwrap.conf
>>
>> api_paste_confg = /etc/cinder/api-paste.ini
>>
>> iscsi_helper = tgtadm
>>
>> volume_name_template = volume-%s
>>
>> volume_group = cinder-volumes
>>
>> verbose = True
>>
>> auth_strategy = keystone
>>
>> state_path = /var/lib/cinder
>>
>> lock_path = /var/lock/cinder
>>
>> volumes_dir = /var/lib/cinder/volumes
>>
>>
>>
>> rpc_backend = cinder.openstack.common.rpc.impl_kombu
>>
>> rabbit_host = controller
>>
>> rabbit_port = 5672
>>
>> rabbit_userid = guest
>>
>> rabbit_password = demo
>>
>>
>>
>> glance_host = controller
>>
>>
>>
>> control_exchange = cinder
>>
>> notification_driver = cinder.openstack.common.notifier.rpc_notifier
>>
>>
>>
>> [database]
>>
>> connection = mysql://cinder:demo@controller/cinder
>>
>>
>>
>> [keystone_authtoken]
>>
>> auth_uri = http://controller:5000
>>
>> auth_host = controller
>>
>> auth_port = 35357
>>
>> auth_protocol = http
>>
>> admin_tenant_name = service
>>
>> admin_user = cinder
>>
>> admin_password = demo
>>
>>
>>
>> Here is my cinder-schedule.log
>>
>> 2014-07-14 17:34:37.592 7141 INFO oslo.messaging._drivers.impl_rabbit [-]
>> Connected to AMQP server on controller:5672
>>
>> 2014-07-14 17:34:44.769 7141 WARNING cinder.context [-] Arguments dropped
>> when creating context: {'user': u'1149275f4ea84690a9da5b7f442ab48f',
>> 'tenant': u'4e898758e77c4d3c8d0b0eecf5ae0957', 'user_identity':
>> u'1149275f4ea84690a9da5b7f442ab48f 4e898758e77c4d3c8d0b0eecf5ae0957 - - -'}
>>
>> 2014-07-14 17:34:45.004 7141 ERROR
>> cinder.scheduler.filters.capacity_filter
>> [req-ebae9974-8741-4a6d-af44-456e506e5612 1149275f4ea84690a9da5b7f442ab48f
>> 4e898758e77c4d3c8d0b0eecf5ae0957 - - -] Free capacity not set: volume node
>> info collection broken.
>>
>> 2014-07-14 17:34:45.030 7141 ERROR cinder.scheduler.flows.create_volume
>> [req-ebae9974-8741-4a6d-af44-456e506e5612 1149275f4ea84690a9da5b7f442ab48f
>> 4e898758e77c4d3c8d0b0eecf5ae0957 - - -] Failed to schedule_create_volume:
>> No valid host was found.
>>
>>
>>
>> Here is my cinder-volume.log
>>
>> 2014-07-14 19:14:15.489 7151 INFO cinder.volume.manager [-] Updating
>> volume status
>>
>> 2014-07-14 19:14:15.490 7151 WARNING cinder.volume.manager [-] Unable to
>> update stats, LVMISCSIDriver -2.0.0 driver is uninitialized.
>>
>>
>>
>>
>>
>> Your response will be appreciated.
>>
>> Let me know if you need more information.
>>
>>
>>
>>
>>
>> Regards,
>>
>> Johnson
>>
>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Duncan Thomas
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> Make sure "controller" resolves on your cinder-volume node. It appears
that either your volume-node isn't able to communicate with the controller
(you can check this by trying a 'cinder service-list'). Another
possibility is something's not quite right with your message queue
settings. Main thing here would again be name resolution and that your
message queue is actually matched up here (ie settings on the controller
match those on your volume-node).
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Can not create cinder volume
Please post up more (all) of your cinder-volume.log - something is stopping
your driver being initialised, but you haven't provided enough logs to tell
what the issue it.
On 14 July 2014 12:22, Johnson Cheng
wrote:
> Dear All,
>
>
>
> When I use “cinder create –display-name myVolume 1” to create a cinder
> volume, its status will be error when I use “cinder list” to query it.
>
>
> +--++--+--+-+--+-+
>
> | ID | Status | Display Name | Size |
> Volume Type | Bootable | Attached to |
>
>
> +--++--+--+-+--+-+
>
> | 83059a3e-e66c-4fd8-829e-09ca450b4d70 | error | myVolume | 1
> | None| false | |
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> My Openstack version is Icehouse, and I install it on Ubuntu 14.04 LTS.
>
>
>
> The vgs output,
>
> VG#PV #LV #SN Attr VSize VFree
>
> cinder-volumes 1 0 0 wz--n- 153.38g 153.38g
>
>
>
> Here is my cinder.conf
>
> [DEFAULT]
>
> rootwrap_config = /etc/cinder/rootwrap.conf
>
> api_paste_confg = /etc/cinder/api-paste.ini
>
> iscsi_helper = tgtadm
>
> volume_name_template = volume-%s
>
> volume_group = cinder-volumes
>
> verbose = True
>
> auth_strategy = keystone
>
> state_path = /var/lib/cinder
>
> lock_path = /var/lock/cinder
>
> volumes_dir = /var/lib/cinder/volumes
>
>
>
> rpc_backend = cinder.openstack.common.rpc.impl_kombu
>
> rabbit_host = controller
>
> rabbit_port = 5672
>
> rabbit_userid = guest
>
> rabbit_password = demo
>
>
>
> glance_host = controller
>
>
>
> control_exchange = cinder
>
> notification_driver = cinder.openstack.common.notifier.rpc_notifier
>
>
>
> [database]
>
> connection = mysql://cinder:demo@controller/cinder
>
>
>
> [keystone_authtoken]
>
> auth_uri = http://controller:5000
>
> auth_host = controller
>
> auth_port = 35357
>
> auth_protocol = http
>
> admin_tenant_name = service
>
> admin_user = cinder
>
> admin_password = demo
>
>
>
> Here is my cinder-schedule.log
>
> 2014-07-14 17:34:37.592 7141 INFO oslo.messaging._drivers.impl_rabbit [-]
> Connected to AMQP server on controller:5672
>
> 2014-07-14 17:34:44.769 7141 WARNING cinder.context [-] Arguments dropped
> when creating context: {'user': u'1149275f4ea84690a9da5b7f442ab48f',
> 'tenant': u'4e898758e77c4d3c8d0b0eecf5ae0957', 'user_identity':
> u'1149275f4ea84690a9da5b7f442ab48f 4e898758e77c4d3c8d0b0eecf5ae0957 - - -'}
>
> 2014-07-14 17:34:45.004 7141 ERROR
> cinder.scheduler.filters.capacity_filter
> [req-ebae9974-8741-4a6d-af44-456e506e5612 1149275f4ea84690a9da5b7f442ab48f
> 4e898758e77c4d3c8d0b0eecf5ae0957 - - -] Free capacity not set: volume node
> info collection broken.
>
> 2014-07-14 17:34:45.030 7141 ERROR cinder.scheduler.flows.create_volume
> [req-ebae9974-8741-4a6d-af44-456e506e5612 1149275f4ea84690a9da5b7f442ab48f
> 4e898758e77c4d3c8d0b0eecf5ae0957 - - -] Failed to schedule_create_volume:
> No valid host was found.
>
>
>
> Here is my cinder-volume.log
>
> 2014-07-14 19:14:15.489 7151 INFO cinder.volume.manager [-] Updating
> volume status
>
> 2014-07-14 19:14:15.490 7151 WARNING cinder.volume.manager [-] Unable to
> update stats, LVMISCSIDriver -2.0.0 driver is uninitialized.
>
>
>
>
>
> Your response will be appreciated.
>
> Let me know if you need more information.
>
>
>
>
>
> Regards,
>
> Johnson
>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Can not create cinder volume
Dear All,
When I use "cinder create -display-name myVolume 1" to create a cinder volume,
its status will be error when I use "cinder list" to query it.
+--++--+--+-+--+-+
| ID | Status | Display Name | Size | Volume
Type | Bootable | Attached to |
+--++--+--+-+--+-+
| 83059a3e-e66c-4fd8-829e-09ca450b4d70 | error | myVolume | 1 |
None| false | |
My Openstack version is Icehouse, and I install it on Ubuntu 14.04 LTS.
The vgs output,
VG#PV #LV #SN Attr VSize VFree
cinder-volumes 1 0 0 wz--n- 153.38g 153.38g
Here is my cinder.conf
[DEFAULT]
rootwrap_config = /etc/cinder/rootwrap.conf
api_paste_confg = /etc/cinder/api-paste.ini
iscsi_helper = tgtadm
volume_name_template = volume-%s
volume_group = cinder-volumes
verbose = True
auth_strategy = keystone
state_path = /var/lib/cinder
lock_path = /var/lock/cinder
volumes_dir = /var/lib/cinder/volumes
rpc_backend = cinder.openstack.common.rpc.impl_kombu
rabbit_host = controller
rabbit_port = 5672
rabbit_userid = guest
rabbit_password = demo
glance_host = controller
control_exchange = cinder
notification_driver = cinder.openstack.common.notifier.rpc_notifier
[database]
connection = mysql://cinder:demo@controller/cinder
[keystone_authtoken]
auth_uri = http://controller:5000
auth_host = controller
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = cinder
admin_password = demo
Here is my cinder-schedule.log
2014-07-14 17:34:37.592 7141 INFO oslo.messaging._drivers.impl_rabbit [-]
Connected to AMQP server on controller:5672
2014-07-14 17:34:44.769 7141 WARNING cinder.context [-] Arguments dropped when
creating context: {'user': u'1149275f4ea84690a9da5b7f442ab48f', 'tenant':
u'4e898758e77c4d3c8d0b0eecf5ae0957', 'user_identity':
u'1149275f4ea84690a9da5b7f442ab48f 4e898758e77c4d3c8d0b0eecf5ae0957 - - -'}
2014-07-14 17:34:45.004 7141 ERROR cinder.scheduler.filters.capacity_filter
[req-ebae9974-8741-4a6d-af44-456e506e5612 1149275f4ea84690a9da5b7f442ab48f
4e898758e77c4d3c8d0b0eecf5ae0957 - - -] Free capacity not set: volume node info
collection broken.
2014-07-14 17:34:45.030 7141 ERROR cinder.scheduler.flows.create_volume
[req-ebae9974-8741-4a6d-af44-456e506e5612 1149275f4ea84690a9da5b7f442ab48f
4e898758e77c4d3c8d0b0eecf5ae0957 - - -] Failed to schedule_create_volume: No
valid host was found.
Here is my cinder-volume.log
2014-07-14 19:14:15.489 7151 INFO cinder.volume.manager [-] Updating volume
status
2014-07-14 19:14:15.490 7151 WARNING cinder.volume.manager [-] Unable to update
stats, LVMISCSIDriver -2.0.0 driver is uninitialized.
Your response will be appreciated.
Let me know if you need more information.
Regards,
Johnson
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
