MAAS failed to start

[Anton Troyanov]

MAAS snap 3.5.0~alpha1-14845-g.8f6c97d2

Observed behaviour: MAAS doesn't work
1. `sudo maas status` doesn't return anything
2. `journalctl -feu snap.maas.pebble.service -t maas.pebble` last log statement is 6h old
3. rackd was started, regiond was not

It might be a Pebble issue, because `sudo snap run --shell maas.pebble -- run-pebble version` just hangs and never returns anything?

Log of a failed start:
https://pastebin.canonical.com/p/rGBwpWwmYr/

Log of a normal start:
https://pastebin.canonical.com/p/YzzjqrhT2w/

Doing `snap restart maas` helps

[Anton Troyanov (troyanov)]

Attempt to bump Pebble version to 1.4.0, to see if that will make any difference
https://code.launchpad.net/~troyanov/maas/+git/maas/+merge/452646

[Anton Troyanov (troyanov)]

Might be related:
https://github.com/canonical/pebble/issues/163

[Anton Troyanov (troyanov)]

Updating Pebble to 1.4.0 didn't help.

https://pastebin.canonical.com/p/H5bzswhwB3/

[Anton Troyanov (troyanov)]

Created a new issue in Pebble https://github.com/canonical/pebble/issues/314

[Adam Collard (adam-collard)]

Updating Pebble to 1.5.0 still didn't help much

[Anton Troyanov (troyanov)]

Updated Pebble to upstream 1.7.0

FTR: we didn't observe this issue with 1.5.0 fork https://github.com/maas/pebble/commit/0f47d0d486b3d8eda1a6b059bf85b7ad0ad9a8c9

[Anton Troyanov (troyanov)]

Pebble got stuck again. Here is a traceback obtained with `pkill -TRAP pebble`

[Anton Troyanov (troyanov)]

The issue is fixed
https://github.com/canonical/pebble/issues/314