staging services share OOPS prefix
Bug #788518 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
Systems that do not share an OOPS output directory should not share an OOPS prefix.
Currently, staging scripts and the staging appserver use the same OOPS prefix. This means conflicts happen. At the moment, every OOPS emitted by the staging appserver has already been taken by a misbehaving script.
The fix is to create a staging-scripts or staging-appserver config that inherits from the main staging config, changing the OOPS prefix.
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| tags: | added: critical-analysis |
Revision history for this message
| Martin Pool (mbp) wrote Re: [Bug 788518] Re: staging services share OOPS prefix | #2 |
Revision history for this message
| Robert Collins (lifeless) wrote | #3 |
Revision history for this message
| Steve Kowalik (stevenk) wrote | #4 |
| Changed in launchpad: | |
| importance: | Critical → High |
Revision history for this message
| William Grant (wgrant) wrote | #5 |
| Changed in launchpad: | |
| status: | Triaged → Won't Fix |
Revision history for this message
| Robert Collins (lifeless) wrote | #6 |
To post a comment you must log in.
In addition to making QA difficult, it also means our reports are lying because many OOPS reports will not be counted.