Comment 7 for bug 1654144

We actually have situation where floating ip pool has no availability zone set.

+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | UP |
| availability_zone_hints | |
| availability_zones | |
| created_at | 2016-11-02T09:45:26 |
| description | |
| dns_domain | |
| id | a853f3b5-3901-4f26-9579-65a01e49c2a4 |
| ipv4_address_scope | None |
| ipv6_address_scope | None |
| is_default | False |
| mtu | 1500 |
| name | public_floating_net |
| port_security_enabled | True |
| project_id | None |
| provider:network_type | flat |
| provider:physical_network | physnet1 |
| provider:segmentation_id | None |
| qos_policy_id | None |
| revision_number | 4 |
| router:external | External |
| segments | None |
| shared | False |
| status | ACTIVE |
| subnets | b53a8314-a48f-409e-8325-68ba02ae7197 |
| updated_at | 2016-11-02T09:45:40 |
+---------------------------+--------------------------------------+
(openstack)

When using juju 2.1.1 with external-network configuration option during bootstrap I get error:

07:52:52 DEBUG juju.provider.openstack networking.go:198 external network a853f3b5-3901-4f26-9579-65a01e49c2a4 was found, however not in the nova availability zone

My opinion is that external networks don't have to be on certain availability zone.