Public bug reported:
I have en environment, with 5 neutron-server(W version), 5 ovn(21.03.1)
When adding an interface to the router, the state of the interface is sometimes
down,
and it will not become up after a long time. Restarting the neutron server can
become up.
I check logical_switch_port by "ovn-nbctl list logical_switch_port <port-id>",
the status
of lsp is up, and the traffic can be forwarded normally.
This should only be a neutron save state problem.
In the past, when creating vm, the ports have been unable to be up, and the
reason has not
been found. The phenomenon is the same as that of the router interface.
In the process of adding a routing interface, I wrote a script to listen to
logical_switch_port
change, I found: before lsp becomes up=true, lsp's up=[], which is not
up=[false], not
matchd LogicalSwitchPortUpdateUpEvent. I don't know why ovn's notification
events are
sometimes different, but I think it should be repaired here in neutron
** Affects: neutron
Importance: Undecided
Status: New
** Description changed:
I have en environment, with 5 neutron-server(W version), 5 ovn(21.03.1)
- When adding an interface to the router, the state of the interface is
sometimes down,
+ When adding an interface to the router, the state of the interface is
sometimes down,
and it will not become up after a long time. Restarting the neutron server
can become up.
- I check logical_switch_port by "ovn-nbctl list logical_switch_port
<port-id>", the status
+ I check logical_switch_port by "ovn-nbctl list logical_switch_port
<port-id>", the status
of lsp is up, and the traffic can be forwarded normally.
This should only be a neutron save state problem.
- In the past, when creating vm, the ports have been unable to be up, and the
reason has not
+ In the past, when creating vm, the ports have been unable to be up, and the
reason has not
been found. The phenomenon is the same as that of the router interface.
- In the process of adding a routing interface, I wrote a script to listen to
logical_switch_port
- change, I found: before lsp becomes up=true, lsp's up=[], which is not
up=[false], not matchd
- LogicalSwitchPortUpdateUpEvent. I don't know why ovn's notification events
are sometimes different,
- but I think it should be repaired here in neutron
+ In the process of adding a routing interface, I wrote a script to listen to
logical_switch_port
+ change, I found: before lsp becomes up=true, lsp's up=[], which is not
up=[false], not
+ matchd LogicalSwitchPortUpdateUpEvent. I don't know why ovn's notification
events are
+ sometimes different, but I think it should be repaired here in neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1983530
Title:
[ovn]router_interface port probability cannot be up
Status in neutron:
New
Bug description:
I have en environment, with 5 neutron-server(W version), 5
ovn(21.03.1)
When adding an interface to the router, the state of the interface is
sometimes down,
and it will not become up after a long time. Restarting the neutron server
can become up.
I check logical_switch_port by "ovn-nbctl list logical_switch_port
<port-id>", the status
of lsp is up, and the traffic can be forwarded normally.
This should only be a neutron save state problem.
In the past, when creating vm, the ports have been unable to be up, and the
reason has not
been found. The phenomenon is the same as that of the router interface.
In the process of adding a routing interface, I wrote a script to listen to
logical_switch_port
change, I found: before lsp becomes up=true, lsp's up=[], which is not
up=[false], not
matchd LogicalSwitchPortUpdateUpEvent. I don't know why ovn's notification
events are
sometimes different, but I think it should be repaired here in neutron
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1983530/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
