Attach journal to checkbox

Bug #1872040 reported by Kristin Chuang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox Provider - Base
Expired
Wishlist
Unassigned

Bug Description

Recently we've received a few requests to have journals included in checkbox as attachments to easily compare the current logs with those of previous images and/or checkbox runs.

Ideally this would be either (1) journal outputs saved as a file that we can easily retrieve inside submission.tar.xz, or (2) having it listed in a job's i/o output, or (3) having it somewhere inside the device's c3 submission page.

Revision history for this message
Kristin Chuang (kristinchuang) wrote :

snippets of related discussion

<spineau> snap set core service.rsyslog.disable=false
<robertliu> spineau, on uc18, the option was removed. there is no rsyslogd in core18.
<spineau> ah
<robertliu> you can just 'mkdir /var/log/journal && reboot'
...
<robertliu> maybe restart journald also apply the setting.
...
<robertliu> spineau, btw, journalctl can show a time range of logs. it's not necessary to include all logs.
<spineau> robertliu: we could record the session start to use it later as a marker, I'm already doing that for connections tests where I want to extract logs for NM/MM only for the time window of the corresponding test, e.g:
<spineau> https://git.launchpad.net/plainbox-provider-checkbox/tree/units/wwan/jobs.pxu#n40
<spineau> setting an arbitrary value won't work for sure even if the average is ~2h for lab runs
<robertliu> spineau, cool

Changed in plainbox-provider-checkbox:
importance: Undecided → Wishlist
Revision history for this message
Pierre Equoy (pieq) wrote :

Recently faced a similar request from SWE/WHE for lp:1902668.

While investigating this issue (a systemd service fails to start, leading to a test case failure in Checkbox), we wanted to check if it was a regression of some sort.

For now, there might be several culprits:

1. The new image has a regression (missing driver) that leads to this error
2. The new image has some new configuration that lead this error (e.g. service should not be there at all, but is there and system tries to start it)
3. The failing Checkbox test case has been recently modified to include items that were not taken into account in the past

I wanted to compare the kernel logs or the list ofsystemd services, but none of these are available in the submission archive. Note that, for that specific case, only consistency matters (i.e. *when* the log gathering is done – at the beginning of Checkbox run for instance).

Revision history for this message
Maksim Beliaev (beliaev-maksim) wrote :

Bug was migrated to GitHub: https://github.com/canonical/checkbox/issues/155.
Bug is no more monitored here.

Changed in plainbox-provider-checkbox:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.