Comment 4 for bug 1708550

I am re-analysing this bug from what I said during office hour[1]

There are two part of it when it comes to using the network from pre-provisioned credential.

1. Tests need a network to setup on the test created server for checking connectivity or booting the server.

2. Tests testing the network creation and other parts of network service like port, router etc independently.

In case of pre-provisioned cred,
Part 1 is where we need to use priority 1. network mentioned in pre-provisioned priority 2. network mentioned in CONF.compute.fixed_network_name . Tempest take care of this part here[2]. If any test falls under this category and we do not take care of the existing network then we need to fix those by using the existing network or skip those

Now come to part2 which is this bug for, those tests are testing the creation of the network and its subresources etc so we should not use pre-provisioned network or CONF.compute.fixed_network_name there. Test should create the network resources for which test is written to verify.

Another point to consider here is - whether test env want to create the network or not then, tester can avoid network only tests which comes under part-2.

So, this bug does not seem to be valid for me at least listed tests in the description.

[1]http://eavesdrop.openstack.org/meetings/qa/2018/qa.2018-12-06-09.11.log.html#l-91
[2] https://github.com/openstack/tempest/blob/9bb03a9782cf3a882ef4efb6545109d437b6e569/tempest/lib/common/fixed_network.py#L95-L104