yahoo-eng-team team mailing list archive

[James Falcon <1843602@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3447

** Bug watch added: github.com/canonical/cloud-init/issues #3447
   https://github.com/canonical/cloud-init/issues/3447

** 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/1843602

Title:
  cloud-init collect logs needs to defer to distro for debug data

Status in cloud-init:
  Expired

Bug description:
  While triaging a bug in sles'based distro using cloud-init, the
  collect-logs output had a few issues:

  1) the user did not have systemd journal privs

  Unexpected error while running command.
  Command: ['journalctl', '--boot=0', '-o', 'short-precise']
  Exit code: 1
  Reason: -
  Stdout: 
  Stderr: Hint: You are currently not seeing messages from other users and the system.
                Users in the 'systemd-journal' group can see all messages. Pass -q to
                turn off this notice.
          No journal files were opened due to insufficient permissions.

  2) we tried to collect dpkg-version on a non debian distro

  Unexpected error while running command.
  Command: ['dpkg-query', '--show', '-f=${Version}\n', 'cloud-init']
  Exit code: -
  Reason: [Errno 2] No such file or directory
  Stdout: -
  Stderr: -

  3) version file is empty

  4) dmesg as non-root user fails

  Unexpected error while running command.
  Command: ['dmesg']
  Exit code: 1
  Reason: -
  Stdout: 
  Stderr: dmesg: read kernel buffer failed: Operation not permitted

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1843602/+subscriptions