MAAS failed to start
Bug #2038307 reported by
Anton Troyanov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
High
|
Unassigned | ||
Bug Description
MAAS snap 3.5.0~alpha1-
Observed behaviour: MAAS doesn't work
1. `sudo maas status` doesn't return anything
2. `journalctl -feu snap.maas.
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:/
Log of a normal start:
https:/
Doing `snap restart maas` helps
Related branches
~troyanov/maas:bump-temporal-version
- Adam Collard (community): Approve
-
Diff: 13 lines (+1/-1)1 file modifieddebian/control (+1/-1)
| Changed in maas: | |
| status: | New → Triaged |
| milestone: | none → 3.5.0 |
Revision history for this message
| Anton Troyanov (troyanov) wrote | #1 |
| Changed in maas: | |
| importance: | Undecided → High |
Revision history for this message
| Anton Troyanov (troyanov) wrote | #2 |
Revision history for this message
| Anton Troyanov (troyanov) wrote | #3 |
Revision history for this message
| Anton Troyanov (troyanov) wrote | #4 |
To post a comment you must log in.
Attempt to bump Pebble version to 1.4.0, to see if that will make any difference
https:/