Volume will not attach

Asked by Tom Purcell

Hello

I'm running openstack-nova.noarch 2012.1-4.el6 on a RHEL 6.2. I have the entire stack running on one node. All service are up and running and appear healthy.

My issue has to do with creating a volume. We've only attempted to create one volume so far. The horizon web interface displays an updating icon and says the volume is attaching. The nova commands display the following:

[root@open-stack1 red]# nova volume-list
+----+-----------+--------------+------+-------------+-------------+
| ID | Status | Display Name | Size | Volume Type | Attached to |
+----+-----------+--------------+------+-------------+-------------+
| 1 | attaching | None | 1 | None | |
+----+-----------+--------------+------+-------------+-------------+
[root@open-stack1 red]# nova volume-show 1
+---------------------+---------------------+
| Property | Value |
+---------------------+---------------------+
| attachments | [] |
| availability_zone | nova |
| created_at | 2012-05-11 18:25:29 |
| display_description | None |
| display_name | None |
| id | 1 |
| metadata | {} |
| size | 1 |
| snapshot_id | None |
| status | attaching |
| volume_type | None |
+---------------------+---------------------+

As you can see its been attempting to attach since 5/11. One more additional piece of information. The nova-volumes LVM volume group was set up via losetup. Initially on reboot the nova-volume service would fail because "volume group nova-volumes doesn't exist". This occurred because the losetup configuration did not survive a reboot. We have since resolved that problem and the nova-volume service starts clean.

My question is how do I figure out what's wrong with the volume? I've gone through the logs and can't find anything indicating a problem. Looking at the api I cannot figure out anything that will provide more information than that provided above. How do we debug this?

Additionally, when I attempt to delete the volume from the web interface I get "Internal Server Error" as a response. I'll post details of that on the horizon question list.

Thanks
Tom

Question information

Language:
English Edit question
Status:
Answered
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Tom Purcell (tpurcell) said :
#1

Hello

Just providing link to related dashboard question: https://answers.launchpad.net/horizon/+question/198220

Thanks
Tom

Revision history for this message
Tom Purcell (tpurcell) said :
#2

Hello

This is still an issue for us. Is there some additional information I should provide? Am I missing something obvious>

Thanks
Tom

Revision history for this message
Vish Ishaya (vishvananda) said :
#3

yes, I would try again using the command line with a new volume and post the nova-volume logs and nova-compute logs when it fails. It is quite possible you have some config options set imporoperly.

Revision history for this message
Koji (kj-tanaka) said :
#4

I have the same problem. Nova's log doesn't provide good information, but libvirt log says like this.

Jun 5 08:56:31 i121 kernel: [ 278.760529] sd 4:0:0:1: Attached scsi generic sg2 type 0
Jun 5 08:56:31 i121 kernel: [ 278.761506] sd 4:0:0:1: [sdb] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
Jun 5 08:56:31 i121 kernel: [ 278.762224] sd 4:0:0:1: [sdb] Write Protect is off
Jun 5 08:56:31 i121 kernel: [ 278.762229] sd 4:0:0:1: [sdb] Mode Sense: 49 00 00 08
Jun 5 08:56:31 i121 kernel: [ 278.762749] sd 4:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 5 08:56:31 i121 kernel: [ 278.774284] sdb: unknown partition table
Jun 5 08:56:31 i121 kernel: [ 278.775839] sd 4:0:0:1: [sdb] Attached SCSI disk

Revision history for this message
Koji (kj-tanaka) said :
#5

I can attach a volume if I attach one from Dashboard when I boot an instance. But if I detach it, I can't attach it again. I want to get some information from logs, but no luck... And euca-attach-volume doesn't work, with the same result...

Could anyone please give me a hint or something?

Revision history for this message
Koji (kj-tanaka) said :
#6

Can you help with this problem?

Provide an answer of your own, or ask Tom Purcell for more information if necessary.

To post a message you must log in.