`cloud-init analyze` fails to produce useful output on Amazon Linux 2 due to log format configuration
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Fix Released
|
High
|
Dan Watkins | ||
Bug Description
When running `cloud-init analyze show` against a log file from an Amazon Linux 2 instance (e.g. https:/
$ cloud-init analyze show -i ~/Downloads/
-- Boot Record 01 --
The total time elapsed since completing an event is printed after the "@" character.
The time the event takes is printed after the "+" character.
Total Time: 0.00000 seconds
1 boot records analyzed
This is because the log configuration on Amazon Linux 2 (https:/
format=
which differs from the upstream definition:
format=
This is a problem, because the `cloud-init analyze` commands depend on the " - " part of the line's presence as a separator (see https:/
(As an aside, this is the only non-whitespace difference between the two configuration files.)
| Ryan Harper (raharper) wrote | #1 |
| Brian O'Rourke (bpo-t) wrote | #2 |
| Dan Watkins (oddbloke) wrote | #3 |
| Dan Watkins (oddbloke) wrote | #4 |
| Changed in cloud-init: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Dan Watkins (daniel-thewatkins) |
| Dan Watkins (oddbloke) wrote | #5 |
| Changed in cloud-init: | |
| status: | In Progress → Fix Committed |
| James Falcon (falcojr) wrote Fixed in cloud-init version 20.3. | #6 |
| Changed in cloud-init: | |
| status: | Fix Committed → Fix Released |
| James Falcon (falcojr) wrote | #7 |
Do we know if Amazon Linux 2 has journald ? we could (prefer) or (fallback) to journalctl output.