Errors that occur during startup inside "yield deferToThread(inner_start_up)" are hidden
Bug #1498600 reported by
Mike Pontillo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Won't Fix
|
Critical
|
Unassigned | ||
Bug Description
See also: bug #1498262, https:/
Whenever an exception is thrown in the inner_start_up process, the stack trace simply shows the fact that we were starting up, such as:
File "/usr/lib/
yield deferToThread(
This makes it difficult to triage bugs that occur in the startup sequence, and could lead to further support issues in the future.
In the past, I have had to patch the code similar to what is described here in order to triage issues:
https:/
... but this is not sustainable for support purposes.
| Changed in maas: | |
| milestone: | 1.9.0 → 1.9.1 |
| Changed in maas: | |
| milestone: | 1.9.1 → 1.9.2 |
| Changed in maas: | |
| milestone: | 1.9.2 → 1.9.3 |
| Changed in maas: | |
| milestone: | 1.9.3 → 1.9.4 |
| Changed in maas: | |
| milestone: | 1.9.4 → 1.9.5 |
| Changed in maas: | |
| importance: | Critical → High |
| Changed in maas: | |
| importance: | High → Critical |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
We believe that this is not longer an issue in the latest releases of MAAS. If you believe this is still an issue, please re-open this bug report and target it accordingly.