Accidental centralized floating IP removal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Oleg Bondarev |
Bug Description
release: Pike.
When a DVR router with centralized floating IPs is rescheduled from down l3 agent to another,
following traces are seen on the destination agent:
2019-02-21 14:55:59,150.150 24730 ERROR neutron.
: ProcessExecutio
2019-02-21 14:55:59,150.150 24730 ERROR neutron.
2019-02-21 14:55:59,150.150 24730 ERROR neutron.
2019-02-21 14:55:59,150.150 24730 ERROR neutron.
2019-02-21 14:55:59,150.150 24730 ERROR neutron.
2019-02-21 14:55:59,150.150 24730 ERROR neutron.
2019-02-21 14:55:59,150.150 24730 ERROR neutron.
2019-02-21 14:55:59,150.150 24730 ERROR neutron.
2019-02-21 14:55:59,150.150 24730 ERROR neutron.
Earlier in logs following is seen:
2019-02-22 07:52:14,894.894 9528 DEBUG neutron.
2019-02-22 07:52:14,922.922 9528 DEBUG neutron.
So centralized floating ip is deleted from gw device for some reason.
Changed in neutron: | |
importance: | Undecided → Medium |
summary: |
- Failed gARP for floating IP in l3 agent logs + Accidental centralized floating IP removal |
Fix proposed to branch: master /review. openstack. org/638648
Review: https:/