Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3676
** Bug watch added: github.com/canonical/cloud-init/issues #3676 https://github.com/canonical/cloud-init/issues/3676 ** 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/1876794 Title: `cloud-init analyze` depends on the upstream-shipped log format to function Status in cloud-init: Expired 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.) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1876794/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
