Euca tests failure, cannot ping server with floating ip

Bug #1101142 reported by Julie Pichon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
High
Unassigned
devstack
Invalid
Undecided
Unassigned

Bug Description

Apologies if this isn't the right component to file against.

The Jenkins job gate-tempest-devstack-vm failed during the euca tests (see https://review.openstack.org/#/c/18298/4). It looks like it timed out trying to ping an instance with a Floating IP:

09:59:05 + euca-associate-address -i i-00000001 172.24.4.225
09:59:07 ADDRESS 172.24.4.225 i-00000001
09:59:07 + euca-authorize -P icmp -s 0.0.0.0/0 -t -1:-1 euca_secgroup
09:59:08 GROUP euca_secgroup
09:59:08 PERMISSION euca_secgroup ALLOWS icmp -1 -1 FROM CIDR 0.0.0.0/0
09:59:08 + timeout 60 sh -c 'while ! ping -c1 -w1 172.24.4.225; do sleep 1; done'
09:59:08 ping: sendmsg: Operation not permitted
09:59:09 PING 172.24.4.225 (172.24.4.225) 56(84) bytes of data.
09:59:09
09:59:09 --- 172.24.4.225 ping statistics ---
09:59:09 1 packets transmitted, 0 received, 100% packet loss, time 0ms
09:59:09
09:59:11 PING 172.24.4.225 (172.24.4.225) 56(84) bytes of data.
09:59:11
09:59:11 --- 172.24.4.225 ping statistics ---
09:59:11 2 packets transmitted, 0 received, 100% packet loss, time 999ms
09:59:11
09:59:13 PING 172.24.4.225 (172.24.4.225) 56(84) bytes of data.
09:59:13 From 172.24.4.225 icmp_seq=1 Destination Host Unreachable
09:59:13
09:59:13 --- 172.24.4.225 ping statistics ---
09:59:13 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
09:59:13
[...]
10:00:08 + echo 'Couldn'\''t ping server with floating ip'
10:00:08 Couldn't ping server with floating ip
10:00:08 + exit 1

Julie Pichon (jpichon)
description: updated
James E. Blair (corvus)
no longer affects: openstack-ci
Revision history for this message
Nachi Ueno (nati-ueno) wrote :

hmmm, Am I misunderstanding something???

most of recheck report is invalid..
https://docs.google.com/spreadsheet/ccc?key=0Ap9P99ymj9wLdEpSRmVQM2tYcXJ0WjRWQkNaMW13WGc#gid=0

Revision history for this message
Vish Ishaya (vishvananda) wrote :

This has been happening infrequently on the gating tests. It would be nice to track this down to a root cause.

Changed in nova:
status: New → Triaged
importance: Undecided → High
milestone: none → grizzly-rc1
Revision history for this message
Vish Ishaya (vishvananda) wrote :
Revision history for this message
Russell Bryant (russellb) wrote :

I'm going to move this to grizzly-rc-potential since it seems like something that should be on the "nice to have" list and shouldn't block grizzly-rc1.

tags: added: grizzly-rc-potential
Changed in nova:
milestone: grizzly-rc1 → none
Thierry Carrez (ttx)
Changed in nova:
status: Triaged → Confirmed
tags: removed: grizzly-rc-potential
Revision history for this message
Jian Wen (wenjianhn) wrote :

Due to many vms are created in the host machine, performance of
 the devstack vm maybe poor.
I guess sometimes 60 seconds are not long enough to create the
icmp security group rule and the DNAT rule.

09:59:08 + timeout 60 sh -c 'while ! ping -c1 -w1 172.24.4.225; do sleep 1; done'

James E. Blair (corvus)
no longer affects: openstack-ci
Revision history for this message
Justin Shepherd (jshepher) wrote :

Marking this issue as invalid, as it has not been updated in almost a year. If you believe this to be in error, please update this issue.

Changed in nova:
status: Confirmed → Invalid
Changed in devstack:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers