| 2023-10-11 16:21:11 |
Alexander Balderson |
description |
TODO |
While bootstrapping a controller against a local MAAS, Juju requested an instance from MAAS and then instantly said the bootstrap process was canceled. Lately one of the SQA MAAS has been a bit overloaded, and returning 400 errors during some requests. I suspect that is what happened here, however the response from Juju was unclear.
The output is as follows:
Creating Juju controller "foundations-maas" on maas_cloud/default
Looking for packaged Juju agent version 3.1.6 for amd64
No packaged binary found, preparing local Juju agent binary
Launching controller instance(s) on maas_cloud/default...
- k7dg4b (arch=amd64 mem=24G cores=4)
Installing Juju agent on bootstrap instance
Waiting for address
ERROR failed to bootstrap model: cancelled
Looking back in the MAAS logs for the host in the debug output, the system received no actions during the time the bootstrap was happening, which is why it leads me to think that MAAS returned an error. |
|
| 2023-10-11 16:22:13 |
Alexander Balderson |
description |
While bootstrapping a controller against a local MAAS, Juju requested an instance from MAAS and then instantly said the bootstrap process was canceled. Lately one of the SQA MAAS has been a bit overloaded, and returning 400 errors during some requests. I suspect that is what happened here, however the response from Juju was unclear.
The output is as follows:
Creating Juju controller "foundations-maas" on maas_cloud/default
Looking for packaged Juju agent version 3.1.6 for amd64
No packaged binary found, preparing local Juju agent binary
Launching controller instance(s) on maas_cloud/default...
- k7dg4b (arch=amd64 mem=24G cores=4)
Installing Juju agent on bootstrap instance
Waiting for address
ERROR failed to bootstrap model: cancelled
Looking back in the MAAS logs for the host in the debug output, the system received no actions during the time the bootstrap was happening, which is why it leads me to think that MAAS returned an error. |
While bootstrapping a controller against a local MAAS, Juju requested an instance from MAAS and then instantly said the bootstrap process was canceled. Lately one of the SQA MAAS has been a bit overloaded, and returning 400 errors during some requests. I suspect that is what happened here, however the response from Juju was unclear.
The output is as follows:
Creating Juju controller "foundations-maas" on maas_cloud/default
Looking for packaged Juju agent version 3.1.6 for amd64
No packaged binary found, preparing local Juju agent binary
Launching controller instance(s) on maas_cloud/default...
- k7dg4b (arch=amd64 mem=24G cores=4)
Installing Juju agent on bootstrap instance
Waiting for address
ERROR failed to bootstrap model: cancelled
Looking back in the MAAS logs for the host in the debug output, the system received no actions during the time the bootstrap was happening, which is why it leads me to think that MAAS returned an error.
The testrun can be found at:
https://solutions.qa.canonical.com/testruns/691a95f7-0108-4b44-b297-6028fc53f1a9/
But there were no logs collected because no instances go started to collect logs from. |
|
