[rhos-list] Cinder validation
Chen, Hao
Hao.Chen at NRCan-RNCan.gc.ca
Fri Jul 19 15:17:29 UTC 2013
Thanks Eric for the information. The log file showed it was a permission problem. Fixed and working now.
Thanks,
Hao
-----Original Message-----
From: Eric Harney [mailto:eharney at redhat.com]
Sent: July 18, 2013 14:43
To: Chen, Hao
Cc: rhos-list at redhat.com
Subject: Re: [rhos-list] Cinder validation
On 07/18/2013 02:15 PM, Chen, Hao wrote:
> Greetings,
>
> When running "cinder create" and "cinder list", I did not see errors or complains. But in the table listed by "cinder list", "Status" showed "error". Does this mean something wrong in the cinder volume creation?
>
> Thanks in advance for answers.
> Hao
>
> [root at cloud1 ~(keystone_admin)]# cinder create 20
> +---------------------+--------------------------------------+
> | Property | Value |
> +---------------------+--------------------------------------+
> | attachments | [] |
> | availability_zone | nova |
> | bootable | false |
> | created_at | 2013-07-18T17:48:36.395789 |
> | display_description | None |
> | display_name | None |
> | id | 26078eba-d9a0-4575-ac32-7862f4d6c550 |
> | metadata | {} |
> | size | 20 |
> | snapshot_id | None |
> | source_volid | None |
> | status | creating |
> | volume_type | None |
> +---------------------+--------------------------------------+
> [root at cloud1 ~(keystone_admin)]# cinder list
> +--------------------------------------+--------+--------------+------+-------------+----------+-------------+
> | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
> +--------------------------------------+--------+--------------+------+-------------+----------+-------------+
> | 26078eba-d9a0-4575-ac32-7862f4d6c550 | error | None | 20 | None | false | |
> +--------------------------------------+--------+--------------+------+-------------+----------+-------------+
>
Hi,
The cinder create call is asynchronous -- if the creation process starts, that command will not error.
The volume Status will start in "creating" and then transition to "available" or "error" as the operation progresses.
/var/log/cinder/volume.log should contain the reason for failure.
Eric
>
> _______________________________________________
> rhos-list mailing list
> rhos-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rhos-list
>
More information about the rhos-list
mailing list