+++ This bug was initially created as a clone of Bug #1726471 +++ Description of problem: RemoteDeeplyNestedStackTest always fails because the hardcoded network name. An error log. ~~~ File "/usr/lib/python2.7/site-packages/heatclient/common/http.py", line 320, in request raise exc.from_response(resp) heatclient.exc.HTTPBadRequest: ERROR: Parameter 'network_name' is invalid: Error validating value 'public': Unable to find network with name or id 'public' ~~~ Version-Release number of selected component (if applicable): Current python-heat-test-tempest in RHOSP13 and upstream. How reproducible: Always Steps to Reproduce: 1. Create a public network whose name is not 'public'. 2. Run the test. 3. Actual results: The test fails. Expected results: The test doesn't fail. Additional info: The issue occurs by the hardcoded network name in test_remote_deeply_nested.py. --- Additional comment from Keigo Noha on 2019-07-04 06:54:20 UTC --- Hi Rabi, Thank you for your review in upstream. The gerrit is now merged status. Would you be able to start the backport process into RHOSP13? Best Regards, Keigo Noha --- Additional comment from Keigo Noha on 2019-07-19 00:12:31 UTC --- Hi Rabi, I'm sorry for interrupting you. Would you proceed the backport into RHOSP13? Kind Regards, Keigo Noha
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3747