volume connect failed due to lun-1 missing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Undecided
|
Unassigned |
Bug Description
We're working on Ubuntu 12.10 with Folsom release cinder-volume 2012.2.1-0ubuntu1.
We met an error when we try to attach a volume to an instance.
We found error log at compute.log like this:
2013-01-07 00:28:33 ERROR nova.compute.
69279 2013-01-07 00:28:33 TRACE nova.compute.
69280 2013-01-07 00:28:33 TRACE nova.compute.
69281 2013-01-07 00:28:33 TRACE nova.compute.
69282 2013-01-07 00:28:33 TRACE nova.compute.
69283 2013-01-07 00:28:33 TRACE nova.compute.
69284 2013-01-07 00:28:33 TRACE nova.compute.
69285 2013-01-07 00:28:33 TRACE nova.compute.
69286 2013-01-07 00:28:33 TRACE nova.compute.
69287 2013-01-07 00:28:33 TRACE nova.compute.
69288 2013-01-07 00:28:33 TRACE nova.compute.
69289 2013-01-07 00:28:33 TRACE nova.compute.
69290 2013-01-07 00:28:33 TRACE nova.compute.
69291 2013-01-07 00:28:33 TRACE nova.compute.
69292 2013-01-07 00:28:33 TRACE nova.compute.
69293 2013-01-07 00:28:33 TRACE nova.compute.
69294 2013-01-07 00:28:33 TRACE nova.compute.
69295 2013-01-07 00:28:33 TRACE nova.compute.
69296 2013-01-07 00:28:33 TRACE nova.compute.
69297 2013-01-07 00:28:33 TRACE nova.compute.
So we back to iscsi server side to check our iscsi target, then we found an strange phenomenon: LUN:1 is missing !!!!!
Target 79: iqn.2010-
System information:
Driver: iscsi
State: ready
I_T nexus information:
I_T nexus: 788
IP Address: 192.168.4.86
LUN information:
LUN: 0
Type: controller
SCSI ID: IET 004f0000
SCSI SN: beaf790
Size: 0 MB, Block size: 1
Online: Yes
Backing store type: null
Backing store path: None
Backing store flags:
Account information:
ACL information:
ALL
What this issue confuse us most is that’s it do not happen to every LVM, just some of them.
For example, when we create 50 volumes at one machine, and try to attach them to instances, always have 1 failed but other 49 are just working fine.
Changed in cinder: | |
status: | New → Incomplete |
Is there any consistency on which target this occurs on? I'm looking at putting a check in the create for this, however it doesn't address the root cause of the problem.