tempest uses compute network client to discover fixed_network

[Andrea Frittoli]

When credential providers do not supply a network name to a test, the test falls back to try and use the configured fixed_network_name.

Tempest code will attempt to resolve the name to an ID using the nova network client, which does not work in case of shared networks. It seems that the nova API proxy to the neutron only returns networks that are owned by the tenant, as opposed to networks visible to the tenant, which leads to the configured name to not being honoured.

It would be good to address this as part of bp tempest-resources.

[Joseph Lanoux (joseph-lanoux)]

In addition to this issue, when the internalURL is behind TLS the Nova API proxy to Neutron is broken. Even if Nova network is not deprecated, I'm not sure Nova will fix this.

[Joseph Lanoux (joseph-lanoux)]

Well, my above comment is wrong. My issue is different.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Joseph Lanoux (<email address hidden>) on branch: master
Review: https://review.openstack.org/288408
Reason: Not needed because wrong diagnostic of my issue.

[Ken'ichi Ohmichi (oomichi)]

The resource qa-spec is https://review.openstack.org/#/c/173334/

That will be able to solve this, I hope.

[Ghanshyam Mann (ghanshyammann)]

As it will be addressed by https://review.openstack.org/#/c/173334/