yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #44264
[Bug 1532106] [NEW] while bringing up the neutron network on the openstack kilo, virtual swtich internal bridges values might be greater than 4094
Public bug reported:
On Kilo, we have the following issue.
When newtron comes up, the bridges come up with value of 4095, which is out of range of 0-4094
Due to this the instance never comes up.
Once we delete and re-create it, it comes up fine
# ovs-vsctl show
0b80f15d-ee1d-48b7-90b5-9192ab423f20
Bridge br-int
fail_mode: secure
Port "qr-e1269850-cf"
tag: 4095
Interface "qr-e1269850-cf"
type: internal
Port "qg-7a2410cc-3e"
tag: 4095
Interface "qg-7a2410cc-3e"
type: internal
Port "qr-f41e6139-7e"
tag: 4095
Interface "qr-f41e6139-7e"
type: internal
Port "tap30314ee9-be"
tag: 4095
Interface "tap30314ee9-be"
type: internal
Port br-int
Interface br-int
type: internal
Port "tap24e08b6f-be"
tag: 4095
Interface "tap24e08b6f-be"
type: internal
[root@cassini ~]# ovs-vsctl show
0b80f15d-ee1d-48b7-90b5-9192ab423f20
Bridge br-int
fail_mode: secure
Port "qr-e1269850-cf"
tag: 4095
Interface "qr-e1269850-cf"
type: internal
Port "qg-7a2410cc-3e"
tag: 4095
Interface "qg-7a2410cc-3e"
type: internal
Port "qr-f41e6139-7e"
tag: 4095
Interface "qr-f41e6139-7e"
type: internal
Port "tap30314ee9-be"
tag: 4095
Interface "tap30314ee9-be"
type: internal
Port br-int
Interface br-int
type: internal
Port "tap24e08b6f-be"
tag: 4095
Interface "tap24e08b6f-be"
type: internal
deleted the existing instance, route and external network and re-created the neutron network again. didnot fell into the same tag values again.
here the info...
[root@cassini tmp]# ovs-vsctl show
0b80f15d-ee1d-48b7-90b5-9192ab423f20
Bridge br-int
fail_mode: secure
Port "qg-9698414d-56"
tag: 5
Interface "qg-9698414d-56"
type: internal
Port patch-tun
Interface patch-tun
type: patch
options:
{peer=patch-int}
Port "qvo86f86280-d0"
tag: 4
Interface "qvo86f86280-d0"
Port "qr-b643dac3-69"
tag: 4
Interface "qr-b643dac3-69"
type: internal
Port int-br-ex
Interface int-br-ex
type: patch
options:
{peer=phy-br-ex}
Port "qvo9ceab7b9-12"
tag: 3
Interface "qvo9ceab7b9-12"
Port "qr-5210e32f-a1"
tag: 3
Interface "qr-5210e32f-a1"
type: internal
Port br-int
Interface br-int
type: internal
Port "tap4d4815bb-9f"
tag: 4
Interface "tap4d4815bb-9f"
type: internal
Port "tape03b5305-94"
tag: 3
Interface "tape03b5305-94"
type: internal
Bridge br-tun
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options:
{peer=patch-tun}
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port phy-br-ex
Interface phy-br-ex
type: patch
options:
{peer=int-br-ex}
Port "eno1"
Interface "eno1"
ovs_version: "2.3.1"
[root@cassini tmp]#
** Affects: neutron
Importance: Undecided
Status: New
** Summary changed:
- hile bringing up the neutron network on the openstack openstack virtual swtich internal bridges values might be greater than 4094
+ while bringing up the neutron network on the openstack kilo, virtual swtich internal bridges values might be greater than 4094
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1532106
Title:
while bringing up the neutron network on the openstack kilo, virtual
swtich internal bridges values might be greater than 4094
Status in neutron:
New
Bug description:
On Kilo, we have the following issue.
When newtron comes up, the bridges come up with value of 4095, which is out of range of 0-4094
Due to this the instance never comes up.
Once we delete and re-create it, it comes up fine
# ovs-vsctl show
0b80f15d-ee1d-48b7-90b5-9192ab423f20
Bridge br-int
fail_mode: secure
Port "qr-e1269850-cf"
tag: 4095
Interface "qr-e1269850-cf"
type: internal
Port "qg-7a2410cc-3e"
tag: 4095
Interface "qg-7a2410cc-3e"
type: internal
Port "qr-f41e6139-7e"
tag: 4095
Interface "qr-f41e6139-7e"
type: internal
Port "tap30314ee9-be"
tag: 4095
Interface "tap30314ee9-be"
type: internal
Port br-int
Interface br-int
type: internal
Port "tap24e08b6f-be"
tag: 4095
Interface "tap24e08b6f-be"
type: internal
[root@cassini ~]# ovs-vsctl show
0b80f15d-ee1d-48b7-90b5-9192ab423f20
Bridge br-int
fail_mode: secure
Port "qr-e1269850-cf"
tag: 4095
Interface "qr-e1269850-cf"
type: internal
Port "qg-7a2410cc-3e"
tag: 4095
Interface "qg-7a2410cc-3e"
type: internal
Port "qr-f41e6139-7e"
tag: 4095
Interface "qr-f41e6139-7e"
type: internal
Port "tap30314ee9-be"
tag: 4095
Interface "tap30314ee9-be"
type: internal
Port br-int
Interface br-int
type: internal
Port "tap24e08b6f-be"
tag: 4095
Interface "tap24e08b6f-be"
type: internal
deleted the existing instance, route and external network and re-created the neutron network again. didnot fell into the same tag values again.
here the info...
[root@cassini tmp]# ovs-vsctl show
0b80f15d-ee1d-48b7-90b5-9192ab423f20
Bridge br-int
fail_mode: secure
Port "qg-9698414d-56"
tag: 5
Interface "qg-9698414d-56"
type: internal
Port patch-tun
Interface patch-tun
type: patch
options:
{peer=patch-int}
Port "qvo86f86280-d0"
tag: 4
Interface "qvo86f86280-d0"
Port "qr-b643dac3-69"
tag: 4
Interface "qr-b643dac3-69"
type: internal
Port int-br-ex
Interface int-br-ex
type: patch
options:
{peer=phy-br-ex}
Port "qvo9ceab7b9-12"
tag: 3
Interface "qvo9ceab7b9-12"
Port "qr-5210e32f-a1"
tag: 3
Interface "qr-5210e32f-a1"
type: internal
Port br-int
Interface br-int
type: internal
Port "tap4d4815bb-9f"
tag: 4
Interface "tap4d4815bb-9f"
type: internal
Port "tape03b5305-94"
tag: 3
Interface "tape03b5305-94"
type: internal
Bridge br-tun
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options:
{peer=patch-tun}
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port phy-br-ex
Interface phy-br-ex
type: patch
options:
{peer=int-br-ex}
Port "eno1"
Interface "eno1"
ovs_version: "2.3.1"
[root@cassini tmp]#
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532106/+subscriptions
Follow ups