dmesg-attachment job is empty
Bug #1712103 reported by
Jeff Lane
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Provider - Base |
Fix Released
|
High
|
Jeff Lane |
Bug Description
See here:
https:/
While investigating issues with this system I noticed that the dmesg attachment is completley blank, making it useless.
We need to fix this job so that it actually attaches the output of dmesg.
Related branches
~bladernr/plainbox-provider-checkbox:1712103-fix-dmesg-attachment
- Paul Larson: Approve
-
Diff: 24 lines (+9/-3)1 file modifiedjobs/info.txt.in (+9/-3)
Changed in plainbox-provider-checkbox: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Jeff Lane (bladernr) |
tags: | added: hwcert-server |
Changed in plainbox-provider-checkbox: | |
status: | Confirmed → In Progress |
Changed in plainbox-provider-checkbox: | |
milestone: | none → future |
Changed in plainbox-provider-checkbox: | |
status: | In Progress → Fix Committed |
milestone: | future → 0.40.0 |
Changed in plainbox-provider-checkbox: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Appears to be because there is no /var/log/dmesg:
ubuntu@above-ox:~$ ls /var/log/ output. log kern.log.1 syslog.2.gz
alternatives.log cloud-init-
apt dist-upgrade lastlog syslog.3.gz
auth.log dpkg.log lxd syslog.4.gz
auth.log.1 fontconfig.log ntpstats sysstat
btmp fsck syslog unattended-upgrades
cloud-init.log kern.log syslog.1 wtmp
(on MAAS deployments at least).