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

Billy Olsen billy.olsen at canonical.com
Fri Jul 1 23:20:06 UTC 2016


** Description changed:

- ubuntu at devstack-master:/opt/stack/nova$ grep -r exception.ProcessExecutionError *  
+ ubuntu at 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.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.
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 Committed

Bug description:
  ubuntu at 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



More information about the Ubuntu-openstack-bugs mailing list