cronscripts using production/launchpad-lazr.conf config file with REPORTIFSEEN prefix

Bug #705657 reported by Diogo Matsubara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Diogo Matsubara

Bug Description

As seen in the oopses below some cronscripts are using production/launchpad-lazr.conf config file and generating oops reports. There's a comment in the config file saying if those are used we need to figure out and fix.

OOPS-1845REPORTIFSEEN5319 script_name: process-mail
OOPS-1845REPORTIFSEEN5340 script_name: distributionmirror-prober
OOPS-1860REPORTIFSEEN10002 script_name: hwdbsubmissions
OOPS-1860REPORTIFSEEN155 script_name: checkwatches
OOPS-1860REPORTIFSEEN1363 script_name: pofile-stats

Each one of those scripts run in a different process but use the same config file. This can cause duplicate OOPS prefix allocation.

Related branches

description: updated
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Diogo Matsubara (matsubara)
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.03
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
William Grant (wgrant) wrote :

This is untestable but cannot be deployed until the config changes land.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

I added to the Unusual Rollout Requirements section on LaunchpadProductionStatus a note explaining that the config files need to be rolled out first before rolling out r12355.

tags: added: qa-untestable
removed: qa-needstesting
Changed in launchpad:
status: Fix Committed → Fix Released
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.