Activity log for bug #1592534
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2016-06-14 19:29:35 | Dmitry Sutyagin | bug | added bug | ||
| 2016-06-14 19:36:57 | Dmitry Sutyagin | description | Reproducible on - all version up to 8.0, have not tried on 9.0 Description: restarting neutron-plugin-openvswitch-agent introduces network downtime stop of the agent does not introduce downtime, but start does. Steps to reproduce: 1 - start ping of a floating ip / internal ip of a VM 2 - stop neutron-plugin-openvswitch-agent on compute 3 - start neutron-plugin-openvswitch-agent on compute 4 - observe several lost packets I believe it should be possible to start agent without manipulating ovs internals if they are already correctly set up - we need to make necessary checks (read operations) and act based on results, and avoid touching anything which is already configured correctly. I believe the same issue is with neutron-l3-agent. | Reproducible on - all version up to 8.0, have not tried on 9.0 Description: restarting neutron-plugin-openvswitch-agent introduces network downtime stop of the agent does not introduce downtime, but start does. Steps to reproduce: 1 - start ping of a floating ip / internal ip of a VM 2 - stop neutron-plugin-openvswitch-agent on compute 3 - start neutron-plugin-openvswitch-agent on compute 4 - observe several lost packets I believe it should be possible to start agent without manipulating ovs internals if they are already correctly set up - we need to make necessary checks (read operations) and act based on results, and avoid touching anything which is already configured correctly. I believe a similar issue is with neutron-l3-agent if we kill it and then it starts back up (by pacemaker) | |
| 2016-06-14 19:38:02 | Bug Checker Bot | tags | support | need-info support | |
| 2016-06-14 20:13:26 | Eugene Nikanorov | mos: importance | Undecided | Medium | |
| 2016-06-15 09:12:24 | Dina Belova | mos: milestone | 10.0 | ||
| 2016-06-15 09:12:26 | Dina Belova | mos: status | New | Confirmed | |
| 2016-06-15 09:12:58 | Dina Belova | tags | need-info support | move-to-10.0 need-info support | |
| 2016-07-06 13:27:20 | Alexander Ignatov | nominated for series | mos/9.x | ||
| 2016-07-06 13:27:20 | Alexander Ignatov | bug task added | mos/9.x | ||
| 2016-07-06 13:27:20 | Alexander Ignatov | nominated for series | mos/10.0.x | ||
| 2016-07-06 13:27:20 | Alexander Ignatov | bug task added | mos/10.0.x | ||
| 2016-07-06 13:27:27 | Alexander Ignatov | mos/9.x: milestone | 10.0 | 9.1 | |
| 2016-07-06 13:27:30 | Alexander Ignatov | mos/10.0.x: status | New | Confirmed | |
| 2016-07-06 13:27:32 | Alexander Ignatov | mos/10.0.x: importance | Undecided | Medium | |
| 2016-07-06 13:27:39 | Alexander Ignatov | mos/10.0.x: assignee | MOS Neutron (mos-neutron) | ||
| 2016-07-06 13:27:41 | Alexander Ignatov | mos/10.0.x: milestone | 10.0 | ||
| 2016-07-06 13:27:58 | Alexander Ignatov | mos/9.x: assignee | MOS Neutron (mos-neutron) | Alexander Ignatov (aignatov) | |
| 2016-07-06 14:03:43 | Alexander Ignatov | tags | move-to-10.0 need-info support | 10.0-reviewed move-to-10.0 need-info support | |
| 2016-07-12 14:08:22 | Alexander Ignatov | mos/10.0.x: status | Confirmed | Invalid | |
| 2016-07-12 14:08:28 | Alexander Ignatov | mos/9.x: status | Confirmed | Invalid | |
| 2016-07-13 12:54:02 | Dmitry Sutyagin | nominated for series | mos/8.0.x | ||
| 2016-07-13 12:54:02 | Dmitry Sutyagin | bug task added | mos/8.0.x | ||
| 2016-07-13 12:54:11 | Dmitry Sutyagin | mos/8.0.x: status | New | Confirmed | |
| 2016-07-13 12:55:25 | Dmitry Sutyagin | mos/8.0.x: assignee | MOS Maintenance (mos-maintenance) | ||
| 2016-07-13 12:55:33 | Dmitry Sutyagin | mos/8.0.x: milestone | 8.0-updates | ||
| 2016-07-22 12:54:40 | Vitaly Sedelnik | mos/8.0.x: importance | Undecided | Medium | |
| 2016-09-02 13:43:38 | Denis Meltsaykin | mos/8.0.x: status | Confirmed | Won't Fix |
