Oops pages show wrong time window in JournalErrors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apport |
Fix Released
|
Medium
|
Benjamin Drung | ||
apport (Ubuntu) |
Fix Released
|
Medium
|
Benjamin Drung | ||
Focal |
Fix Released
|
Medium
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
Unassigned |
Bug Description
[Impact]
Oops pages show wrong time window in JournalErrors. For example, I just experienced a crash at:
Feb 28 17:31:12
And the JournalErrors entries are:
Feb 28 17:31:30 - Feb 28 17:31:41
So don't relate to the crash.
[Test Plan]
1. Find a recent crash report from a relevant Ubuntu release on https:/
2. Now you're on a page starting with https:/
3. Verify the Date field falls within the time range of the JournalErrors entries.
Step 3 might fail in the case of there being no system log entries from around the time of the crash. That does not necessarily mean the test plan has failed. Go to step 1 and pick a different crash.
Prior to the fix you would almost never find oops pages that would pass the test. After the fix you should find many/most oops pages do pass the test.
[Where problems could occur]
Worst case - in any part of the bug reporting/
[Other Info]
Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https:/
* jammy SRU: https:/
* focal SRU: https:/
Related branches
- Benjamin Drung: Approve
-
Diff: 33 lines (+13/-2)1 file modifieddata/general-hooks/generic.py (+13/-2)
Changed in apport (Ubuntu): | |
importance: | Undecided → Low |
Changed in errors: | |
status: | New → Invalid |
Changed in apport (Ubuntu): | |
status: | New → Triaged |
tags: | added: fr-2321 |
tags: |
added: jammy removed: fr-2321 rls-jj-incoming |
tags: | added: fr-2321 |
Changed in apport (Ubuntu Jammy): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in apport: | |
assignee: | nobody → Brian Murray (brian-murray) |
status: | New → In Progress |
Changed in apport: | |
status: | In Progress → Fix Committed |
milestone: | none → 2.21.0 |
Changed in apport: | |
status: | Fix Committed → Fix Released |
importance: | Undecided → Medium |
Changed in apport: | |
assignee: | Brian Murray (brian-murray) → Benjamin Drung (bdrung) |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: foundations-todo |
description: | updated |
Changed in apport (Ubuntu Jammy): | |
status: | Incomplete → Confirmed |
Changed in apport (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | removed: foundations-todo |
This could be due to the complete data collection happening after the crash, not immediately at the time of the crash. One thing apport could do is look at the time stamp of the crash and gather the journal slightly before that.