yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #45816
[Bug 1541702] [NEW] Unable to see the attached cinder volume in instance
Public bug reported:
I have successfully installed OpenStack kilo + XenServer 6.5. I have added a Cinder service it seems to be working because I can connect to my horizon (also by command line) and create volumes and attach them to my instances. Instance name in OpenStack is aaa and it's name in XenServer is instance-0000011e. This is a print screen from my horizon:
|-------------------------------------------------------------------------------------------------------------------------------
| Name Size Status Attached To Availability Zone
| xen_volume2 1GB In-Use Attached to aaa on /dev/xvdb demo
|-------------------------------------------------------------------------------------------------------------------------------
Taking a look on XenCenter connected to my XenServer, seems like the ISCSI mapping is
working fine, this is a print screen:
|----------------------------------------------------------------------------------------------------------------------------
|Position Name Description SR
|0 instance-0000011e root Local storage on xenserver2
|1 tempSR-b76853a3-86f2-4f0a-b78e-eaa4c883172a
|----------------------------------------------------------------------------------------------------------------------------
The tempSR-b76853a3... is the mmaping of the xen_volume2 to my aaa. This storage's type is VDI-per-LUN iSCSI. According to the cinder mapping information the device is mapped to xvdb, but I cant find this volume (dmesg or fdisk -l doesn't show anything), I have noticed two strange behaviors.
1. After attach the volume, boot the instance takes a lot of time.
2. After attach the volume and after restart it (and wait a lot) the dmesg contains this:
[ 0.164935] blkfront: xvda: barrier: enabled
[ 0.179729] xvda: xvda1
[ 0.184022] Setting capacity to 2097152
[ 0.184043] xvda: detected capacity change from 0 to 1073741824
[ 5.260049] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...
225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...
155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s
...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
If I remove the volume and reboot this is not present.
/var/lib/messages @ XenServer 6.5 shows
Jul 16 19:32:09 xenserver2 xapi: [info|xenserver2|6599 storage_unix |VDI.activate D:b152d00698ae|storage-access] vbd/4/xvdb sr:OpaqueRef:e47be30a-b987-a1d8-b7b4-903cca36db53 does not support vdi_activate: doing nothing
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1541702
Title:
Unable to see the attached cinder volume in instance
Status in OpenStack Compute (nova):
New
Bug description:
I have successfully installed OpenStack kilo + XenServer 6.5. I have added a Cinder service it seems to be working because I can connect to my horizon (also by command line) and create volumes and attach them to my instances. Instance name in OpenStack is aaa and it's name in XenServer is instance-0000011e. This is a print screen from my horizon:
|-------------------------------------------------------------------------------------------------------------------------------
| Name Size Status Attached To Availability Zone
| xen_volume2 1GB In-Use Attached to aaa on /dev/xvdb demo
|-------------------------------------------------------------------------------------------------------------------------------
Taking a look on XenCenter connected to my XenServer, seems like the ISCSI mapping is
working fine, this is a print screen:
|----------------------------------------------------------------------------------------------------------------------------
|Position Name Description SR
|0 instance-0000011e root Local storage on xenserver2
|1 tempSR-b76853a3-86f2-4f0a-b78e-eaa4c883172a
|----------------------------------------------------------------------------------------------------------------------------
The tempSR-b76853a3... is the mmaping of the xen_volume2 to my aaa. This storage's type is VDI-per-LUN iSCSI. According to the cinder mapping information the device is mapped to xvdb, but I cant find this volume (dmesg or fdisk -l doesn't show anything), I have noticed two strange behaviors.
1. After attach the volume, boot the instance takes a lot of time.
2. After attach the volume and after restart it (and wait a lot) the dmesg contains this:
[ 0.164935] blkfront: xvda: barrier: enabled
[ 0.179729] xvda: xvda1
[ 0.184022] Setting capacity to 2097152
[ 0.184043] xvda: detected capacity change from 0 to 1073741824
[ 5.260049] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...
225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...
155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s
...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
If I remove the volume and reboot this is not present.
/var/lib/messages @ XenServer 6.5 shows
Jul 16 19:32:09 xenserver2 xapi: [info|xenserver2|6599 storage_unix |VDI.activate D:b152d00698ae|storage-access] vbd/4/xvdb sr:OpaqueRef:e47be30a-b987-a1d8-b7b4-903cca36db53 does not support vdi_activate: doing nothing
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1541702/+subscriptions
Follow ups
