Comment 3 for bug 1710848

Thank you for the quick response!

Yes, we currently have two Openstack subnets associated with 169.254.192.0/18.

This subnet is used for communication between the Neutron HA routers. Neutron
creates one network and a subnet for each tenant/project. This network and
subnet is not associated with a tenant/project, no project_id is recorded in
the database. See attachment with detailed output from openstack.

These subnets and networks was created after we enabled Neutorn HA which we
deploy with neutron-api charm.

https://jujucharms.com/neutron-api/#charm-config-enable-l3ha

I assume that this is correct behavior from Neutron. The HA network is
internal to Neutron and it makes sense that it should not be exposed to the
tenant/project and therefore does not have a project_id.

I have investigated the issue further and it seems that I'm hitting this
problem because my test account has admin access in Openstack, even when
tenant-name is set to the correct tenant/project. I can successfully bootstrap
Juju 2.2.2 with an account with "member" access to the tenant/project.

It seems that there is bug in how Juju filters out subnets by project_id. The
HA networks for Neutron does not have a project_id set. See attached output
from openstack.