Hello everyone! 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. 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. root@controller01:/etc/nova# cinder list +--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+ | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+ | 159051c5-4124-4d1a-aa76-ff355bbc1319 | in-use | vol-a | 1 | None | true | a66f75e3-b5d1-49d1-bbe7-08d58f504b1a | | 5546f22d-afc9-4712-b9c4-3328a3c375d3 | error | | 1 | None | false | | | 588719d6-02b3-435c-8f99-279ada7781f9 | in-use | vol-b | 1 | None | true | ab600eed-d72c-48fe-9f32-79e6d9507647 | +--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+
root@controller01:/etc/nova# cinder show
5546f22d-afc9-4712-b9c4-3328a3c375d3
+--------------------------------+--------------------------------------+
| Property | Value |
+--------------------------------+--------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| created_at | 2014-05-15T15:31:24.000000 |
| display_description | |
| display_name | |
| encrypted | False |
| id | 5546f22d-afc9-4712-b9c4-3328a3c375d3 |
| metadata | {} |
| os-vol-host-attr:host | None |
| os-vol-mig-status-attr:migstat | None |
| os-vol-mig-status-attr:name_id | None |
| os-vol-tenant-attr:tenant_id | 2def817a4d7f4097be01c06d009362ca |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | error |
| volume_type | None |
+--------------------------------+--------------------------------------+
root@controller01:/etc/nova# cinder availability-zone-list
+-------+-----------+
| Name | Status |
+-------+-----------+
| tdc-a | available |
| tdc-b | available |
+-------+-----------+
root@controller01:/etc/nova# nova availability-zone-list
+-----------------------+----------------------------------------+
| Name | Status |
+-----------------------+----------------------------------------+
| internal | available |
| |- controller01 | |
| | |- nova-conductor | enabled :-) 2014-05-15T15:36:46.000000 |
| | |- nova-cert | enabled :-) 2014-05-15T15:36:45.000000 |
| | |- nova-consoleauth | enabled :-) 2014-05-15T15:36:45.000000 |
| | |- nova-scheduler | enabled :-) 2014-05-15T15:36:46.000000 |
| tdc-b | available |
| |- compute05 | |
| | |- nova-compute | enabled :-) 2014-05-15T15:36:51.000000 |
| |- compute06 | |
| | |- nova-compute | enabled :-) 2014-05-15T15:36:49.000000 |
| |- compute08 | |
| | |- nova-compute | enabled :-) 2014-05-15T15:36:48.000000 |
| tdc-a | available |
| |- compute01 | |
| | |- nova-compute | enabled :-) 2014-05-15T15:36:46.000000 |
| |- compute03 | |
| | |- nova-compute | enabled :-) 2014-05-15T15:36:49.000000 |
| |- compute04 | |
| | |- nova-compute | enabled :-) 2014-05-15T15:36:47.000000 |
+-----------------------+----------------------------------------+
Anyone know why nova is triying to create a new volume at the nova zone?
Thanks
Fernando Cortijo
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
