set a TTL for OOPS data when it is submitted

Bug #1977779 reported by Brian Murray
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Daisy
Triaged
High
Unassigned

Bug Description

A TTL is set for snap crashes when they are submitted to the Ubuntu Error Tracker. From daisy/submit.py:

    try:
        if problem_type == 'Snap':
            expire = True
        else:
            expire = False
        oopses.insert_dict(_session, oops_id, data, system_token, fields,
                           proposed_pkg=package_from_proposed, ttl=expire)

However, this is not done for regular crash reports. As mentioned in the following mailing list thread:

https://lists.ubuntu.com/archives/ubuntu-devel/2022-May/042057.html

A TTL should also be set for Ubuntu crash reports and the expiration date for that data should be when the release reaches its end of standard support. We'll likely want to pass a value for the TTL to oopses.py, instead of a boolean, and do some maths using the end of standard support data from distro-info-data to determine that value.

Changed in daisy:
importance: Undecided → High
status: New → Triaged
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.