Dear Neutron Team, I was the bugs deputy for the week of Aug 12th - Aug 19th. Here's the summary of the bugs that were filed: Something what needs attention to clarify: https://bugs.launchpad.net/neutron/+bug/1787385 - vpnaas and dynamic-routing missing neutron-tempest-plugin in test-requirements.txt https://bugs.launchpad.net/neutron/+bug/1787420 - Floating ip association to router interface should be restricted - Confirmed behavior - should be like that? New: https://bugs.launchpad.net/neutron/+bug/1787534 - DNS extension broken for provider networks - configuration or code issue? Confirmed: https://bugs.launchpad.net/neutron/+bug/1786934 - Duplicating packet log when enable security group logging - another issue split from https://bugs.launchpad.net/neutron/+bug/1781372 In progress: https://bugs.launchpad.net/neutron/+bug/1786746 - issue with not deleted NFLOG - fix proposed https://review.openstack.org/#/c/591978/ https://bugs.launchpad.net/neutron/+bug/1787028 - neutron returned internal server error on updating tags - issue observed on gates - ERROR neutron.api.v2.resource StaleDataError: UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched. https://bugs.launchpad.net/neutron/+bug/1787106 - cannot ping over router between VMs in two different subnets, with allowed ICMP and set logging https://bugs.launchpad.net/neutron/+bug/1787119 - [Logging] firewall_group log resource and security_group log resource could not co-exist correctly Potentially RFE: https://bugs.launchpad.net/neutron/+bug/1787793 - Does not support shared N-S qos per-tenant - looks like a RFE question? https://bugs.launchpad.net/neutron/+bug/1787792 - Does not support ipv6 N-S qos - looks like a RFE question? Best regards, -- Paweł Suder