yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #92179
[Bug 1876795] Re: `cloud-init analyze` should emit a useful error message if it finds no log lines to process
Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3677
** Bug watch added: github.com/canonical/cloud-init/issues #3677
https://github.com/canonical/cloud-init/issues/3677
** Changed in: cloud-init
Status: Triaged => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1876795
Title:
`cloud-init analyze` should emit a useful error message if it finds no
log lines to process
Status in cloud-init:
Expired
Bug description:
When run on the log output from Amazon Linux 2 (see bug 1876323),
`analyze` fails to find any log lines to process. Currently, it
treats this as a normal situation and emits:
$ cloud-init analyze show -i ~/Downloads/uhJNysgm.txt
-- 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
It would be better if it emitted a clear error message that it didn't
find any log lines.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1876795/+subscriptions
References