Volume attachment silently fails in current devstack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
John Griffith | ||
OpenStack Dashboard (Horizon) |
Invalid
|
Undecided
|
Gabriel Hurley |
Bug Description
With latest devstack when trying to attach a volume to an instance in horizon the volume goes into the attaching state but after ~ 2 minutes it return to the state it was in prior to attempting to attach. Nothing interesting that I could find in nova api log or cinder log.
This is in /var/log/syslog:
Aug 21 18:09:04 EIGHT kernel: [ 373.467923] connection1:0: detected conn error (1019)
Aug 21 18:09:04 EIGHT iscsid: Kernel reported iSCSI connection 1:0 error (1019) state (2)
Aug 21 18:09:21 EIGHT kernel: [ 391.235575] connection1:0: detected conn error (1019)
Aug 21 18:09:22 EIGHT iscsid: Kernel reported iSCSI connection 1:0 error (1019) state (2)
Aug 21 18:09:39 EIGHT kernel: [ 408.498545] connection1:0: detected conn error (1019)
Aug 21 18:09:39 EIGHT iscsid: Kernel reported iSCSI connection 1:0 error (1019) state (2)
Aug 21 18:09:56 EIGHT kernel: [ 425.762905] connection1:0: detected conn error (1019)
Aug 21 18:09:57 EIGHT iscsid: Kernel reported iSCSI connection 1:0 error (1019) state (2)
Aug 21 18:10:13 EIGHT kernel: [ 443.025484] connection1:0: detected conn error (1019)
Aug 21 18:10:14 EIGHT iscsid: Kernel reported iSCSI connection 1:0 error (1019) state (2)
Aug 21 18:10:30 EIGHT kernel: [ 460.287754] connection1:0: detected conn error (1019)
Aug 21 18:10:31 EIGHT iscsid: Kernel reported iSCSI connection 1:0 error (1019) state (2)
Aug 21 18:10:48 EIGHT kernel: [ 477.550922] connection1:0: detected conn error (1019)
Aug 21 18:10:48 EIGHT iscsid: Kernel reported iSCSI connection 1:0 error (1019) state (2)
Aug 21 18:15:53 EIGHT kernel: [ 783.117893] scsi6 : iSCSI Initiator over TCP/IP
Aug 21 18:15:53 EIGHT kernel: [ 783.123425] connection2:0: detected conn error (1019)
Changed in cinder: | |
milestone: | none → folsom-rc1 |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
status: | Fix Released → Fix Committed |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | folsom-rc1 → 2012.2 |
I think the persistent targets change has introduced some problems when upgrading. In this particular case I'm wondering if you had a devstack install previously on this machine prior to pulling the latest version of devstack and re-running?
If this was not a fresh OS and devstack install, let me know a bit more about the system and setup.
If this was in fact a fresh install of the OS and of devstack, could you please try simply running the devstack/ exercises/ volumes. sh test and see if that test passes?