ovs tunnel state not syncing (failure pinging overcloud instance)
Bug #1292105 reported by
Ben Nemec
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Critical
|
Unassigned | ||
Icehouse |
Fix Released
|
Undecided
|
Unassigned | ||
tripleo |
Fix Released
|
Critical
|
Robert Collins |
Bug Description
I saw this in a recent CI overcloud run: http://
2014-03-12 20:01:46.509 | Timing out after 300 seconds:
2014-03-12 20:01:46.509 | COMMAND=ping -c 1 192.0.2.46
2014-03-12 20:01:46.509 | OUTPUT=PING 192.0.2.46 (192.0.2.46) 56(84) bytes of data.
2014-03-12 20:01:46.509 | From 192.0.2.46 icmp_seq=1 Destination Host Unreachable
It appears as though everything ran fine up until it tried to ping the booted overcloud instance. I'm fairly certain it has nothing to do with my change, so I wanted to open a bug to track it in case anyone else runs into a similar problem.
Changed in tripleo: | |
assignee: | nobody → Robert Collins (lifeless) |
status: | Triaged → In Progress |
summary: |
- CI failed pinging overcloud instance + ovs tunnel state not syncing (failure pinging overcloud instance) |
Changed in neutron: | |
importance: | Undecided → Critical |
Changed in tripleo: | |
status: | In Progress → Fix Committed |
Changed in tripleo: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | none → juno-2 |
Changed in neutron: | |
assignee: | Kevin Benton (kevinbenton) → Baohua Yang (yangbaohua) |
assignee: | Baohua Yang (yangbaohua) → nobody |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
This appears to be happening to all Fedora 20 jobs as of today.