[DVR] Lost snat after ban l3-agent with snat for updated router
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
High
|
Oleg Bondarev |
Bug Description
After banning l3-agent on node with snat for updated router snat was lost
Steps:
1) Create net1, subnet1
2) Create centralized router, set gateway, add interface to net1
3) Boot vm in net1
4) Update router to Distributed:
neutron router-update router1 --admin_state_up False
neutron router-update router1 --distributed True
neutron router-update router1 --admin_state_up True
5) Check that ping 8.8.8.8 is available from vm
6) Ban l3-agent on node with snat
7) Wait some time
Expected result: snat moved on another controller, ping 8.8.8.8 from vm is available
Currenr result: snat was lost, ping 8.8.8.8 isn't available
Find on:
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "8.0"
api: "1.0"
build_number: "478"
build_id: "478"
fuel-nailgun_sha: "ae949905142507
python-
fuel-agent_sha: "481ed135de2cb5
fuel-
astute_sha: "b81577a5b7857c
fuel-library_sha: "420c6fa5f8cb51
fuel-ostf_sha: "ab5fd151fc6c1a
fuel-mirror_sha: "b62f3cce5321fd
fuelmenu_sha: "fac143f4dfa757
shotgun_sha: "63645dea384a37
network-
fuel-upgrade_sha: "616a7490ec7199
fuelmain_sha: "6c6b088a3d52dd
(neutron+vlan+dvr, neutron+
Neutron server logs in attachment
Changed in mos: | |
assignee: | MOS Neutron (mos-neutron) → Oleg Bondarev (obondarev) |
status: | New → Triaged |
tags: |
added: area-neutron removed: neutron |
The same situation repeated for firstly created distributed router. Sometimes reschedulling is too slow, sometimes the same situation as for updated router
Logs in attachment