Mirantis OpenStack

[DVR] Lost snat after very long recovering destroyed node

Bug #1546093 reported by Kristina Berezovskaia on 2016-02-16

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
Mirantis OpenStack	Fix Released	Medium	MOS Maintenance	Mirantis OpenStack 8.0-updates
8.0.x	Won't Fix	Medium	MOS Maintenance	Mirantis OpenStack 8.0-updates
9.x	Fix Released	Medium	Oleg Bondarev	Mirantis OpenStack 9.0

Bug Description

After start previously destroyed node, env was recovering very long and snat for 2 routers was dissapeared

Steps:
1. net-1, subnet-1, net-2, subnet-2, dvr-router with gateway and interfaces to both nets
2. vm1 in net-1, vm2 in net-2
3. net-3, subnet-3, router-3 with gateway and interface to net-3
4. vm3 in net-3
5. default router router04
6. snat for this routers:
router-1 - node-2
router04 and router-2 - node-4
7. Destroy controller node-2
8. After destroying snat for routers:
router-1 - node-5
router04 and router-2 - node-4
9. Start destroyed node-2
Recovering was too long and after some time (when all agents became alive) we can see that router-1 is on node-2 and there are no snat for router04 and router-2

This situation was only once
Logs in attachment

Tags:

Revision history for this message

Kristina Berezovskaia (kkuznetsova) wrote on 2016-02-16:

neutron_dvr_logs.tar Edit (5.0 MiB, application/x-tar)

Revision history for this message

Oleg Bondarev (obondarev) wrote on 2016-02-16:

Upstream bug: https://bugs.launchpad.net/neutron/+bug/1524908
Upstream fix to be backported to 8.0-updates: https://review.openstack.org/#/c/255989/

Changed in mos:
status:	New → Confirmed
assignee:	Oleg Bondarev (obondarev) → MOS Maintenance (mos-maintenance)

Alexander Ignatov (aignatov) on 2016-02-16

tags:

added: release-notes

Revision history for this message

Vitaly Sedelnik (vsedelnik) wrote on 2016-03-23:

Won't Fix for 8.0-updates because of Medium importance. Targeted to 9.0

tags:

added: wontfix-low

Kristina Berezovskaia (kkuznetsova) on 2016-06-10

tags:

added: on-verification

Revision history for this message

Kristina Berezovskaia (kkuznetsova) wrote on 2016-06-10:

Verify on
cat /etc/fuel_build_id:
461
cat /etc/fuel_build_number:
461
cat /etc/fuel_release:
9.0
cat /etc/fuel_openstack_version:
mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
fuel-release-9.0.0-1.mos6349.noarch
fuel-misc-9.0.0-1.mos8451.noarch
python-packetary-9.0.0-1.mos140.noarch
fuel-bootstrap-cli-9.0.0-1.mos285.noarch
fuel-migrate-9.0.0-1.mos8451.noarch
rubygem-astute-9.0.0-1.mos750.noarch
fuel-mirror-9.0.0-1.mos140.noarch
shotgun-9.0.0-1.mos90.noarch
fuel-openstack-metadata-9.0.0-1.mos8741.noarch
fuel-notify-9.0.0-1.mos8451.noarch
nailgun-mcagents-9.0.0-1.mos750.noarch
python-fuelclient-9.0.0-1.mos325.noarch
fuel-9.0.0-1.mos6349.noarch
fuel-utils-9.0.0-1.mos8451.noarch
fuel-setup-9.0.0-1.mos6349.noarch
fuel-provisioning-scripts-9.0.0-1.mos8741.noarch
fuel-library9.0-9.0.0-1.mos8451.noarch
network-checker-9.0.0-1.mos74.x86_64
fuel-agent-9.0.0-1.mos285.noarch
fuel-ui-9.0.0-1.mos2717.noarch
fuel-ostf-9.0.0-1.mos935.noarch
fuelmenu-9.0.0-1.mos273.noarch
fuel-nailgun-9.0.0-1.mos8741.noarch