Public bug reported:
Greetings,
I am in the process of building a new openstack cloud and documentation
[1] states that since 2023.2 nova recommends using the new unified
limits quotas driver.
I followed the documentation and the driver itself is working but what I
am very confused about is that
Public bug reported:
Since a couple of weeks we have a problem in our production environment
when restarting our l3-agent. (Our assumption is that this might has
something to do with our upgrade to wallaby, as we never saw this
problem on prior releases before.)
The l3 agent is hosting around 300
Public bug reported:
Greetings,
While we tested a couple of disaster scenarios in our lab environment we
noticed that when we stop our rabbitmq cluster completely, the neutron
dynamic routing bgp speaker shuts down all bgp sessions to its peers.
This results in all announced floating ip's or sub
** This bug is no longer a duplicate of bug 1930414
Traffic leaked from dhcp port before vlan tag is applied
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1953165
Title:
DHCP agent f
Public bug reported:
We are running neutron victoria 17.4.1. The floating ip port forwarding
extention doesn't seem to work with external traffic.
After debugging it looks like the neutron port forwarding extention
doesn't create a necessary iptables rule responsible for setting the
0x400/0xf
Public bug reported:
Greetings,
I am seeing the following error in our galera cluster a couple of times
a day:
[ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index
`PRIMARY` table `neutron`.`provisioningblocks`
This only happens for neutron and always for the provisioningblocks tabl
Public bug reported:
Hello,
since the train release the openvswitch agent is very noisy related to
"Agent rpc_loop" logs.
I found that this was done with the following Change [1].
This results in at least >=2 messages per second per agent which can be a very
big number of logs in a production
Public bug reported:
We upgraded neutron from ussuri to victoria in our lab environment and
are seeing a strange error message that I dont really understand.
The dhcp agent is logging the following for every network: Unexpected
number of DHCP interfaces for metadata proxy, expected 1, got 3
This
Public bug reported:
When we restart the neutron-l3-agent we observe that backup routers start
accepting router advertisements. This leads to routes inside the router
namespace which expire.
e.g.:
$ ip netns exec qrouter-a5f7fb32-3e30-4e15-89f9-4ae888c2cac6 ip -6 r
x:x:1002:1::/64 dev qr-72f8512
Public bug reported:
In our openstack stein installation (neutron 14.4.2) we upgraded keepalived
from 1.3.9 to 2.2.4.
After that when restarting the neutron-l3-agent we saw that the router state of
routers with external gatways were not able to update anymore. So we ended up
with only standby r
Public bug reported:
neutron sets the no_track flag for keepalived config when keepalived is
installed in version >= 2.0.0
This breaks installations with keepalived between 2.0.0 and 2.0.2 because
keepalived implemented the no_track option in version
2.0.3.(https://github.com/acassen/keepalived
Public bug reported:
With the following report
https://bugs.launchpad.net/neutron/+bug/1814002 neutron was set to
create SNAT rules with the --random-fully flag.
This is only getting applied with iptables 1.6.2 through a version check on the
neutorn-l3-agent start.
--random-fully is already sup
12 matches
Mail list logo
