tempest ignors network.public_network_id values and discovers other shared network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I have two networks:
(overcloud) [stack@undercloud-0 ~]$ openstack network show private
+------
| Field | Value |
+------
| admin_state_up | UP |
| availability_
| availability_zones | |
| created_at | 2018-09-
| description | |
| dns_domain | None |
| id | 7a791ac9-
| ipv4_address_scope | None |
| ipv6_address_scope | None |
| is_default | None |
| is_vlan_transparent | None |
| mtu | 1450 |
| name | private |
| port_security_
| project_id | f24c27056de14ec
| provider:
| provider:
| provider:
| qos_policy_id | None |
| revision_number | 4 |
| router:external | Internal |
| segments | None |
| shared | True |
| status | ACTIVE |
| subnets | |
| tags | |
| updated_at | 2018-09-
+------
(overcloud) [stack@undercloud-0 ~]$ openstack network show public
+------
| Field | Value |
+------
| admin_state_up | UP |
| availability_
| availability_zones | nova |
| created_at | 2018-08-
| description | |
| dns_domain | None |
| id | e2de7ebb-
| ipv4_address_scope | None |
| ipv6_address_scope | None |
| is_default | False |
| is_vlan_transparent | None |
| mtu | 1500 |
| name | public |
| port_security_
| project_id | f24c27056de14ec
| provider:
| provider:
| provider:
| qos_policy_id | None |
| revision_number | 9 |
| router:external | External |
| segments | None |
| shared | False |
| status | ACTIVE |
| subnets | 972ba648-
| tags | |
| updated_at | 2018-09-
+------
and this test is failing due to the shared private network:
tempest.
with following error:
"Multiple possible networks found, use a Network ID to be more specific."
my network section in tempest.conf has the following variables set:
[network]
region = regionOne
public_network_id = e2de7ebb-
floating_
fixed_network_name = public
According to the error message, I should use a network ID, which I did, so therefore it seems like a tempest bug.
The problem seems to be with the shared network, if I set that network as --no-share, the test works as expected.
Changed in tempest: | |
status: | Fix Committed → Fix Released |
Related fix proposed to branch: master /review. openstack. org/615425
Review: https:/