[stein][neutron][bridge config][kolla]ovs-vsctl shows issue with bridge config

Arnaud Morin arnaud.morin at gmail.com
Wed Feb 17 11:35:37 UTC 2021


Hello,

I dont have the whole picture of your network architecture, but if it is
correct you should have a tap interface in br-int for your instance.
Then the br-int should be connected to br-ex through a patch (something
like int-patch-ex or similar).

The you should have a physical interface in br-ex (like eth2).

You can also try to see if the DHCP agent succesfully created ports in
your provider network (openstack port list, if you see some down ports,
then you have an issue).

Good luck!

-- 
Arnaud Morin

On 17.02.21 - 16:07, roshan anvekar wrote:
> Hello Folks,
> 
> Any suggestions on this??
> 
> Thank you
> 
> On Tue, Feb 16, 2021, 12:28 PM roshan anvekar <roshananvekar at gmail.com>
> wrote:
> 
> > Hello,
> >
> > I have tried multiple options of setting up the bridge interface for vlan
> > provider network setup in stein. None is allowing the gm to get IP. Getting
> > the same DHCP issue all the time.
> >
> > I tried with:
> > 1. Setting provider network interface as as sub interface on a bond.
> > Connecting bridge with it.
> > 2. Setting bridge directly over bond.
> > 3. Manual setup of bridge interface.
> > 4. Allowing Openstack to setup bridge on the bond.
> >
> > None of this is working. All are giving the same DHCP issue.
> >
> > Also I m using a sub-interface on the same bond for TLS interface. Not
> > sure if that's causing a issue.
> >
> > Error message in openvswitch container while running ovs-vsctl show
> > command:
> >
> > *error: "could not add network device br-ex to ofproto (File exists)"*
> >
> > Any pointers for this issue??
> >
> > Regards,
> > Roshan
> >



More information about the openstack-discuss mailing list