tempest uses compute network client to discover fixed_network

Bug #1551218 reported by Andrea Frittoli on 2016-02-29
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

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) wrote :

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.

Changed in tempest:
assignee: nobody → Joseph Lanoux (joseph-lanoux)
status: New → In Progress
Joseph Lanoux (joseph-lanoux) wrote :

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

Changed in tempest:
assignee: Joseph Lanoux (joseph-lanoux) → nobody

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.

Changed in tempest:
status: In Progress → New
Ken'ichi Ohmichi (oomichi) wrote :

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

That will be able to solve this, I hope.

Ghanshyam Mann (ghanshyammann) wrote :

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

Changed in tempest:
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers