← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1308839] Re: ProcessExecutionError exception is not defined in exception.py now

 

This bug was fixed in the package nova - 1:2014.1.5-0ubuntu1.5

---------------
nova (1:2014.1.5-0ubuntu1.5) trusty; urgency=medium

  * Fix live migration usage of the wrong connector (LP: #1475411)
    - d/p/Fix-live-migrations-usage-of-the-wrong-connector-inf.patch
  * Fix wrong used ProcessExecutionError exception (LP: #1308839)
    - d/p/Fix-wrong-used-ProcessExecutionError-exception.patch
  * Clean up iSCSI multipath devices in Post Live Migration (LP: #1357368)
    - d/p/Clean-up-iSCSI-multipath-devices-in-Post-Live-Migrat.patch
  * Detach iSCSI latest path for latest disk (LP: #1374999)
    - d/p/Detach-iSCSI-latest-path-for-latest-disk.patch

 -- Billy Olsen <billy.olsen@xxxxxxxxxxxxx>  Fri, 29 Apr 2016 15:35:01
-0700

** Changed in: nova (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

** Changed in: nova (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1308839

Title:
  ProcessExecutionError exception is not defined in exception.py now

Status in OpenStack Compute (nova):
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Trusty:
  Fix Released

Bug description:
  ubuntu@devstack-master:/opt/stack/nova$ grep -r exception.ProcessExecutionError *
  nova/virt/libvirt/volume.py:        except exception.ProcessExecutionError as exc:

  commit 5e016846708ef62c92dcf607f03c67c36ce5c23f has been fixed all
  other wrong used places, but this one is added after this change.

  [Impact]

  Error doesn't exist, if error encountered then wrong error reported.

  [Test Case]
  grep -r exception.ProcessExecutionError /usr/lib/python2.7/dist-packages/nova/*

  [Regression Potential]
  Minimal. This change is in an error path already. When error path is encountered, the exception doesn't exist and causes a different error to occur but calling code treats both the same way. This ensures the right error is thrown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1308839/+subscriptions


References