xenserver driver raises NotImplementedError for reset_network

Bug #1309580 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

Looks like this is by design, but the xenapi vmops reset_network method should raise a more specific error than NotImplementedError when the instance doesn't have an agent enabled here:

http://git.openstack.org/cgit/openstack/nova/tree/nova/virt/xenapi/vmops.py#n1725

This failed all over in XenServer CI with what I think is an unrelated patch:

http://dd6b71949550285df7dc-dda4e480e005aaa13ec303551d2d8155.r49.cf1.rackcdn.com/11/80511/2/screen-n-cpu.txt.gz

Tags: xenserver
Changed in nova:
importance: Undecided → Medium
Andrew Laski (alaski)
Changed in nova:
status: New → Confirmed
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
importance: Medium → Undecided
status: Confirmed → Expired
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.