Submitter: Jenkins
Branch:    master

commit 676babbd9acb08b389848092236cad182306b373
Author: Jianghua Wang <>
Date:   Tue Sep 6 11:14:05 2016 +0800

    XenAPI: resolve the fetch_bandwidth failure
    When introducing interim bridge for XenAPI, it introduced a interface
    which is connected to the interim bridge and it has the name as
    vifxxxxxxxx-xx. In the xenapi plugin of bandwidth, it uses
    the pattern of "^vif*" to filter out VM's interfaces. Due to the
    existing of vifxxxxxxxx-xx, it will get exception when parsing the
    interface's name basing on "vif<dom#>.<dev>".
    So let's give more restrict pattern to filter VM's vifs e.g. change from
    "^vif*" to "^vif<dom#>.<dev#>". May consider to use another interface
    name for the interface on interim bridge; but need cover both name
    patterns when delete interfaces to avoid upgrade issues which may make
    things complicated.
    Change-Id: I36b96bbe2bb764f3d60cbeb43aa3dbd9a0a43f61
    Closes-Bug: #1597551

** Changed in: nova
       Status: In Progress => Fix Released

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).

  XenAPI plugin failure with fetch_all_bandwidth

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  XenAPI can't fetch the bandwidth with the following error in log:
  2016-06-29 09:02:27.639 30900 ERROR oslo_service.periodic_task Failure: 
['XENAPI_PLUGIN_FAILURE', 'fetch_all_bandwidth', 'ValueError', 'need more than 
1 value to unpack']

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to