Mailing List Archive: [PackStack][Neutron] erro port no present in bridge br-int

[PackStack][Neutron] erro port no present in bridge br-int

Nov 6, 2018, 4:23 AM

Post #1 of 6 (938 views)

Hi, I initilize an instance using a defined flat network and I got the
error:
port no present in bridge br-int

I have a 2 node deployment (controller + network, compute).

The output of the command ovs-vsctl show is

*On the network node*
d3a06f16-d727-4333-9de6-cf4ce3b0ce36
Manager "ptcp:6640:127.0.0.1"
is_connected: true
Bridge br-ex
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port br-ex
Interface br-ex
type: internal
Port phy-br-ex
Interface phy-br-ex
type: patch
options: {peer=int-br-ex}
Port "ens33"
Interface "ens33"
Bridge br-int
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port int-br-ex
Interface int-br-ex
type: patch
options: {peer=phy-br-ex}
Port "tapefb98047-57"
tag: 1
Interface "tapefb98047-57"
type: internal
Port "qr-d62d0c14-51"
tag: 1
Interface "qr-d62d0c14-51"
type: internal
Port "qg-5468707b-6d"
tag: 2
Interface "qg-5468707b-6d"
type: internal
Bridge br-tun
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port br-tun
Interface br-tun
type: internal
Port "vxlan-c0a8003d"
Interface "vxlan-c0a8003d"
type: vxlan
options: {df_default="true", in_key=flow,
local_ip="192.168.0.62", out_key=flow, remote_ip="192.168.0.61"}
ovs_version: "2.9.0"

*On the Compute node*

*55e62867-9c88-4925-b49c-55fb74d174bd*
* Manager "ptcp:6640:127.0.0.1"*
* is_connected: true*
* Bridge br-ex*
* Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
* is_connected: true*
* fail_mode: secure*
* Port phy-br-ex*
* Interface phy-br-ex*
* type: patch*
* options: {peer=int-br-ex}*
* Port "enp2s0"*
* Interface "enp2s0"*
* Port br-ex*
* Interface br-ex*
* type: internal*
* Bridge br-tun*
* Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
* is_connected: true*
* fail_mode: secure*
* Port br-tun*
* Interface br-tun*
* type: internal*
* Port "vxlan-c0a8003e"*
* Interface "vxlan-c0a8003e"*
* type: vxlan*
* options: {df_default="true", in_key=flow,
local_ip="192.168.0.61", out_key=flow, remote_ip="192.168.0.62"}*
* Port patch-int*
* Interface patch-int*
* type: patch*
* options: {peer=patch-tun}*
* Bridge br-int*
* Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
* is_connected: true*
* fail_mode: secure*
* Port int-br-ex*
* Interface int-br-ex*
* type: patch*
* options: {peer=phy-br-ex}*
* Port br-int*
* Interface br-int*
* type: internal*
* Port patch-tun*
* Interface patch-tun*
* type: patch*
* options: {peer=patch-int}*
* ovs_version: "2.9.0"*

How can I solve the problem?

Thanks

Re: [PackStack][Neutron] erro port no present in bridge br-int [ In reply to ]

amotoki at gmail

Nov 6, 2018, 8:04 AM

Post #2 of 6 (936 views)

Permalink

How is your [ovs] bridge_mapping in your configuration?
Flat network requires a corresponding bridge_mapping entry and you also
need to create a corresponding bridge in advance.

2018?11?6?(?) 21:31 Soheil Pourbafrani <soheil.ir08@gmail.com>:

> Hi, I initilize an instance using a defined flat network and I got the
> error:
> port no present in bridge br-int
>
> I have a 2 node deployment (controller + network, compute).
>
> The output of the command ovs-vsctl show is
>
> *On the network node*
> d3a06f16-d727-4333-9de6-cf4ce3b0ce36
> Manager "ptcp:6640:127.0.0.1"
> is_connected: true
> Bridge br-ex
> Controller "tcp:127.0.0.1:6633"
> is_connected: true
> fail_mode: secure
> Port br-ex
> Interface br-ex
> type: internal
> Port phy-br-ex
> Interface phy-br-ex
> type: patch
> options: {peer=int-br-ex}
> Port "ens33"
> Interface "ens33"
> Bridge br-int
> Controller "tcp:127.0.0.1:6633"
> is_connected: true
> fail_mode: secure
> Port br-int
> Interface br-int
> type: internal
> Port patch-tun
> Interface patch-tun
> type: patch
> options: {peer=patch-int}
> Port int-br-ex
> Interface int-br-ex
> type: patch
> options: {peer=phy-br-ex}
> Port "tapefb98047-57"
> tag: 1
> Interface "tapefb98047-57"
> type: internal
> Port "qr-d62d0c14-51"
> tag: 1
> Interface "qr-d62d0c14-51"
> type: internal
> Port "qg-5468707b-6d"
> tag: 2
> Interface "qg-5468707b-6d"
> type: internal
> Bridge br-tun
> Controller "tcp:127.0.0.1:6633"
> is_connected: true
> fail_mode: secure
> Port patch-int
> Interface patch-int
> type: patch
> options: {peer=patch-tun}
> Port br-tun
> Interface br-tun
> type: internal
> Port "vxlan-c0a8003d"
> Interface "vxlan-c0a8003d"
> type: vxlan
> options: {df_default="true", in_key=flow,
> local_ip="192.168.0.62", out_key=flow, remote_ip="192.168.0.61"}
> ovs_version: "2.9.0"
>
> *On the Compute node*
>
> *55e62867-9c88-4925-b49c-55fb74d174bd*
> * Manager "ptcp:6640:127.0.0.1"*
> * is_connected: true*
> * Bridge br-ex*
> * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
> * is_connected: true*
> * fail_mode: secure*
> * Port phy-br-ex*
> * Interface phy-br-ex*
> * type: patch*
> * options: {peer=int-br-ex}*
> * Port "enp2s0"*
> * Interface "enp2s0"*
> * Port br-ex*
> * Interface br-ex*
> * type: internal*
> * Bridge br-tun*
> * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
> * is_connected: true*
> * fail_mode: secure*
> * Port br-tun*
> * Interface br-tun*
> * type: internal*
> * Port "vxlan-c0a8003e"*
> * Interface "vxlan-c0a8003e"*
> * type: vxlan*
> * options: {df_default="true", in_key=flow,
> local_ip="192.168.0.61", out_key=flow, remote_ip="192.168.0.62"}*
> * Port patch-int*
> * Interface patch-int*
> * type: patch*
> * options: {peer=patch-tun}*
> * Bridge br-int*
> * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
> * is_connected: true*
> * fail_mode: secure*
> * Port int-br-ex*
> * Interface int-br-ex*
> * type: patch*
> * options: {peer=phy-br-ex}*
> * Port br-int*
> * Interface br-int*
> * type: internal*
> * Port patch-tun*
> * Interface patch-tun*
> * type: patch*
> * options: {peer=patch-int}*
> * ovs_version: "2.9.0"*
>
> How can I solve the problem?
>
> Thanks
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>

Re: [PackStack][Neutron] erro port no present in bridge br-int [ In reply to ]

laszlo.budai at gmail

Nov 6, 2018, 10:51 PM

Post #3 of 6 (935 views)

Permalink

Hi

we had a similar situation when the ``host`` entry in the neutron.conf was different than the host entry in the nova.conf on the compute nodes.
So if you're setting a ``host`` entry in one of these files, then make sure the other file contains the same ``host`` setting.

see https://docs.openstack.org/neutron/rocky/configuration/neutron.html#DEFAULT.host and https://docs.openstack.org/nova/rocky/configuration/config.html#DEFAULT.host

Kind regards,
Laszlo

On 11/6/18 6:04 PM, Akihiro Motoki wrote:
> How is your [ovs] bridge_mapping in your configuration?
> Flat network requires a corresponding bridge_mapping entry and you also need to create a corresponding bridge in advance.
>
>
> 2018?11?6?(?) 21:31 Soheil Pourbafrani <soheil.ir08@gmail.com <mailto:soheil.ir08@gmail.com>>:
>
> Hi, I initilize an instance using a defined flat network and I got the error:
> port no present in bridge br-int
>
> I have a 2 node deployment (controller + network, compute).
>
> The output of the command ovs-vsctl show is
> *
> *
> *On the network node*
> d3a06f16-d727-4333-9de6-cf4ce3b0ce36
> Manager "ptcp:6640:127.0.0.1"
> is_connected: true
> Bridge br-ex
> Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"
> is_connected: true
> fail_mode: secure
> Port br-ex
> Interface br-ex
> type: internal
> Port phy-br-ex
> Interface phy-br-ex
> type: patch
> options: {peer=int-br-ex}
> Port "ens33"
> Interface "ens33"
> Bridge br-int
> Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"
> is_connected: true
> fail_mode: secure
> Port br-int
> Interface br-int
> type: internal
> Port patch-tun
> Interface patch-tun
> type: patch
> options: {peer=patch-int}
> Port int-br-ex
> Interface int-br-ex
> type: patch
> options: {peer=phy-br-ex}
> Port "tapefb98047-57"
> tag: 1
> Interface "tapefb98047-57"
> type: internal
> Port "qr-d62d0c14-51"
> tag: 1
> Interface "qr-d62d0c14-51"
> type: internal
> Port "qg-5468707b-6d"
> tag: 2
> Interface "qg-5468707b-6d"
> type: internal
> Bridge br-tun
> Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"
> is_connected: true
> fail_mode: secure
> Port patch-int
> Interface patch-int
> type: patch
> options: {peer=patch-tun}
> Port br-tun
> Interface br-tun
> type: internal
> Port "vxlan-c0a8003d"
> Interface "vxlan-c0a8003d"
> type: vxlan
> options: {df_default="true", in_key=flow, local_ip="192.168.0.62", out_key=flow, remote_ip="192.168.0.61"}
> ovs_version: "2.9.0"
>
> *On the Compute node*
> *
> *
> *55e62867-9c88-4925-b49c-55fb74d174bd*
> * Manager "ptcp:6640:127.0.0.1"*
> * is_connected: true*
> * Bridge br-ex*
> * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
> * is_connected: true*
> * fail_mode: secure*
> * Port phy-br-ex*
> * Interface phy-br-ex*
> * type: patch*
> * options: {peer=int-br-ex}*
> * Port "enp2s0"*
> * Interface "enp2s0"*
> * Port br-ex*
> * Interface br-ex*
> * type: internal*
> * Bridge br-tun*
> * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
> * is_connected: true*
> * fail_mode: secure*
> * Port br-tun*
> * Interface br-tun*
> * type: internal*
> * Port "vxlan-c0a8003e"*
> * Interface "vxlan-c0a8003e"*
> * type: vxlan*
> * options: {df_default="true", in_key=flow, local_ip="192.168.0.61", out_key=flow, remote_ip="192.168.0.62"}*
> * Port patch-int*
> * Interface patch-int*
> * type: patch*
> * options: {peer=patch-tun}*
> * Bridge br-int*
> * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
> * is_connected: true*
> * fail_mode: secure*
> * Port int-br-ex*
> * Interface int-br-ex*
> * type: patch*
> * options: {peer=phy-br-ex}*
> * Port br-int*
> * Interface br-int*
> * type: internal*
> * Port patch-tun*
> * Interface patch-tun*
> * type: patch*
> * options: {peer=patch-int}*
> * ovs_version: "2.9.0"*
>
> How can I solve the problem?
>
> Thanks
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org <mailto:openstack@lists.openstack.org>
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [PackStack][Neutron] erro port no present in bridge br-int [ In reply to ]

soheil.ir08 at gmail

Nov 7, 2018, 4:52 AM

Post #4 of 6 (935 views)

Permalink

Thanks. In one node installation no error happened but in two node
installation, I got the error. So I guess the answer of Laszlo is
reasonable.

On Wed, Nov 7, 2018 at 10:23 AM Budai Laszlo <laszlo.budai@gmail.com> wrote:

> Hi
>
> we had a similar situation when the ``host`` entry in the neutron.conf was
> different than the host entry in the nova.conf on the compute nodes.
> So if you're setting a ``host`` entry in one of these files, then make
> sure the other file contains the same ``host`` setting.
>
> see
> https://docs.openstack.org/neutron/rocky/configuration/neutron.html#DEFAULT.host
> and
> https://docs.openstack.org/nova/rocky/configuration/config.html#DEFAULT.host
>
> Kind regards,
> Laszlo
>
> On 11/6/18 6:04 PM, Akihiro Motoki wrote:
> > How is your [ovs] bridge_mapping in your configuration?
> > Flat network requires a corresponding bridge_mapping entry and you also
> need to create a corresponding bridge in advance.
> >
> >
> > 2018?11?6?(?) 21:31 Soheil Pourbafrani <soheil.ir08@gmail.com <mailto:
> soheil.ir08@gmail.com>>:
> >
> > Hi, I initilize an instance using a defined flat network and I got
> the error:
> > port no present in bridge br-int
> >
> > I have a 2 node deployment (controller + network, compute).
> >
> > The output of the command ovs-vsctl show is
> > *
> > *
> > *On the network node*
> > d3a06f16-d727-4333-9de6-cf4ce3b0ce36
> > Manager "ptcp:6640:127.0.0.1"
> > is_connected: true
> > Bridge br-ex
> > Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"
> > is_connected: true
> > fail_mode: secure
> > Port br-ex
> > Interface br-ex
> > type: internal
> > Port phy-br-ex
> > Interface phy-br-ex
> > type: patch
> > options: {peer=int-br-ex}
> > Port "ens33"
> > Interface "ens33"
> > Bridge br-int
> > Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"
> > is_connected: true
> > fail_mode: secure
> > Port br-int
> > Interface br-int
> > type: internal
> > Port patch-tun
> > Interface patch-tun
> > type: patch
> > options: {peer=patch-int}
> > Port int-br-ex
> > Interface int-br-ex
> > type: patch
> > options: {peer=phy-br-ex}
> > Port "tapefb98047-57"
> > tag: 1
> > Interface "tapefb98047-57"
> > type: internal
> > Port "qr-d62d0c14-51"
> > tag: 1
> > Interface "qr-d62d0c14-51"
> > type: internal
> > Port "qg-5468707b-6d"
> > tag: 2
> > Interface "qg-5468707b-6d"
> > type: internal
> > Bridge br-tun
> > Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"
> > is_connected: true
> > fail_mode: secure
> > Port patch-int
> > Interface patch-int
> > type: patch
> > options: {peer=patch-tun}
> > Port br-tun
> > Interface br-tun
> > type: internal
> > Port "vxlan-c0a8003d"
> > Interface "vxlan-c0a8003d"
> > type: vxlan
> > options: {df_default="true", in_key=flow,
> local_ip="192.168.0.62", out_key=flow, remote_ip="192.168.0.61"}
> > ovs_version: "2.9.0"
> >
> > *On the Compute node*
> > *
> > *
> > *55e62867-9c88-4925-b49c-55fb74d174bd*
> > * Manager "ptcp:6640:127.0.0.1"*
> > * is_connected: true*
> > * Bridge br-ex*
> > * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
> > * is_connected: true*
> > * fail_mode: secure*
> > * Port phy-br-ex*
> > * Interface phy-br-ex*
> > * type: patch*
> > * options: {peer=int-br-ex}*
> > * Port "enp2s0"*
> > * Interface "enp2s0"*
> > * Port br-ex*
> > * Interface br-ex*
> > * type: internal*
> > * Bridge br-tun*
> > * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
> > * is_connected: true*
> > * fail_mode: secure*
> > * Port br-tun*
> > * Interface br-tun*
> > * type: internal*
> > * Port "vxlan-c0a8003e"*
> > * Interface "vxlan-c0a8003e"*
> > * type: vxlan*
> > * options: {df_default="true", in_key=flow,
> local_ip="192.168.0.61", out_key=flow, remote_ip="192.168.0.62"}*
> > * Port patch-int*
> > * Interface patch-int*
> > * type: patch*
> > * options: {peer=patch-tun}*
> > * Bridge br-int*
> > * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"*
> > * is_connected: true*
> > * fail_mode: secure*
> > * Port int-br-ex*
> > * Interface int-br-ex*
> > * type: patch*
> > * options: {peer=phy-br-ex}*
> > * Port br-int*
> > * Interface br-int*
> > * type: internal*
> > * Port patch-tun*
> > * Interface patch-tun*
> > * type: patch*
> > * options: {peer=patch-int}*
> > * ovs_version: "2.9.0"*
> >
> > How can I solve the problem?
> >
> > Thanks
> > _______________________________________________
> > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to : openstack@lists.openstack.org <mailto:
> openstack@lists.openstack.org>
> > Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> >
> >
> > _______________________________________________
> > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to : openstack@lists.openstack.org
> > Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> >
>
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>

Re: [PackStack][Neutron] erro port no present in bridge br-int [ In reply to ]

laszlo.budai at gmail

Nov 7, 2018, 6:09 AM

Post #5 of 6 (935 views)

Permalink

Hi,

please don't misunderstand me. If you have multiple nodes, then each of them will have its own ``host`` setting (like, host = node1 for node1 and host = node2 for node2). The important thing is that both the neutron.conf and nova.conf to have the same ``host`` setting on one node. So if you have used the ``host = node1`` in neutron.conf of node1, then do the same in the nova.conf on the same host. And if you have ``host = node2`` in neutron.conf on node2, then you should have the same in the nova.conf.

Kind regards,
Laszlo

On 11/7/18 2:52 PM, Soheil Pourbafrani wrote:
> Thanks. In one node installation no error happened but in two node installation, I got the error. So I guess the answer of Laszlo is reasonable.
>
> On Wed, Nov 7, 2018 at 10:23 AM Budai Laszlo <laszlo.budai@gmail.com <mailto:laszlo.budai@gmail.com>> wrote:
>
> Hi
>
> we had a similar situation when the ``host`` entry in the neutron.conf was different than the host entry in the nova.conf on the compute nodes.
> So if you're setting a ``host`` entry in one of these files, then make sure the other file contains the same ``host`` setting.
>
> see https://docs.openstack.org/neutron/rocky/configuration/neutron.html#DEFAULT.host and https://docs.openstack.org/nova/rocky/configuration/config.html#DEFAULT.host
>
> Kind regards,
> Laszlo
>
> On 11/6/18 6:04 PM, Akihiro Motoki wrote:
> > How is your [ovs] bridge_mapping in your configuration?
> > Flat network requires a corresponding bridge_mapping entry and you also need to create a corresponding bridge in advance.
> >
> >
> > 2018?11?6?(?) 21:31 Soheil Pourbafrani <soheil.ir08@gmail.com <mailto:soheil.ir08@gmail.com> <mailto:soheil.ir08@gmail.com <mailto:soheil.ir08@gmail.com>>>:
> >
> > Hi, I initilize an instance using a defined flat network and I got the error:
> > port no present in bridge br-int
> >
> > I have a 2 node deployment (controller + network, compute).
> >
> > The output of the command ovs-vsctl show is
> > *
> > *
> > *On the network node*
> > d3a06f16-d727-4333-9de6-cf4ce3b0ce36
> > Manager "ptcp:6640:127.0.0.1"
> > is_connected: true
> > Bridge br-ex
> > Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633> <http://127.0.0.1:6633>"
> > is_connected: true
> > fail_mode: secure
> > Port br-ex
> > Interface br-ex
> > type: internal
> > Port phy-br-ex
> > Interface phy-br-ex
> > type: patch
> > options: {peer=int-br-ex}
> > Port "ens33"
> > Interface "ens33"
> > Bridge br-int
> > Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633> <http://127.0.0.1:6633>"
> > is_connected: true
> > fail_mode: secure
> > Port br-int
> > Interface br-int
> > type: internal
> > Port patch-tun
> > Interface patch-tun
> > type: patch
> > options: {peer=patch-int}
> > Port int-br-ex
> > Interface int-br-ex
> > type: patch
> > options: {peer=phy-br-ex}
> > Port "tapefb98047-57"
> > tag: 1
> > Interface "tapefb98047-57"
> > type: internal
> > Port "qr-d62d0c14-51"
> > tag: 1
> > Interface "qr-d62d0c14-51"
> > type: internal
> > Port "qg-5468707b-6d"
> > tag: 2
> > Interface "qg-5468707b-6d"
> > type: internal
> > Bridge br-tun
> > Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633> <http://127.0.0.1:6633>"
> > is_connected: true
> > fail_mode: secure
> > Port patch-int
> > Interface patch-int
> > type: patch
> > options: {peer=patch-tun}
> > Port br-tun
> > Interface br-tun
> > type: internal
> > Port "vxlan-c0a8003d"
> > Interface "vxlan-c0a8003d"
> > type: vxlan
> > options: {df_default="true", in_key=flow, local_ip="192.168.0.62", out_key=flow, remote_ip="192.168.0.61"}
> > ovs_version: "2.9.0"
> >
> > *On the Compute node*
> > *
> > *
> > *55e62867-9c88-4925-b49c-55fb74d174bd*
> > * Manager "ptcp:6640:127.0.0.1"*
> > * is_connected: true*
> > * Bridge br-ex*
> > * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633> <http://127.0.0.1:6633>"*
> > * is_connected: true*
> > * fail_mode: secure*
> > * Port phy-br-ex*
> > * Interface phy-br-ex*
> > * type: patch*
> > * options: {peer=int-br-ex}*
> > * Port "enp2s0"*
> > * Interface "enp2s0"*
> > * Port br-ex*
> > * Interface br-ex*
> > * type: internal*
> > * Bridge br-tun*
> > * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633> <http://127.0.0.1:6633>"*
> > * is_connected: true*
> > * fail_mode: secure*
> > * Port br-tun*
> > * Interface br-tun*
> > * type: internal*
> > * Port "vxlan-c0a8003e"*
> > * Interface "vxlan-c0a8003e"*
> > * type: vxlan*
> > * options: {df_default="true", in_key=flow, local_ip="192.168.0.61", out_key=flow, remote_ip="192.168.0.62"}*
> > * Port patch-int*
> > * Interface patch-int*
> > * type: patch*
> > * options: {peer=patch-tun}*
> > * Bridge br-int*
> > * Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633> <http://127.0.0.1:6633>"*
> > * is_connected: true*
> > * fail_mode: secure*
> > * Port int-br-ex*
> > * Interface int-br-ex*
> > * type: patch*
> > * options: {peer=phy-br-ex}*
> > * Port br-int*
> > * Interface br-int*
> > * type: internal*
> > * Port patch-tun*
> > * Interface patch-tun*
> > * type: patch*
> > * options: {peer=patch-int}*
> > * ovs_version: "2.9.0"*
> >
> > How can I solve the problem?
> >
> > Thanks
> > _______________________________________________
> > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to : openstack@lists.openstack.org <mailto:openstack@lists.openstack.org> <mailto:openstack@lists.openstack.org <mailto:openstack@lists.openstack.org>>
> > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> >
> >
> > _______________________________________________
> > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to : openstack@lists.openstack.org <mailto:openstack@lists.openstack.org>
> > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> >
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org <mailto:openstack@lists.openstack.org>
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [PackStack][Neutron] erro port no present in bridge br-int [ In reply to ]

soheil.ir08 at gmail

Nov 7, 2018, 8:01 AM

Post #6 of 6 (935 views)

Permalink

Thank you for the clarification, Laszlo.

On Wed, Nov 7, 2018 at 5:39 PM Budai Laszlo <laszlo.budai@gmail.com> wrote:

> Hi,
>
> please don't misunderstand me. If you have multiple nodes, then each of
> them will have its own ``host`` setting (like, host = node1 for node1 and
> host = node2 for node2). The important thing is that both the neutron.conf
> and nova.conf to have the same ``host`` setting on one node. So if you have
> used the ``host = node1`` in neutron.conf of node1, then do the same in the
> nova.conf on the same host. And if you have ``host = node2`` in
> neutron.conf on node2, then you should have the same in the nova.conf.
>
> Kind regards,
> Laszlo
>
>
> On 11/7/18 2:52 PM, Soheil Pourbafrani wrote:
> > Thanks. In one node installation no error happened but in two node
> installation, I got the error. So I guess the answer of Laszlo is
> reasonable.
> >
> > On Wed, Nov 7, 2018 at 10:23 AM Budai Laszlo <laszlo.budai@gmail.com
> <mailto:laszlo.budai@gmail.com>> wrote:
> >
> > Hi
> >
> > we had a similar situation when the ``host`` entry in the
> neutron.conf was different than the host entry in the nova.conf on the
> compute nodes.
> > So if you're setting a ``host`` entry in one of these files, then
> make sure the other file contains the same ``host`` setting.
> >
> > see
> https://docs.openstack.org/neutron/rocky/configuration/neutron.html#DEFAULT.host
> and
> https://docs.openstack.org/nova/rocky/configuration/config.html#DEFAULT.host
> >
> > Kind regards,
> > Laszlo
> >
> > On 11/6/18 6:04 PM, Akihiro Motoki wrote:
> > > How is your [ovs] bridge_mapping in your configuration?
> > > Flat network requires a corresponding bridge_mapping entry and
> you also need to create a corresponding bridge in advance.
> > >
> > >
> > > 2018?11?6?(?) 21:31 Soheil Pourbafrani <soheil.ir08@gmail.com
> <mailto:soheil.ir08@gmail.com> <mailto:soheil.ir08@gmail.com <mailto:
> soheil.ir08@gmail.com>>>:
> > >
> > > Hi, I initilize an instance using a defined flat network and
> I got the error:
> > > port no present in bridge br-int
> > >
> > > I have a 2 node deployment (controller + network, compute).
> > >
> > > The output of the command ovs-vsctl show is
> > > *
> > > *
> > > *On the network node*
> > > d3a06f16-d727-4333-9de6-cf4ce3b0ce36
> > > Manager "ptcp:6640:127.0.0.1"
> > > is_connected: true
> > > Bridge br-ex
> > > Controller "tcp:127.0.0.1:6633 <
> http://127.0.0.1:6633> <http://127.0.0.1:6633>"
> > > is_connected: true
> > > fail_mode: secure
> > > Port br-ex
> > > Interface br-ex
> > > type: internal
> > > Port phy-br-ex
> > > Interface phy-br-ex
> > > type: patch
> > > options: {peer=int-br-ex}
> > > Port "ens33"
> > > Interface "ens33"
> > > Bridge br-int
> > > Controller "tcp:127.0.0.1:6633 <
> http://127.0.0.1:6633> <http://127.0.0.1:6633>"
> > > is_connected: true
> > > fail_mode: secure
> > > Port br-int
> > > Interface br-int
> > > type: internal
> > > Port patch-tun
> > > Interface patch-tun
> > > type: patch
> > > options: {peer=patch-int}
> > > Port int-br-ex
> > > Interface int-br-ex
> > > type: patch
> > > options: {peer=phy-br-ex}
> > > Port "tapefb98047-57"
> > > tag: 1
> > > Interface "tapefb98047-57"
> > > type: internal
> > > Port "qr-d62d0c14-51"
> > > tag: 1
> > > Interface "qr-d62d0c14-51"
> > > type: internal
> > > Port "qg-5468707b-6d"
> > > tag: 2
> > > Interface "qg-5468707b-6d"
> > > type: internal
> > > Bridge br-tun
> > > Controller "tcp:127.0.0.1:6633 <
> http://127.0.0.1:6633> <http://127.0.0.1:6633>"
> > > is_connected: true
> > > fail_mode: secure
> > > Port patch-int
> > > Interface patch-int
> > > type: patch
> > > options: {peer=patch-tun}
> > > Port br-tun
> > > Interface br-tun
> > > type: internal
> > > Port "vxlan-c0a8003d"
> > > Interface "vxlan-c0a8003d"
> > > type: vxlan
> > > options: {df_default="true", in_key=flow,
> local_ip="192.168.0.62", out_key=flow, remote_ip="192.168.0.61"}
> > > ovs_version: "2.9.0"
> > >
> > > *On the Compute node*
> > > *
> > > *
> > > *55e62867-9c88-4925-b49c-55fb74d174bd*
> > > * Manager "ptcp:6640:127.0.0.1"*
> > > * is_connected: true*
> > > * Bridge br-ex*
> > > * Controller "tcp:127.0.0.1:6633 <
> http://127.0.0.1:6633> <http://127.0.0.1:6633>"*
> > > * is_connected: true*
> > > * fail_mode: secure*
> > > * Port phy-br-ex*
> > > * Interface phy-br-ex*
> > > * type: patch*
> > > * options: {peer=int-br-ex}*
> > > * Port "enp2s0"*
> > > * Interface "enp2s0"*
> > > * Port br-ex*
> > > * Interface br-ex*
> > > * type: internal*
> > > * Bridge br-tun*
> > > * Controller "tcp:127.0.0.1:6633 <
> http://127.0.0.1:6633> <http://127.0.0.1:6633>"*
> > > * is_connected: true*
> > > * fail_mode: secure*
> > > * Port br-tun*
> > > * Interface br-tun*
> > > * type: internal*
> > > * Port "vxlan-c0a8003e"*
> > > * Interface "vxlan-c0a8003e"*
> > > * type: vxlan*
> > > * options: {df_default="true", in_key=flow,
> local_ip="192.168.0.61", out_key=flow, remote_ip="192.168.0.62"}*
> > > * Port patch-int*
> > > * Interface patch-int*
> > > * type: patch*
> > > * options: {peer=patch-tun}*
> > > * Bridge br-int*
> > > * Controller "tcp:127.0.0.1:6633 <
> http://127.0.0.1:6633> <http://127.0.0.1:6633>"*
> > > * is_connected: true*
> > > * fail_mode: secure*
> > > * Port int-br-ex*
> > > * Interface int-br-ex*
> > > * type: patch*
> > > * options: {peer=phy-br-ex}*
> > > * Port br-int*
> > > * Interface br-int*
> > > * type: internal*
> > > * Port patch-tun*
> > > * Interface patch-tun*
> > > * type: patch*
> > > * options: {peer=patch-int}*
> > > * ovs_version: "2.9.0"*
> > >
> > > How can I solve the problem?
> > >
> > > Thanks
> > > _______________________________________________
> > > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > > Post to : openstack@lists.openstack.org <mailto:
> openstack@lists.openstack.org> <mailto:openstack@lists.openstack.org
> <mailto:openstack@lists.openstack.org>>
> > > Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > >
> > >
> > > _______________________________________________
> > > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > > Post to : openstack@lists.openstack.org <mailto:
> openstack@lists.openstack.org>
> > > Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > >
> >
> >
> > _______________________________________________
> > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to : openstack@lists.openstack.org <mailto:
> openstack@lists.openstack.org>
> > Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> >
>
>