assess_network_health MaaS bundle timeout

[Michael Skalka]

Bundle deployments on MaaS versions of this test are running into intermittent timeout errors resulting in failed tests.

Traceback (most recent call last):
  File "/var/lib/jenkins/juju-ci-tools/utility.py", line 426, in logged_exception
    yield
  File "/var/lib/jenkins/juju-ci-tools/deploy_stack.py", line 897, in runtime_context
    yield
  File "/var/lib/jenkins/juju-ci-tools/deploy_stack.py", line 1007, in booted_context
    yield machines
  File "/var/lib/jenkins/juju-ci-tools/assess_network_health.py", line 642, in main
    start_test(bs_manager.client, args, None)
  File "/var/lib/jenkins/juju-ci-tools/assess_network_health.py", line 608, in start_test
    args.reboot, args.series, maas)
  File "/var/lib/jenkins/juju-ci-tools/assess_network_health.py", line 70, in assess_network_health
    self.setup_testing_environment(client, bundle, target_model, series)
  File "/var/lib/jenkins/juju-ci-tools/assess_network_health.py", line 163, in setup_testing_environment
    client.wait_for_workloads()
  File "/var/lib/jenkins/juju-ci-tools/jujupy/client.py", line 2467, in wait_for_workloads
    timeout=timeout, start=start)
  File "/var/lib/jenkins/juju-ci-tools/jujupy/client.py", line 2235, in _wait_for_status
    raise exc_type(self.env.environment, status)
WorkloadsNotReady: Workloads not ready in network-health-maas-2-1.

[Michael Skalka (mskalka)]

After further investigation the root cause has been determined. Juju is failing to spin up LXD containers on the machines, resulting in a timeout. This has been reported against Juju: https://bugs.launchpad.net/juju/+bug/1677265