tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_in_tenant_traffic Timeout

Bug #1310852 reported by YAMAMOTO Takashi
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Expired
Medium
Unassigned
Tags: gate-failure
Revision history for this message
Matt Riedemann (mriedem) wrote :
Revision history for this message
Matt Riedemann (mriedem) wrote :
Revision history for this message
Matt Riedemann (mriedem) wrote :

This might be a variant of bug 1253896.

Revision history for this message
Matt Riedemann (mriedem) wrote :

Opened bug 1323658 for the SSH EOFError.

Revision history for this message
Kyle Mestery (mestery) wrote :
Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

Regarding the log in the first Matt's comment, I've found the following discrepancy:

The server to which tempest is trying to check the connectivity supposed to have 10.100.0.20 as fixed ip and 172.24.4.61 as floating.
Server output from nova doesn't show that server with fixed ip 10.100.0.20 has floating ip:
http://logs.openstack.org/24/88224/2/check/check-tempest-dsvm-neutron-2/dfb1367/console.html.gz#_2014-04-21_17_12_36_097

In the end of the log file another output from nova could be seen: http://logs.openstack.org/24/88224/2/check/check-tempest-dsvm-neutron-2/dfb1367/console.html.gz#_2014-04-21_17_12_36_564

Here you can see that VM has expected floating ip 172.24.4.61 but fixed ip is different: 10.100.0.18
If you search by 172.24.4.61 you'll see that it was only associated with 10.100.0.18 ever.
I'm not sure I'm interpreting logs correctly, at least it confuses me that logs related to the failing tests show nova output for different servers.

Anyway my conclusion is that there is a discrepancy between fixed/floating ips of the instance and test's expectation.
I was not able to find out the root cause yet.

Changed in neutron:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

Marking as incomplete as this have not been hit for quite a while

tags: added: gate-failure
Changed in neutron:
importance: High → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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