RELEASE_UPRADER_NO_APPORT seems to have no effect

Bug #1399836 reported by Brian Murray
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Fix Released
Medium
Brian Murray
Vivid
Fix Released
Medium
Brian Murray

Bug Description

I was trying to test the alternate paths in run_apport of DistUpgradeApport.py and was setting RELEASE_UPRADER_NO_APPORT=1 but this seemed to have no effect. I tested this upgrading from utopic to vivid and from trusty to utopic.

I examined os.environ right before the failure I'd created (a divide by 0 error in DistUpgradeController.py) and that key existed, so it seems like DistUpgradeApport or the call to it is unsetting that variable somehow.

Tags: trusty utopic
tags: added: trusty utopic
Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Brian Murray (brian-murray) wrote :

Duh, it's because only run_apport checks for that environmental variable and apport_crash() and apport_pkgfailure() don't.

Changed in ubuntu-release-upgrader (Ubuntu Vivid):
status: New → In Progress
assignee: nobody → Brian Murray (brian-murray)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-release-upgrader - 1:15.04.11

---------------
ubuntu-release-upgrader (1:15.04.11) vivid; urgency=medium

  * DistUpgrade/DistUpgradeApport.py: check to see if
    RELEASE_UPRADER_NO_APPORT is set when running apport_crash or
    apport_pkgfailure. (LP: #1399836)
 -- Brian Murray <email address hidden> Mon, 09 Mar 2015 14:35:00 -0700

Changed in ubuntu-release-upgrader (Ubuntu Vivid):
status: In Progress → 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.