Ask Your Question
0

stay in attaching volume to instances

asked 2013-04-12 08:42:08 -0500

ollimaller gravatar image

Hi,

i have create a OpenStack Grizzly MultiNode Infrastrucutr.

Controlnode management network 192.168.0.1 / external 10.123.4.xxx Computenode management network 192.168.0.2 / data 10.10.10.2 networknode management network 192.168.0.3 / external 10.123.4.xxx /data 10.10.10.1

I Followed this Install Guide https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst (https://github.com/mseknibilel/OpenSt...)

When i attach a Volume to a existing instaces, in will be staying in attaching since 12 hours. I have reboot the control and compute node. Where could be the problem? Who can help me?

cinder-api.log 2013-04-12 10:09:30 AUDIT [cinder.api.v1.volumes] vol={'volume_metadata': [], 'availability_zone': u'nova', 'terminated_at': None, 'updated_at': datetime.datetime(2013, 4, 11, 14, 48, 12), 'snapshot_id': None, 'ec2_id': None, 'mountpoint': None, 'deleted_at': None, 'id': u'0358222b-3d77-438b-af1a-237db6c22865', 'size': 40L, 'user_id': u'fdcf86f4e7b843a4a69907423d32d073', 'attach_time': None, 'display_description': u'', 'project_id': u'd2a556839afe4e7a9eda53cd0b4e54f0', 'launched_at': datetime.datetime(2013, 4, 11, 14, 44, 31), 'scheduled_at': datetime.datetime(2013, 4, 11, 14, 44, 30), 'status': u'attaching', 'volume_type_id': None, 'deleted': False, 'provider_location': u'10.123.4.101:3260,1 iqn.2010-10.org.openstack:volume-0358222b-3d77-438b-af1a-237db6c22865 0', 'volume_glance_metadata': [], 'host': u'controlnode', 'source_volid': None, 'provider_auth': u'CHAP K9y8DoFPAG8LCTnYHFhH diikBrj9DfTLai92DMP3', 'display_name': u'kvasy', 'instance_uuid': None, 'created_at': datetime.datetime(2013, 4, 11, 14, 44, 30), 'attach_status': u'detached', 'volume_type': None} 2013-04-12 10:09:30 INFO [cinder.api.openstack.wsgi] http://10.123.4.101:8776/v1/d2a556839afe4e7a9eda53cd0b4e54f0/volumes/0358222b-3d77-438b-af1a-237db6c22865 (http://10.123.4.101:8776/v1/d2a556839...) returned with HTTP 200 2013-04-12 10:09:34 INFO [cinder.api.openstack.wsgi] GET http://10.123.4.101:8776/v1/d2a556839afe4e7a9eda53cd0b4e54f0/os-quota-sets/d2a556839afe4e7a9eda53cd0b4e54f0 (http://10.123.4.101:8776/v1/d2a556839...) 2013-04-12 10:09:34 INFO [cinder.api.openstack.wsgi] http://10.123.4.101:8776/v1/d2a556839afe4e7a9eda53cd0b4e54f0/os-quota-sets/d2a556839afe4e7a9eda53cd0b4e54f0 (http://10.123.4.101:8776/v1/d2a556839...) returned with HTTP 200 2013-04-12 10:09:34 INFO [cinder.api.openstack.wsgi] GET http://10.123.4.101:8776/v1/d2a556839afe4e7a9eda53cd0b4e54f0/volumes/detail (http://10.123.4.101:8776/v1/d2a556839...) 2013-04-12 10:09:34 AUDIT [cinder.api.v1.volumes] vol= 2013-04-12 10:09:34 INFO [cinder.api.openstack.wsgi] http://10.123.4.101:8776/v1/d2a556839afe4e7a9eda53cd0b4e54f0/volumes/detail (http://10.123.4.101:8776/v1/d2a556839...) returned with HTTP 200 2013-04-12 10:32:02 INFO [cinder.api.openstack.wsgi] GET http://10.123.4.101:8776/v1/d2a556839afe4e7a9eda53cd0b4e54f0/volumes/detail (http://10.123.4.101:8776/v1/d2a556839...) 2013-04-12 10:32:02 AUDIT [cinder.api.v1.volumes] vol= 2013-04-12 10:32:02 INFO [cinder.api.openstack.wsgi] http://10.123.4.101:8776/v1/d2a556839afe4e7a9eda53cd0b4e54f0/volumes/detail (http://10.123.4.101:8776/v1/d2a556839...) returned with HTTP 200 2013-04-12 10:32:03 INFO [cinder.api.openstack.wsgi] GET http://10.123.4.101:8776/v1/d2a556839afe4e7a9eda53cd0b4e54f0/volumes/0358222b-3d77-438b-af1a-237db6c22865 (http://10.123.4.101:8776/v1/d2a556839...) 2013-04-12 10:32:03 AUDIT [cinder.api.v1.volumes] vol={'volume_metadata': [], 'availability_zone': u'nova', 'terminated_at': None, 'updated_at': datetime.datetime(2013, 4 ... (more)

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2013-04-16 06:10:46 -0500

ollimaller gravatar image

Another problem that i have, i can't start instances with Volumes. The instances going directly into a error status after starting.

edit flag offensive delete link more
0

answered 2013-04-17 07:49:05 -0500

ollimaller gravatar image

root@controlnode:~# cinder list +--------------------------------------+-----------+--------------+------+-------------+----------+-------------+ | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+-----------+--------------+------+-------------+----------+-------------+ | 45d6f5b6-e623-41d4-b8c3-994c176a6b93 | creating | admin_test | 45 | Performance | false | | | a12d50c8-f7e5-46f8-9e9f-4d0a0fb2c50e | available | admin_test2 | 30 | backup | false | | | b365a120-eccd-4b73-8b2e-cf95606addf1 | available | admin_test3 | 15 | Performance | false | | +--------------------------------------+-----------+--------------+------+-------------+----------+-------------+ root@controlnode:~# locate iqn root@controlnode:~#

edit flag offensive delete link more
0

answered 2013-04-26 11:18:00 -0500

ollimaller gravatar image

Adding this line to compute node's nova.conf helped resolve the issue. cinder_catalog_info=volume:cinder:internalURL

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-04-12 08:42:08 -0500

Seen: 310 times

Last updated: Apr 26 '13