yahoo-eng-team team mailing list archive

[OpenStack Infra <1612281@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/354143
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=26399c700577f7a98213ec908dd2f478270f494e
Submitter: Jenkins
Branch:    master

commit 26399c700577f7a98213ec908dd2f478270f494e
Author: Daniel P. Berrange <berrange@xxxxxxxxxx>
Date:   Thu Aug 11 16:11:01 2016 +0100

    network: fix handling of linux-bridge in os-vif conversion
    
    The nova.network.model.Network class uses names
    'should_create_{bridge,vlan}' not 'should_provide_{bridge,vlan}'
    
    The bridge_interface attribute should always be set, even if
    to None, since None is a valid value.
    
    The vlan attribute is compulsory if should_create_vlan is
    set.
    
    Closes-bug: 1612281
    Change-Id: I245f560156d596be14ef9181bfb881be9680c166


** Changed in: nova
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1612281

Title:
  Neutron Linuxbridge jobs failing with 'operation failed: failed to
  read XML'

Status in neutron:
  Invalid
Status in OpenStack Compute (nova):
  Fix Released
Status in os-vif:
  Invalid

Bug description:
  Example: http://logs.openstack.org/64/353664/2/check/gate-tempest-
  dsvm-neutron-
  linuxbridge/591295c/console.html#_2016-08-11_12_57_42_191711

  2016-08-11 12:57:42.191740 |     Traceback (most recent call last):
  2016-08-11 12:57:42.191760 |       File "tempest/test.py", line 106, in wrapper
  2016-08-11 12:57:42.191779 |         return f(self, *func_args, **func_kwargs)
  2016-08-11 12:57:42.191814 |       File "tempest/scenario/test_server_advanced_ops.py", line 90, in test_server_sequence_suspend_resume
  2016-08-11 12:57:42.191825 |         'ACTIVE')
  2016-08-11 12:57:42.191851 |       File "tempest/common/waiters.py", line 75, in wait_for_server_status
  2016-08-11 12:57:42.191865 |         server_id=server_id)
  2016-08-11 12:57:42.191905 |     tempest.exceptions.BuildErrorException: Server 15dcd67e-dd8a-4805-b14b-798c6d2a6e87 failed to build and is in ERROR status
  2016-08-11 12:57:42.191942 |     Details: {u'message': u'operation failed: failed to read XML', u'created': u'2016-08-11T12:52:28Z', u'code': 500}

  In nova-cpu logs, we see the same error:
  http://logs.openstack.org/64/353664/2/check/gate-tempest-dsvm-neutron-
  linuxbridge/591295c/logs/screen-n-cpu.txt.gz?level=TRACE#_2016-08-11_12_55_21_025

  Note that the log contains other suspicious errors, like:

  - privsep unexpected errors: http://logs.openstack.org/64/353664/2/check/gate-tempest-dsvm-neutron-linuxbridge/591295c/logs/screen-n-cpu.txt.gz?level=TRACE#_2016-08-11_12_25_47_284
  - libvirt failing to locate brq: http://logs.openstack.org/64/353664/2/check/gate-tempest-dsvm-neutron-linuxbridge/591295c/logs/screen-n-cpu.txt.gz?level=TRACE#_2016-08-11_12_26_13_346

  Agent logs seems more or less clean.

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