[openstack-dev] [neutron] Bug deputy report
Hi all, I'm zhaobo, I was the bug deputy for the last week and I'm afraid that cannot attending the comming upstream meeting so I'm sending out this report: Last week there are some high priority bugs for neutron . What a quiet week. ;-) Also some bugs need to attention, I list them here: [High] Race conditions in neutron_tempest_plugin/scenario/test_security_groups.py https://bugs.launchpad.net/neutron/+bug/1801306 TEMPEST CI FAILURE, the result is caused by some tempest tests operate the default SG, that will affect other test cases. Migration causes downtime while doing bulk_pull https://bugs.launchpad.net/neutron/+bug/1801104 Seems refresh the local cache so frequently, also if the records we want from neutron-server are so large, could we improve the query filter for improve performance on agent rpc? [Need Attention] Network: concurrent issue for create network operation https://bugs.launchpad.net/neutron/+bug/1800417 This looks like an exist issue for master. I think this must be an issue, but the bug lacks some logs for deep into, so hope the reporter can provider more details about it at first. [RFE]Neutron API Server: unexpected behavior with multiple long live clients https://bugs.launchpad.net/neutron/+bug/1800599 I have changed this bug to a new RFE, as it introduces an new mechanism to make sure each request can be processed to the maximum extend if possible, without long time waiting on client side. Thanks, Best Regards, ZhaoBo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] Bug deputy report
Hi all, I'm zhaobo, I was the bug deputy for the last week and I'm afraid that cannot attending the comming upstream meeting so I'm sending out this report: Last week there are some high priority bugs for neutron . Also some bugs need to attention, I list them here: [High] Deleting a port on a system with 1K ports takes too long https://bugs.launchpad.net/neutron/+bug/1779882 As the desciption, delete 1k port will cost mostly 35s, and seems related to the policy checking for consume much time. We need to check how to increase the performance if it's an issue. Also, thanks @Ajo for correct. L3 AttributeError in doc job https://bugs.launchpad.net/neutron/+bug/1779801 Queens neutron broken with recent L3 removal from neutron-lib.constants https://bugs.launchpad.net/neutron/+bug/1780376 These bugs need to be attentioned, as the neutron-lib increase and remove some in-use code(https://github.com/openstack/neutron-lib/commit/ec829f9384547864aebb56390da8e17df7051aac). It already affected Neutron Queens release. [Medium] A race condition may occur when concurrent agent scheduling happens https://bugs.launchpad.net/neutron/+bug/1780357 The DHCP and L3 agent maybe in race condition during scheduling process. [Need Attention] Sending SIGHUP to neutron-server process causes it to hang https://bugs.launchpad.net/neutron/+bug/1780139 This bug hit in Queens release and in container env, need help from someone who is familiar with it to test. [fwaas] FWaaS instance stuck in PENDING_CREATE when devstack enable fwaas-v1 https://bugs.launchpad.net/neutron/+bug/1779978 FWAAS V1?? Add or remove firewall rules, caused the status of associated firewall becomes "PENDING_UPDATE" https://bugs.launchpad.net/neutron/+bug/1780883 These 2 bugs seems hit the same issue, I will fix and associated with the first one. Both of them seems the FWv1 devstack configuration issue. Thanks, Best Regards, ZhaoBo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] Bug deputy report
Hi all, I'm zhaobo, I was the bug deputy for the last week and I'm afraid that cannot attending the comming upstream meeting so I'm sending out this report: Last week there are some high priority bugs for neutron . Also some bugs need to attention, I list them here: High priority --- [CI failure] https://bugs.launchpad.net/neutron/+bug/1756301 Tempset DVR HA miltimode tests fails as no FIP connectivity. I suspect that it may be a devstack bug. https://bugs.launchpad.net/neutron/+bug/1755243 In DVR HA scenarios, it will hit the AttributeError if depoly a LB on the network node, and Neutron depolys a DvrEdgeRouter on the network node for LB, when server call "router_update" to agent, agent side want to check whether the router is an ha router. Then hit the error as DvrEdgeRouter doesn't have a attribute named "ha_state". I found Brain and Swaminathan already work around with the bug reporter. Medium priority --- https://bugs.launchpad.net/neutron/+bug/1756406 Dvr mac address format may be invalid for non native openflow interface, Swamination has already work on it. Need attention -- https://bugs.launchpad.net/neutron/+bug/1754695 As the bug description, the vxlan port on br-tun may miss in L3 DVR+HA large scale env, the probability of failure seems high. I have no idea about this, so need help from L3 team experts, then setting the priority. https://bugs.launchpad.net/neutron/+bug/1755810 plugins.ml2.plugin.Ml2Plugin#_bind_port_if_needed There is a concurrency issue here, it will lead to a missing RPC notification which in turn result in a port stuck in DOWN status following a live-migration. I think we can check the details in the Bug descrption, it is enough to explain what the problem is. https://bugs.launchpad.net/neutron/+bug/1737917 In l2pop scenarios, linux bridge agent want to rpc to server with "update_port_down", server will call list_router_ids_on_host with l3plugin, then it raise the error, agent will get the remote rpc error.So the process may looks like NeutronServer try to find l3 agent on compute node and failed. This bug is reported for a long time, as the reporter said he still hit the same issue on Queen/master, so I think it is worth to raise here. https://bugs.launchpad.net/neutron/+bug/1755414 This sounds like a enhancement for routing function. So need to raise it and discuss with our L3 experts about whether we need the "metric". https://bugs.launchpad.net/neutron/+bug/1756064 Trunk bridge residue if restart the nove-compute before remove the vm in ovs-dpdk. As armando said, it may be related DPDK process. Armando mark it as Incomplete now for need more description about the issue condition. Thanks, Best Regards, ZhaoBo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron]Why neutron-vpnaas support transport vpn mode?
HI , Neutron guys: Currently, I found the neutron vpn service which is ipsec vpn support transport mode. And the current data model is that a vpn service must be associated with a Router instance. AFAIK, transport mode can not pass through a Router with NAT and usually used by P-to-P VPN not for the current site-to-site type. Just a question about it, is that we just support as the configuration/vpn backend support? What the usecase towards Openstack env? Thanks, Best Regards,__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] Bug deputy report
Hi all, I'm zhaobo, I was the bug deputy for the last week and I'm afraid that cannot attending the comming upstream meeting so I'm sending out this report: Last week there is not very priority for neutron function bug. But some CI failure related. CI FAILURE: https://bugs.launchpad.net/neutron/+bug/1733649 -- This is about fullstack one, Slawek Kaplonski had focused on it. https://bugs.launchpad.net/neutron/+bug/1734265 -- This is about the neutron-dynamic-routing didn't met the new extension directory. Other need concerned are: https://bugs.launchpad.net/neutron/+bug/1733852 -- In DVR&l2pop env, the arp entry generated is wrong if we use a port for VIP(we use in allowed address pairs) such as LoadBalancer things, the mac in generated arp entry will come from the notbound port. So need the best approach for it. https://bugs.launchpad.net/neutron/+bug/1734136 -- would be good if Qos team could have a look to prioritize this bug, as this may be caused the backend does the wrong behavior. Thanks, Best Regards, ZhaoBo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
