yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <1612281@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Critical
         Status: New

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: gate-failure linuxbridge

** Also affects: nova
   Importance: Undecided
       Status: New

-- 
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:
  New
Status in OpenStack Compute (nova):
  New

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