TestNetworkBasicOps often times out running against tripleo

Bug #1605654 reported by wes hayutin
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Critical
Jakub Libosvar

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

Tags: alert ci
Revision history for this message
Emilien Macchi (emilienm) wrote :

setting to invalid for some reasons:

- you're using RDO CI links to mention a potential TripleO CI issue (both CI are different).
- you're passing logs without much context, it's not helpful to figure out what could be wrong.

I'll close it. Feel free to re-open it with more technical context. Thanks.

Changed in tripleo:
status: New → Invalid
Revision history for this message
Arx Cruz (arxcruz) wrote :
Changed in tripleo:
status: Invalid → New
Changed in tripleo:
status: New → Triaged
milestone: none → pike-3
importance: Undecided → Medium
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Revision history for this message
wes hayutin (weshayutin) wrote :
wes hayutin (weshayutin)
Changed in tripleo:
importance: Medium → Critical
assignee: nobody → Jakub Libosvar (libosvar)
milestone: queens-1 → pike-rc1
wes hayutin (weshayutin)
tags: added: alert ci
affects: tripleo → neutron
Changed in neutron:
milestone: pike-rc1 → none
milestone: none → pike-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/491890

Changed in neutron:
status: Triaged → In Progress
Revision history for this message
YaZug (jon-schlueter) wrote :

test_port_security_macspoofing_port[compute,id-7c0bb1a2-d053-49a4-98f9-ca1a1d849f63,network,slow] - this is the tempest test that is failing

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/491890
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=03c100b9596f2c46c090571286abe750174494b4
Submitter: Jenkins
Branch: master

commit 03c100b9596f2c46c090571286abe750174494b4
Author: Jakub Libosvar <email address hidden>
Date: Tue Aug 8 19:10:41 2017 +0000

    Fill device_info with port_security_enabled data

    Firewall drivers check if port security is enabled. After ovo is sent
    over the wire, the port_security_enabled is part of 'security' field.
    The patch translates the RPC call from agent to server so the payload
    containing port_security_enabled is at the same place.

    We may consider implementing change of OVO field to contain boolean
    directly.

    Change-Id: I647343e84b41da63d7ffcc5a87f3dfa2036adc56
    Closes-bug: #1605654

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 11.0.0.0rc1

This issue was fixed in the openstack/neutron 11.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.