Hi,
OK, I was able to reproduce the problem locally in devstack as stated in
comment #3. The patch I proposed does fix it for me, so I am somewhat
confident that it will also fix for you, but wanted to be sure.
If you can take a look at the patch itself, the code is quite small.
Thanks again
Hi,
Thanks for reporting it, I was looking into the problem and saw that we
are actually checking if the snat is enabled in order to call
update_nat_rules() in the update_router() method. I've fixed the problem
at https://review.opendev.org/c/openstack/neutron/+/788485
I tested it locally
** Changed in: neutron
Assignee: (unassigned) => Lucas Alvares Gomes (lucasagomes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922089
Title:
[ovn] enable_snat cannot be disabled o
** Changed in: neutron
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881771
Title:
neutron-ipset-cleanup fails with Traceback: Unhandled error:
I'm also marking ironic-inspector as affected here because in the logs I
see (thanks to bfournier for pointing it out):
2016-12-21 06:39:16.254 24006 ERROR ironic_inspector.node_cache [-] [node:
f06c26d1-8008-47a9-a687-d5ef05083e41 state None] Database integrity error
