`cloud-init analyze` depends on the upstream-shipped log format to function
Bug #1876794 reported by
Dan Watkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Expired
|
Medium
|
Unassigned | ||
Bug Description
This is a more general version of bug 1876323: `cloud-init analyze` relies on the log format that upstream ships in order to detect log lines. This means that if logging configuration by users or downstream packagers diverges (as is the case on Amazon Linux 2, for example), then the `analyze` commands will not produce any useful output (or a useful error message).
(Ubuntu uses this log format, so this bug does not present on Ubuntu.)
| Changed in cloud-init: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| James Falcon (falcojr) wrote | #1 |
| Changed in cloud-init: | |
| status: | Triaged → Expired |
To post a comment you must log in.
Tracked in Github Issues as https:/