Wrong content in cloudinit-userdata can crash Juju's controller
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
When experimenting with cloudinit-userdata option in a model, I thought naively that it was possible to use exactly the same syntax methods for runcmd of cloudinit.
Anyway, when adding some specific content and then adding a machine, the controller will then simply panic and restart.
Versions :
- MaaS : 3.1
- Juju : 2.9.31
- single juju controller (not tested in HA environment)
Steps :
1) add to cloudinit-userdata :
"postruncmd:
- [ systemctl, restart, snap.lxd.
2) add a machine to the model
3) the controller crashes
https:/
3)a) The machine gets allocated from MaaS point of view.
3)b) the controller restarting will attempt to allocate another machine and crash in a loop until no machine is available from MaaS.
| Joseph Phillips (manadart) wrote | #1 |
| DUFOUR Olivier (odufourc) wrote | #2 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
Does this work if you have a YAML file with contents:
cloudinit-userdata: |
postruncmd:
- "systemctl restart snap.lxd.
And use it to set the model config?