[Yahoo-eng-team] [Bug 1447651] Re: Find many duplicate rules in memory by using iptables_manager
Fix proposed to branch: master Review: https://review.openstack.org/596634 ** Changed in: neutron Status: Expired => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1447651 Title: Find many duplicate rules in memory by using iptables_manager Status in neutron: In Progress Bug description: I installed VPNaas In my devstack. I find many duplicate iptables rules in memory. The rule is ' 2015-04-23 10:55:15.380 ERROR neutron.agent.linux.iptables_manager [-] ## rule is -A neutron- vpn-agen-POSTROUTING -s 192.168.10.0/24 -d 192.168.20.1/24 -m policy --dir out --pol ipsec -j ACCEPT ', and I add this log in 'agent/linux/iptables_manager.py ' after ' _modify_rules '. Why there are duplicate iptables rules? Does iptables_manager weed out duplicate rules? To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1447651/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1783378] Re: Following protocol 73 name change , neutron constants have to be updated too
Reviewed: https://review.openstack.org/585489 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=034db863a02ce38a520e4b8aa3a65e1ccdb37f30 Submitter: Zuul Branch:master commit 034db863a02ce38a520e4b8aa3a65e1ccdb37f30 Author: Dave Hill Date: Tue Jul 24 13:41:28 2018 -0400 Use system protocol assigments for iptables protocol map Merge the system protocol assignments into the iptables name to protocol mapping array, IPTABLES_PROTOCOL_NAME_MAP, so that systems with updated or new values in /etc/protocols can successfully install iptables rules. This was done as an IptablesFirewallDriver() instance mapping since there is typically only a single instance per-agent, and it also allows us to more easily unit test it. Change-Id: Ib73def4e2a9e3644462fdee312768382fcb800a5 Closes-Bug: #1783378 ** Changed in: neutron Status: In Progress => 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/1783378 Title: Following protocol 73 name change , neutron constants have to be updated too Status in neutron: Fix Released Bug description: Following protocol 73 name change , neutron constants have to be updated too [root@undercloud-0-rhosp10 ~]# cat /etc/protocols | grep 73 cphb73 CPHB# Computer Protocol Heart Beat [dhill@otto neutron]$ grep -r rspf * neutron/common/constants.py: '73': 'rspf', To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1783378/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1789074] [NEW] failed to boot guest with vnic_type direct when rx_queue_size and tx_queue_size are set
Public bug reported: Description of problem: Nova compute forces the virtio RX/TX Queue Size also on SRIOV devices. This makes VM spawn to fail. The configurable RX/TX Queue Size code is similar all the way from OSP10 to OSP13, so it's possible the issue is present also on other releases. Version-Release number of selected component (if applicable): OSP13 z3 How reproducible: (quick and dirty way) Change nova config file # crudini --set /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt rx_queue_size 1024 # crudini --set /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt tx_queue_size 1024 # restart nova_compute container docker restart nova_compute # boot a VM with an SRIOV (PF or VF) interface Actual results: Nova add on the sriov port section rx_queue_size Expected results: Additional info: ** Affects: nova Importance: Undecided Assignee: Moshe Levi (moshele) Status: New ** Changed in: nova Assignee: (unassigned) => Moshe Levi (moshele) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1789074 Title: failed to boot guest with vnic_type direct when rx_queue_size and tx_queue_size are set Status in OpenStack Compute (nova): New Bug description: Description of problem: Nova compute forces the virtio RX/TX Queue Size also on SRIOV devices. This makes VM spawn to fail. The configurable RX/TX Queue Size code is similar all the way from OSP10 to OSP13, so it's possible the issue is present also on other releases. Version-Release number of selected component (if applicable): OSP13 z3 How reproducible: (quick and dirty way) Change nova config file # crudini --set /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt rx_queue_size 1024 # crudini --set /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt tx_queue_size 1024 # restart nova_compute container docker restart nova_compute # boot a VM with an SRIOV (PF or VF) interface Actual results: Nova add on the sriov port section rx_queue_size Expected results: Additional info: To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1789074/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
