yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1194389

Title:
  iptables manager does not honor top param of add_rule

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  When I add some rules with add_rule method of IptablesTable class,
  sometimes the top parameter is not always honored.

  to reproduce:

  self.iptables.ipv4['filter'].add_chain('filter')
  self.iptables.ipv4['filter'].add_rule('filter',
                                        '-s 0/0 -d 192.168.0.2 -j'
                                        ' RETURN',
                                        top=True)
  self.iptables.ipv4['filter'].add_rule('filter',
                                        '-s 0/0 -d 192.168.0.3 -j'
                                        ' RETURN',
                                        top=False)
  self.iptables.ipv4['filter'].add_rule('filter',
                                        '-s 0/0 -d 192.168.0.4 -j'
                                        ' RETURN',
                                        top=True)
  self.iptables.apply()

  the good order should be:

  -s 0/0 -d 192.168.0.2 -j RETURN
  -s 0/0 -d 192.168.0.4 -j RETURN
  -s 0/0 -d 192.168.0.3 -j RETURN

  and I get:

  -s 0/0 -d 192.168.0.2 -j RETURN
  -s 0/0 -d 192.168.0.3 -j RETURN
  -s 0/0 -d 192.168.0.4 -j RETURN

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1194389/+subscriptions