Ping occasionally fails in pingtest in OVB ha jobs

Bug #1690109 reported by Sagi (Sergey) Shnaidman on 2017-05-11
This bug report is a duplicate of:  Bug #1680195: Random ovb-ha ping test failures. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Critical
Unassigned
Tags: ci Edit Tag help
Ben Nemec (bnemec) wrote :

This has been open and marked critical for a month: https://bugs.launchpad.net/tripleo/+bug/1680195 Nobody has looked into it to my knowledge.

This bug was escalated in Thursday 11 May. Should it be closed as duplicate or worth to leave it as is?

Amit Ugol (amit-ugol) wrote :

Sergey, duplicate of which bug?

@Amit, see Ben's comment above: https://bugs.launchpad.net/tripleo/+bug/1680195

Download full text (3.9 KiB)

I have this issue reproduced on CI dev system right now, ping me for getting access to the system to debug (@sshnaidm on #tripleo)

The failed vm networks are located in non-master HA controller node, maybe it was switch during the creation, or before it.

So far as I see, the router has its gateway down:

(overcloud) [jenkins@undercloud tripleo-ci]$ openstack port list --router 71ce23d9-2c47-4286-ad56-f2e5265ee30f
+--------------------------------------+----------------------------------------------+-------------------+------------------------------------------------+--------+
| ID | Name | MAC Address | Fixed IP Addresses | Status |
+--------------------------------------+----------------------------------------------+-------------------+------------------------------------------------+--------+
| 5597935b-ce81-4002-ba83-1fdd404fab45 | HA port tenant | fa:16:3e:8e:24:c3 | ip_address='169.254.192.7', subnet_id | ACTIVE |
| | 124a61db46a24ebbadda7caa47de29a1 | | ='3af6b6be-972a-4fe5-bdc8-717a24a623a4' | |
| 9e9131b5-31b4-44f3-92e0-7b13de9e7f8d | | fa:16:3e:07:3e:15 | ip_address='192.168.2.1', subnet_id='086fe45e- | ACTIVE |
| | | | 4c20-45ae-bc16-ad7bb370951f' | |
| b72a3c4b-6545-4b34-856d-904b4bd66694 | HA port tenant | fa:16:3e:b3:f3:db | ip_address='169.254.192.3', subnet_id | ACTIVE |
| | 124a61db46a24ebbadda7caa47de29a1 | | ='3af6b6be-972a-4fe5-bdc8-717a24a623a4' | |
| d37fdab9-0490-47a4-a020-a3017c690c2a | HA port tenant | fa:16:3e:22:ca:96 | ip_address='169.254.192.4', subnet_id | ACTIVE |
| | 124a61db46a24ebbadda7caa47de29a1 | | ='3af6b6be-972a-4fe5-bdc8-717a24a623a4' | |
| e6688ece-5936-42bf-affa-028b182f9bf4 | | fa:16:3e:c1:a4:15 | ip_address='10.0.0.101', subnet_id='25b22b42 | DOWN |
| | | | -4b8b-44bc-a0fc-cc512a189d4d' | |
+--------------------------------------+----------------------------------------------+-------------------+------------------------------------------------+--------+

Errors in neutron server log about the gateway port creation (e6688ece-5936-42bf-affa-028b182f9bf4):

/var/log/neutron/server.log:2017-05-14 12:32:49.159 127313 INFO neutron.plugins.ml2.plugin [req-15df71a6-ee71-4fe3-90ea-be5b98790b1c - - - - -] Attempt 2 to bind port e6688ece-5936-42bf-affa-028b182f9bf4
/var/log/neutron/server.log:2017-05-14 12:32:53.521 127311 WARNING neutron.plugins.ml2.rpc [req-2956d1a9-251b-4180-8b83-293380d01ce9 - - - - -] Device...

Read more...

tags: removed: alert promotion-blocker
tags: added: alert promotion-blocker
tags: removed: alert promotion-blocker
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers