device name is inconsistent

Asked by alven yen

Hi,

I construct a openstack environment in single server, and everything is work fine, but only problem is when I attach a volume to the instance, the device name appears in the instance is inconsistent with pages(ex. page shows "/dev/vdf", but actual is "/dev/vdl"). I'm sure the device name I assign is empty, and I found the device name will auto generate sequentially. First time I attached a volume to "/dev/vdf", it appeared in "/dev/vdf". Next time, I detached and attached same volume again, it appeared in "/dev/vdg". But "/dev/vdf" is empty, because I just detached device from this device name, and the pages always shows "/dev/vdf".

My nova.conf is as below:
--------------------------------------------------------------------------------------------------------------------------------
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--verbose
--s3_host=172.18.0.101
--rabbit_host=192.168.0.1
--cc_host=192.168.0.1
--ec2_url=http://172.18.0.101:8773/services/Cloud
--network_size=15
--FAKE_subdomain=ec2
--sql_connection=mysql://root:Password@172.18.0.101/nova
--glance_host=192.168.0.1
--image_service=nova.image.glance.GlanceImageService
--routing_source_ip=192.168.0.1
--flat_interface=eth0
--network_manager=nova.network.manager.FlatDHCPManager
--flat_network_dhcp_start=192.168.0.2
--flat_injected=False
--iscsi_ip_prefix=192.168.0
 --------------------------------------------------------------------------------------------------------------------------------

Does anyone have same problem?

Thanks,

Alven

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Vish Ishaya
Solved:
Last query:
Last reply:
Revision history for this message
Best Vish Ishaya (vishvananda) said :
#1

This is a limitation of the way kvm attaches disks and the way that udev names them. It seems like someone could come up with a fancy udev solution that actually symlinks the disk based on querying metadata, but it hasn't been written yet.

Vish

On Jul 11, 2011, at 8:55 PM, alven yen wrote:

> New question #164498 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/164498
>
> Hi,
>
> I construct a openstack environment in single server, and everything is work fine, but only problem is when I attach a volume to the instance, the device name appears in the instance is inconsistent with pages(ex. page shows "/dev/vdf", but actual is "/dev/vdl"). I'm sure the device name I assign is empty, and I found the device name will auto generate sequentially. First time I attached a volume to "/dev/vdf", it appeared in "/dev/vdf". Next time, I detached and attached same volume again, it appeared in "/dev/vdg". But "/dev/vdf" is empty, because I just detached device from this device name, and the pages always shows "/dev/vdf".
>
> My nova.conf is as below:
> --------------------------------------------------------------------------------------------------------------------------------
> --dhcpbridge_flagfile=/etc/nova/nova.conf
> --dhcpbridge=/usr/bin/nova-dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --verbose
> --s3_host=172.18.0.101
> --rabbit_host=192.168.0.1
> --cc_host=192.168.0.1
> --ec2_url=http://172.18.0.101:8773/services/Cloud
> --network_size=15
> --FAKE_subdomain=ec2
> --sql_connection=mysql://root:Password@172.18.0.101/nova
> --glance_host=192.168.0.1
> --image_service=nova.image.glance.GlanceImageService
> --routing_source_ip=192.168.0.1
> --flat_interface=eth0
> --network_manager=nova.network.manager.FlatDHCPManager
> --flat_network_dhcp_start=192.168.0.2
> --flat_injected=False
> --iscsi_ip_prefix=192.168.0
> --------------------------------------------------------------------------------------------------------------------------------
>
> Does anyone have same problem?
>
> Thanks,
>
> Alven
>
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Revision history for this message
alven yen (alven-yen) said :
#2

Thanks Vish Ishaya, that solved my question.