Ask Your Question
0

Unable to see the attached volume in instance

asked 2013-04-11 13:26:40 -0600

shantha-kumar gravatar image

Hi,

I have single node openstack setup where ( compute + controller ) installed and running with all the required services.

I am able to create the volume using cinder and assign to instance but unable to see the attached volume inside the Virtual instances

################################ Services ################################ keystone start/running, process 7740 glance-api start/running, process 7742 glance-registry start/running, process 7744 mysql start/running, process 7770 quantum-server start/running, process 7829 quantum-dhcp-agent start/running, process 7846 quantum-metadata-agent start/running, process 7851 quantum-l3-agent start/running, process 7866 quantum-plugin-linuxbridge-agent start/running, process 7871 * Checking DNS forwarder and DHCP server dnsmasq * (dead, pid file exists) nova-api start/running, process 8073 nova-cert start/running, process 8084 nova-compute start/running, process 8096 nova-conductor start/running, process 8107 nova-consoleauth start/running, process 8122 nova-novncproxy start/running, process 8134 nova-scheduler start/running, process 8152 libvirt-bin start/running, process 2035 Apache2 is running (pid 8247). * memcached is running

#####################################

nova list +--------------------------------------+--------------+--------+-------------------+ | ID | Name | Status | Networks | +--------------------------------------+--------------+--------+-------------------+ | 3d34826f-480e-40bb-a2d5-9bd32b14ee05 | SB | ACTIVE | grzmrnw=50.50.1.4 | | 0583f7a7-ed02-43b6-b3c7-c1d7405426b5 | Testvm-ciros | ACTIVE | grzmrnw=50.50.1.3 | +--------------------------

cinder list +--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+ | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+ | 03d68746-6519-4f63-91d3-ba96603cf8cd | in-use | Testvol1 | 2 | None | false | 3d34826f-480e-40bb-a2d5-9bd32b14ee05 | +--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+

Nova Compute log: #############

2013-04-12 07:17:40.957 8096 INFO nova.compute.manager [-] Updating host status 2013-04-12 07:17:42.408 AUDIT nova.compute.manager [req-2fd028df-8eda-48bd-a9ad-098074264bdb 4b106ff812b54472b8e2d3596524f730 fedfaa89548e41188c2dbd6f96d0de4a] [instance: 3d34826f-480e-40bb-a2d5-9bd32b14ee05] Attaching volume 03d68746-6519-4f63-91d3-ba96603cf8cd to /dev/vdb 2013-04-12 07:17:42.477 WARNING nova.virt.libvirt.utils [req-2fd028df-8eda-48bd-a9ad-098074264bdb 4b106ff812b54472b8e2d3596524f730 fedfaa89548e41188c2dbd6f96d0de4a] systool is not installed 2013-04-12 07:17:42.543 WARNING nova.virt.libvirt.utils [req-2fd028df-8eda-48bd-a9ad-098074264bdb 4b106ff812b54472b8e2d3596524f730 fedfaa89548e41188c2dbd6f96d0de4a] systool is not installed 2013-04-12 07:18:42.130 8096 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources 2013-04-12 07:18:42.387 8096 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 141987 2013-04-12 07:18:42.388 8096 AUDIT nova.compute.resource_tracker [-] Free disk (GB): -11 2013-04-12 07:18:42.388 8096 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 22 2013-04-12 07:18:42.443 8096 INFO nova.compute.resource_tracker [-] Compute_service record updated for grzrc3:grzrc3

Virtual Machine: ############

Log into VM

iaasc@grzrc3:~$ ssh cirros@50.50.1.4 The authenticity of host '50.50.1.4 (50.50.1.4)' can't be established. RSA key fingerprint is 76:65:41:41:04:a0:2e:29:b4:8a:f5:11:a5:87:64:10. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '50.50.1.4' (RSA) to the list of known hosts. cirros@50.50.1.4's password: $ $ fdisk -l $

Kindly help me on this.

edit retag flag offensive close merge delete

12 answers

Sort by ยป oldest newest most voted
0

answered 2013-05-17 06:41:32 -0600

drolfe gravatar image

I wrote up a blog post really for my own reference but you might as well have a look if your having issues with cinder as it covers the basics

http://drolfe.github.io/drolfe/blog/2013/05/01/troubleshoot-cinder-volumes/ (http://drolfe.github.io/drolfe/blog/2...)

edit flag offensive delete link more
0

answered 2013-05-17 14:53:39 -0600

Thanks Xinxin and Daniel. Those information were really useful. In addition, here is what my observations were:

The confusion was that if you attach a device /dev/vdc, it used to get detected as /dev/vdb. So, it looks like when you attach a device with any path (/dev/vdc or /dev/vdd), OpenStack takes care of attaching with next device in the loop. For example, if you select a flavor m1.small, the devices that gets created by default are /dev/vda (root) and /dev/vdb (ephemeral). So, when you attach disk to that instance, it will show up as /dev/vdc (regardless of which device name is suggested while attaching). Seems to be a bug, but we know now how it works.

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-11 13:26:40 -0600

Seen: 2,467 times

Last updated: May 17 '13