*** This bug is a duplicate of bug 1584647 ***
https://bugs.launchpad.net/bugs/1584647
On the assumption that bug 1584647 resolved this issue marking as a dupe
- please comment if this is not the case or the issue remains.
** This bug has been marked a duplicate of bug 1584647
[SRU] "Inter
I believe that part of all of this issue is resolved by
https://bugs.launchpad.net/neutron/+bug/1584647 which is currently being
backported to Xenial/Mitaka
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Need to triage in the Master branch to see if we still see such issue.
Also need to check if there was a bug fix that went in after Mitaka for
this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I've added upstream neutron to the bug. Keeping in mind this is mitaka
and unsupported by upstream, but perhaps someone from upstream knows
whether this is fixed in a mitaka+ release or not.
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notificatio
Possibly also related: https://bugs.launchpad.net/neutron/+bug/1697243
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758868
Title:
ovs restart can lead to critical ovs flows missing
To manage noti
Based on neutron-ovs-cleanup not being restarted since early February, I
don't think this is related to the recent neutron regression.
I would like to test with the following patch. After a brief look at the code,
it doesn't appear to fix the issue, but perhaps I missed something so I think
it'
I'm fairly confident this is not the ovs-cleanup bug. "grep neutron-ovs-
cleanup syslog" doesn't have anything, I'm using neutron-plugin-
openvswitch-agent 2:8.4.0-0ubuntu6, and neutron-ovs-cleanup.service is
"Active: active (exited) since Mon 2018-02-19 05:09:12 UTC; 1 months 4
days ago" so it did
neutron-ovs-cleanup was run after upgrading pkg?
and you can check if that service is fine with below
systemctl list-units --failed
if it is failed state, ovs-cleanup can run while upgrading and blow all
ports
This seems different issue but checking it for sure
--
You received this bug notifi
Hi Junien, I see that you have stated that you are using neutron version
2:8.4.0-0ubuntu6 which for the sake of this comment is fine but just to
close the loop:
The current version of neutron in xenial-updates i.e. 2:8.4.0-0ubuntu7.1
introduced a regression [1][2] that produces almost exactly the
This problem can probably be easily replicated if you replace /usr/bin
/ovsdb-client (used by the polling manager) by a shell script that
sleeps 0.5s and then exec the actual ovsdb-client.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
10 matches
Mail list logo
