Public bug reported:
High level description:
After a reboot the network controller, neutron linuxbridge agent does not
create all network links correctly of the tenant networks.
This is behavior is not only on system where the node is rebooted also on nodes
that are longer running. And not possible to respawn new networks/dhcp
agents/l3 routers
* Pre-conditions:
I was able to reproduce the issue by deleting the vxlan interface of a tenant
network and then reboot the node.
After the reboot the interface the namespace for example for the dhcp namespace
- does not get attached to the bridge
- the bridge does not get created
- the vxlan interace does not get created
* Step-by-step reproduction steps
1. remove the vxlan interface from the brigde
brctl delif brq8c9de29c-e2 vxlan-149
2. delete in vxlan interface
ip link del dev vxlan-149
3. reboot
reboot
* Expected output:
Expected behavior is that after the reboot vxlan get recreated and that we see
the following:
interface ns-41a5e6e6-b3@if105 (inside the dhcp namespace) ->
tap41a5e6e6-b3@if2 (outside the namespace) -> brq8c9de29c-e2 -> vxlan-149
* Actual output:
after the reboot:
* interface ns-41a5e6e6-b3@if105 exists
* interface tap41a5e6e6-b3@if2 exists
* interface tap41a5e6e6-b3@if2 not attached to any bridge
* bridge brq8c9de29c-e2 does not exists
* vxlan interface does not exists
* Version:
** Openstack Ussuri
** Installed with Openstack ansible version 21.2.6
** neutron version 7.1.1
** Ubuntu Bionic
Perceived severity: The cluster is degrated state where is only possible to new
networks, dhcp agent and l3 router on one of the three network nodes.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: linuxbridge neutron
** Tags added: linu neurton
** Tags removed: linu neurton
** Tags added: linux
** Tags removed: linux
** Tags added: linuxbridge neutron
** Description changed:
High level description:
After a reboot the network controller, neutron linuxbridge agent does not
create all network links correctly of the tenant networks.
This is behavior is not only on system where the node is rebooted also on
nodes that are longer running. And not possible to respawn new networks/dhcp
agents/l3 routers
-
* Pre-conditions:
I was able to reproduce the issue by deleting the vxlan interface of a tenant
network and then reboot the node.
- After the reboot the interface the namespace for example for the dhcp
namespace
+ After the reboot the interface the namespace for example for the dhcp
namespace
- does not get attached to the bridge
- the bridge does not get created
- the vxlan interace does not get created
* Step-by-step reproduction steps
1. remove the vxlan interface from the brigde
- brctl delif brq8c9de29c-e2 vxlan-149
+ brctl delif brq8c9de29c-e2 vxlan-149
2. delete in vxlan interface
- ip link del dev vxlan-149
+ ip link del dev vxlan-149
3. reboot
- reboot
+ reboot
* Expected output:
Expected behavior is that after the reboot vxlan get recreated and that we
see the following:
interface ns-41a5e6e6-b3@if105 (inside the dhcp namespace) ->
tap41a5e6e6-b3@if2 (outside the namespace) -> brq8c9de29c-e2 -> vxlan-149
* Actual output:
after the reboot:
- * interface ns-41a5e6e6-b3@if105 exists
- * interface tap41a5e6e6-b3@if2 exists
- * interface tap41a5e6e6-b3@if2 not attached to any bridge
- * bridge brq8c9de29c-e2 does not exists
- * vxlan interface does not exists
+ * interface ns-41a5e6e6-b3@if105 exists
+ * interface tap41a5e6e6-b3@if2 exists
+ * interface tap41a5e6e6-b3@if2 not attached to any bridge
+ * bridge brq8c9de29c-e2 does not exists
+ * vxlan interface does not exists
* Version:
- ** Openstack Ussuri
- ** Installed with Openstack ansible version 21.2.6
- ** neutron version 7.1.1
- ** Ubuntu Bionic
+ ** Openstack Ussuri
+ ** Installed with Openstack ansible version 21.2.6
+ ** neutron version 7.1.1
+ ** Ubuntu Bionic
- Perceived severity: The cluster is degrated state where is only possible to
new
+ Perceived severity: The cluster is degrated state where is only possible to
new
networks, dhcp agent and l3 router on one of the three network nodes.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1952611
Title:
Neurton linuxbridge agent does not create VXLAN interface
Status in neutron:
New
Bug description:
High level description:
After a reboot the network controller, neutron linuxbridge agent does not
create all network links correctly of the tenant networks.
This is behavior is not only on system where the node is rebooted also on
nodes that are longer running. And not possible to respawn new networks/dhcp
agents/l3 routers
* Pre-conditions:
I was able to reproduce the issue by deleting the vxlan interface of a tenant
network and then reboot the node.
After the reboot the interface the namespace for example for the dhcp
namespace
- does not get attached to the bridge
- the bridge does not get created
- the vxlan interace does not get created
* Step-by-step reproduction steps
1. remove the vxlan interface from the brigde
brctl delif brq8c9de29c-e2 vxlan-149
2. delete in vxlan interface
ip link del dev vxlan-149
3. reboot
reboot
* Expected output:
Expected behavior is that after the reboot vxlan get recreated and that we
see the following:
interface ns-41a5e6e6-b3@if105 (inside the dhcp namespace) ->
tap41a5e6e6-b3@if2 (outside the namespace) -> brq8c9de29c-e2 -> vxlan-149
* Actual output:
after the reboot:
* interface ns-41a5e6e6-b3@if105 exists
* interface tap41a5e6e6-b3@if2 exists
* interface tap41a5e6e6-b3@if2 not attached to any bridge
* bridge brq8c9de29c-e2 does not exists
* vxlan interface does not exists
* Version:
** Openstack Ussuri
** Installed with Openstack ansible version 21.2.6
** neutron version 7.1.1
** Ubuntu Bionic
Perceived severity: The cluster is degrated state where is only possible to
new
networks, dhcp agent and l3 router on one of the three network nodes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1952611/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
