I was on bug deputy in week of 8.10.2018 to 15.10.2018.
Below is summary of reported bugs for Neutron:

Bugs which needs some look to confirm them:
* https://bugs.launchpad.net/neutron/+bug/1795432 - neutron does not create the 
necessary iptables rules for dhcp agents when linuxbridge is used
        This one should be confirmed on multinode environment with Linuxbridge, 
I didn’t have such env to work on that.

* https://bugs.launchpad.net/neutron/+bug/1797368 - Trunk: different behavior 
of admin_state_up attribute between trunk and port
        I have no experience with trunks and I would like someone else to take 
a look on that. From description it looks for me that it’s valid issue

* https://bugs.launchpad.net/neutron/+bug/1795816 - neutron_dynamic_routing Bgp 
floatingip_update KeyError: 'last_known_router_id
        Should be good that someone more familiar with neutron-dynamic-routing 
could take a look on it.
        I don’t have environment to confirm it but from bug report it looks as 
valid bug.
        Importance set to medium

Bugs triaged or triage in progress already:
* https://bugs.launchpad.net/neutron/+bug/1796491 - DVR Floating IP setup in 
the SNAT namespace of the network node and also in the qrouter namespace in the 
compute node 
        Swami is checking if it wasn’t already fixed…

* https://bugs.launchpad.net/neutron/+bug/1796824 - Port in some type of 
device_owner should not allow update IP address
        Importance set to Medium

* https://bugs.launchpad.net/neutron/+bug/1797037 - Extra routes configured on 
routers are not set in the router namespace and snat namespace with DVR-HA 
        already in progress, importance Medium

* https://bugs.launchpad.net/neutron/+bug/1796854 - Neutron doesn't respect 
advscv role while creating port
        Importance set to Medium, this is an neutron-lib issue

* https://bugs.launchpad.net/neutron/+bug/1796976 - neutron.conf needs 
lock_path set for router to operate 
        Docs issue - importance Low,

* https://bugs.launchpad.net/neutron/+bug/1797084 - Stale namespaces when 
fallback tunnels are present
        Importance Low, patch already proposed by dalvarez

* https://bugs.launchpad.net/neutron/+bug/1797298 - Router gateway device are 
repeatedly configured When ha changed
        Importance Low, patch already proposed

* https://bugs.launchpad.net/neutron/+bug/1796703 - HA router interfaces in 
standby state 
        Needs look by some L3 experts - I already raised this on on L3 Sub-team 
meeting and Brian is triaging it now

* https://bugs.launchpad.net/neutron/+bug/1796230 - no libnetfilter-log1 
package on centos 
        Waiting for reply for Brian’s question now….

* https://bugs.launchpad.net/neutron/+bug/1763608 - Netplan ignores Interfaces 
without IP Addresses 
        I asked how it’s related to neutron as I don’t understand that. Waiting 
for reply now.

* https://bugs.launchpad.net/neutron/+bug/1795222 - [l3] router agent side 
gateway IP not changed if directly change IP address
        Importance medium, patch already proposed

* https://bugs.launchpad.net/neutron/+bug/1797663 - refactor def 
_get_dvr_sync_data from neutron/db/l3_dvr_db.py
        Importance wishlist,

* https://bugs.launchpad.net/neutron/+bug/1796629 - Incorrectly passing ext_ips 
as gw_ips after creating router gateway
        Importance set to medium

* https://bugs.launchpad.net/neutron/+bug/1796925 - [RFE] port forwarding 
floating IP QoS
* https://bugs.launchpad.net/neutron/+bug/1797140 - [RFE] create port by 
providing parameters subnet_id only

Potential RFEs maybe:
* https://bugs.launchpad.net/neutron/+bug/1792890 - The user can delete a 
security group which is used as remote-group-id
        It looks like maybe potential RFE as it may change current API behavior

Slawek Kaplonski
Senior software engineer
Red Hat

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to