Config item 'create_isolated_networks' can't work for some test cases
Bug #1778003 reported by
Dan Xu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Expired
|
Undecided
|
Unassigned |
Bug Description
There is a config item 'create_
However, some test cases still create networks and ignore the 'fixed_
For example,
tempest.
Changed in tempest: | |
assignee: | nobody → Manik Bindlish (manikbindlish) |
Changed in tempest: | |
assignee: | Manik Bindlish (manikbindlish19) → nobody |
To post a comment you must log in.
Scenario are full tests in a meaning they test several features which should be able to interact together (output of one feature is suitable for another one, etc). The mentioned scenario tests cold migration of a server from the beginning (creating a network, floating ip, server ..) until the end (the server is migrated). Therefore it creates its own network regarding the fixed_network_name. Also in the help of the option is written "... this is the network which will be used for creating servers if tempest does not create a network ..." [1].
Let me know if that makes sense. I'll mark the bug as Incomplete for now.
[1] https:/ /opendev. org/openstack/ tempest/ src/commit/ 65bc35d17181fd2 6afd2949a769090 39b93914cb/ tempest/ config. py#L301- L307