[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2020-03-27 Thread Junien Fridrick
@hopem I think it got installed as Pike but with old charm config options used. I can't argue against "don't use external_network_bridge", and I guess no one uses that in recent openstacks, so no one is getting hit by this bug ? If anything, we should log the exception in

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2020-03-27 Thread Edward Hope-Morley
Does feel like the code change in https://review.opendev.org/#/c/564825/10/neutron/agent/l3/router_info.py could be reverted though since it only affects the legacy config and is also breaking it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2020-03-27 Thread Edward Hope-Morley
@axino I assume the environment you have that is using external_network_bridge/external_network_id is quite old and was originally deployed with a version older than Queens? Using these option to configure external networks is really deprecated and since at least Juno we have used bridge_mappings

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2020-03-27 Thread Edward Hope-Morley
@slaweq the bug description says this issue was observed in Queens which is currently under Extended Maintenance so presumably still eligible for fixes if there is sufficient consensus on their criticality and enough people to review. We also need to consider upgrades from Q -> R -> S where people

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2019-07-09 Thread Slawek Kaplonski
Hi, Currently, since Stein there is no external_network_bridge config option at all. Is it still an issue? Maybe it's still a problem in some stable releases (which ones)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2019-07-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: neutron (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799737 Title:

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2018-11-26 Thread YAMAMOTO Takashi via ubuntu-bugs
** Tags added: l3-ipam-dhcp ** Changed in: neutron Importance: Undecided => High ** Changed in: neutron Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799737

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2018-11-26 Thread YAMAMOTO Takashi via ubuntu-bugs
** Tags added: ovs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799737 Title: l3 agent external_network_bridge broken with ovs To manage notifications about this bug go to:

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2018-11-19 Thread Junien Fridrick
The charm appears to do the right thing, it marks the feature as "deprecated" but properly configures it whenever asked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799737 Title: l3 agent

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2018-11-05 Thread Corey Bryant
Hi Junien, Thanks for reporting this and making Ubuntu better. I've added the upstream neutron project to this bug as this doesn't appear to be limited to the Ubuntu package. Does the charm also need a fix for this? If so we should add the charm project to this bug. Thanks, Corey ** Also

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2018-10-26 Thread Junien Fridrick
This cloud is indeed upgraded from pike, and using juju charms - said charms still offer the option to set external_network_bridge, although the option is clearly marked as "deprecated". In my book, "deprecated" doesn't mean "completely broken" though... If I use "external_network_bridge = ",

[Bug 1799737] Re: l3 agent external_network_bridge broken with ovs

2018-10-24 Thread Albert Damen
I guess you upgraded from an original neutron 8 config to queens. In queens external_network_bridge has been deprecated and should not be used (Using this will result in incorrect port statuses). What happens if you use "external_network_bridge = " -- You received this bug notification because