Open fnordahl opened 5 years ago
A workaround for this issue would likely be to run JUJU_CONTROLLER=localhost-localhost functest-run-suite
. Would you be able to try that and see if it is a viable workaround until we can identify the best way to manage controller as well?
In my local environment I may have Zaza performing tests on one juju controller (i.e. localhost-localhost) and at the same time using my juju environmet to interface with a local or remote maas controller.
If I have a model on a different controller in focus Zaza will bomb out.
Example Traceback: