yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1605654] Re: TestNetworkBasicOps often times out running against tripleo

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Jakub Libosvar <libosvar@xxxxxxxxxx>
Date: Tue, 08 Aug 2017 19:03:19 -0000
Reply-to: Bug 1605654 <1605654@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Project changed: tripleo => neutron

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

Title:
  TestNetworkBasicOps often times out running against tripleo

Status in neutron:
  Triaged

Bug description:
  https://ci.centos.org/artifacts/rdo/jenkins-tripleo-quickstart-
  promote-mitaka-delorean-
  minimal-633/undercloud/home/stack/tempest/tempest.xml.gz

  we'll be moving this into the skip list until it is solved.

  2016-07-22 05:57:42,401 31892 INFO     [tempest.scenario.manager] FloatingIP: {u'router_id': u'aaa52d2b-df09-4bce-8525-68c48eceecff', u'status': u'ACTIVE', u'description': u'', u'dns_name': u'', u'dns_domain': u'', u'floating_network_id': u'c3a17c42-9729-4ef0-96fb-ae91aba741cf', u'fixed_ip_address': u'192.168.0.3', u'floating_ip_address': u'192.0.2.117', u'tenant_id': u'18c53419e9f544bea79412e7d33c7a65', u'port_id': u'9eb7e32e-24d3-40ec-bc59-5e51521ee477', u'id': u'17a0ce8d-46fe-4f87-8857-58ab62ad2a33'} is at status: ACTIVE
  2016-07-22 05:57:42,402 31892 DEBUG    [tempest.scenario.manager] checking network connections to IP 192.0.2.117 with user: cirros
  2016-07-22 05:57:42,403 31892 DEBUG    [tempest.scenario.manager] TestNetworkBasicOps:test_network_basic_ops begins to ping 192.0.2.117 in 120 sec and the expected result is reachable
  2016-07-22 05:59:44,092 31892 DEBUG    [tempest.scenario.manager] TestNetworkBasicOps:test_network_basic_ops finishes ping 192.0.2.117 in 120 sec and the ping result is unexpected
  2016-07-22 05:59:44,094 31892 ERROR    [tempest.scenario.manager] Public network connectivity check failed
  2016-07-22 05:59:44.094 31892 ERROR tempest.scenario.manager Traceback (most recent call last):
  2016-07-22 05:59:44.094 31892 ERROR tempest.scenario.manager   File "tempest/scenario/manager.py", line 602, in check_public_network_connectivity
  2016-07-22 05:59:44.094 31892 ERROR tempest.scenario.manager     should_connect=should_connect)
  2016-07-22 05:59:44.094 31892 ERROR tempest.scenario.manager   File "tempest/scenario/manager.py", line 586, in check_vm_connectivity
  2016-07-22 05:59:44.094 31892 ERROR tempest.scenario.manager     msg=msg)
  2016-07-22 05:59:44.094 31892 ERROR tempest.scenario.manager   File "/home/stack/tempest/.venv/lib/python2.7/site-packages/unittest2/case.py", line 702, in assertTrue
  2016-07-22 05:59:44.094 31892 ERROR tempest.scenario.manager     raise self.failureException(msg)
  2016-07-22 05:59:44.094 31892 ERROR tempest.scenario.manager AssertionError: False is not true : Timed out waiting for 192.0.2.117 to become reachable
  2016-07-22 05:59:44.094 31892 ERROR tempest.scenario.manager

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