yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #65226
[Bug 1696104] Re: iptables without ipset are not being restored after reboot
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1696104
Title:
iptables without ipset are not being restored after reboot
Status in neutron:
Invalid
Bug description:
After deleting all VMs from compute node there are related to ipset
entries left in /etc/iptables/rules.v4. So after restarting this node
not all of the entries would be restored.
Steps to reproduce:
1. Create VM
2. Delete VM
3. Check number of entries in iptables-save
4. Reboot compute node
5. Check number of entries in iptables-save or run `iptables-restore < /etc/iptables/rules.v4`
Expected output:
Not all entries are restored
Actual output:
# iptables-restore < /etc/iptables/rules.v4
iptables-restore v1.4.21: Set NIPv4d6056099-2723-45ac-bf56- doesn't exist.
Error occurred at line: 161
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
Version:
Openstack Mitaka
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1696104/+subscriptions
References