This may be a different problem with the same final error message. Investigation shows the initial failure to be:
2021-12-08 21:49:32 WARNING juju.worker.provisioner provisioner_task.go:1114 machine 1/lxd/0 failed to start: websocket: close 1006 (abnormal closure): unexpected EOF
2021-12-08 21:49:32 WARNING juju.worker.provisioner provisioner_task.go:1153 failed to start machine 1/lxd/0 (websocket: close 1006 (abnormal closure): unexpected EOF), retrying in 10s (10 more attempts)
In 1945813, this does not occur, as far as I've seen in the logs. As well, it's 1 out of 7 containers which have this error.
I have found that the machines created have only 1G of memory. If the lxd error does not occur, they fail to have network capability. The error is no longer seen if the machines are created with a memory constraint of 4G
Investigating if a minimum mem of 1G for non controller machines is still an appropriate value.
This may be a different problem with the same final error message. Investigation shows the initial failure to be:
2021-12-08 21:49:32 WARNING juju.worker. provisioner provisioner_ task.go: 1114 machine 1/lxd/0 failed to start: websocket: close 1006 (abnormal closure): unexpected EOF provisioner provisioner_ task.go: 1153 failed to start machine 1/lxd/0 (websocket: close 1006 (abnormal closure): unexpected EOF), retrying in 10s (10 more attempts)
2021-12-08 21:49:32 WARNING juju.worker.
In 1945813, this does not occur, as far as I've seen in the logs. As well, it's 1 out of 7 containers which have this error.
I have found that the machines created have only 1G of memory. If the lxd error does not occur, they fail to have network capability. The error is no longer seen if the machines are created with a memory constraint of 4G
Investigating if a minimum mem of 1G for non controller machines is still an appropriate value.