<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<span style="font-family:arial,sans-serif;font-size:13px">Hello
everyone!<br>
<br>
I have 3 nova-compute nodes at the zone tdc-a and 3 at tdc-b, and
1 cinder-volume noda at tdc-a and the other at tdc-b. <br>
If I create a volume at the zone tdc-b I can boot an instance
without problem using that volume, but if I try to create an
instance at the zone tdc-a it fails, because the volume was
created at the zone nova, instead use tdc-a or tdc-b.<br>
root@controller01:/etc/nova# cinder list<br>
+--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+<br>
| ID | Status | Display Name |
Size | Volume Type | Bootable | Attached
to |<br>
+--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+<br>
| 159051c5-4124-4d1a-aa76-ff355bbc1319 | in-use | vol-a |
1 | None | true |
a66f75e3-b5d1-49d1-bbe7-08d58f504b1a |<br>
| 5546f22d-afc9-4712-b9c4-3328a3c375d3 | error | |
1 | None | false
| |<br>
| 588719d6-02b3-435c-8f99-279ada7781f9 | in-use | vol-b |
1 | None | true |
ab600eed-d72c-48fe-9f32-79e6d9507647 |<br>
+--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+<br>
<br>
root@controller01:/etc/nova# cinder show
5546f22d-afc9-4712-b9c4-3328a3c375d3<br>
+--------------------------------+--------------------------------------+<br>
| Property |
Value |<br>
+--------------------------------+--------------------------------------+<br>
| attachments |
[] |<br>
| availability_zone |
nova |<br>
| bootable |
false |<br>
| created_at |
2014-05-15T15:31:24.000000 |<br>
| display_description
| |<br>
| display_name
| |<br>
| encrypted |
False |<br>
| id |
5546f22d-afc9-4712-b9c4-3328a3c375d3 |<br>
| metadata |
{} |<br>
| os-vol-host-attr:host |
None |<br>
| os-vol-mig-status-attr:migstat |
None |<br>
| os-vol-mig-status-attr:name_id |
None |<br>
| os-vol-tenant-attr:tenant_id |
2def817a4d7f4097be01c06d009362ca |<br>
| size |
1 |<br>
| snapshot_id |
None |<br>
| source_volid |
None |<br>
| status |
error |<br>
| volume_type |
None |<br>
+--------------------------------+--------------------------------------+<br>
<br>
root@controller01:/etc/nova# cinder availability-zone-list<br>
+-------+-----------+<br>
| Name | Status |<br>
+-------+-----------+<br>
| tdc-a | available |<br>
| tdc-b | available |<br>
+-------+-----------+<br>
<br>
root@controller01:/etc/nova# nova availability-zone-list<br>
+-----------------------+----------------------------------------+<br>
| Name | Status |<br>
+-----------------------+----------------------------------------+<br>
| internal | available |<br>
| |- controller01 | |<br>
| | |- nova-conductor | enabled :-) 2014-05-15T15:36:46.000000 |<br>
| | |- nova-cert | enabled :-) 2014-05-15T15:36:45.000000 |<br>
| | |- nova-consoleauth | enabled :-) 2014-05-15T15:36:45.000000 |<br>
| | |- nova-scheduler | enabled :-) 2014-05-15T15:36:46.000000 |<br>
| tdc-b | available |<br>
| |- compute05 | |<br>
| | |- nova-compute | enabled :-) 2014-05-15T15:36:51.000000 |<br>
| |- compute06 | |<br>
| | |- nova-compute | enabled :-) 2014-05-15T15:36:49.000000 |<br>
| |- compute08 | |<br>
| | |- nova-compute | enabled :-) 2014-05-15T15:36:48.000000 |<br>
| tdc-a | available |<br>
| |- compute01 | |<br>
| | |- nova-compute | enabled :-) 2014-05-15T15:36:46.000000 |<br>
| |- compute03 | |<br>
| | |- nova-compute | enabled :-) 2014-05-15T15:36:49.000000 |<br>
| |- compute04 | |<br>
| | |- nova-compute | enabled :-) 2014-05-15T15:36:47.000000 |<br>
+-----------------------+----------------------------------------+<br>
<br>
<br>
Anyone know why nova is triying to create a new volume at the nova
zone?<br>
Thanks<br>
<br>
Fernando Cortijo<br>
</span>
</body>
</html>