python-oops-tools

New oops-prefixes should be automatically known by oops-tools by reading the LAZR_CONFIG file

Bug #667375 reported by Diogo Matsubara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-oops-tools
Fix Released
High
Unassigned

Bug Description

When a new prefix is added to lp-production-config, there's a manual step to add the prefix to the correct summary and another one to make the prefix known by oops-tools (through: https://lp-oops.canonical.com/prefixloader)

This should be automated and need no human intervention

Revision history for this message
Robert Collins (lifeless) wrote :

See the other bugs about oops-prefixes; at the epic I will make some time to talk through this and we can sort out the roadmap in this area.

Changed in oops-tools:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Robert Collins (lifeless) wrote :

prefixes are now just added as they are seen in an oops report, no manual intervention. We can nuke the prefix-loader too, if we don't need the auto-association of LPNETA -> lpnet. (which I think we can drop sensibly)

Changed in oops-tools:
status: Triaged → Fix Released
affects: oops-tools → python-oops-tools
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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