Public bug reported:
Neutron (Xena) is happy to accept equivalent rules with overlapping
remote CIDR prefix as long as the notation is different, e.g. 10.0.0.0/8
and 10.0.0.1/8.
However, OVN is smarter, normalizes the prefix and figures out that they
both are 10.0.0.0/8.
This does not have any f
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/194
Title:
[ovn] neutron_ovn_db_sync_util crashes (ACL already exists
Public bug reported:
neutron-ovn-db-sync-util hangs in certain scenarios while running
sync_routers_and_rports.
Specifically, it seems to be hanging on self.l3_plugin.get_routers(ctx)
-> model_query.get_collection(...) of get_routers(...) in neutron.db.l3_db.py
-> get_collection(...) in neutron_l
Public bug reported:
Doing fresh install on Xena, running neutron-ovn-db-sync-util in repair
mode crashes (on a basically empty Neutron database).
Based on our testing using Ubuntu Cloud Archive, this error did not
occur inneutron-common/focal-updates,now
2:18.1.1+git2021091315.0fa97ecceb-0ubuntu
Public bug reported:
See: https://review.opendev.org/c/openstack/neutron/+/714716
Upon starting neutron-server with OVN mechanism driver, it crashes when
trying to read cfg.CONF.ml2_type_geneve.max_header_size.
Traceback (most recent call last):
File "/usr/bin/neutron-server", line 10, in
It looks like it's not an issue in nova nor cinder.
If you take the XML that nova is using (if you turn debug log, you'll see it in
nova-compute.log):
025aa02e-9348-4740-94dc-c862ac0e
And try to attach it to the domain manually:
# virsh attach-device
Public bug reported:
Running `keystone-manage mapping_engine` (with parameters) is broken:
2017-03-30 16:09:11.982 13513 CRITICAL keystone [-] TypeError: __init__() takes
exactly 3 arguments (2 given)
2017-03-30 16:09:11.982 13513 ERROR keystone Traceback (most recent call last):
2017-03-30 16:0
I am reopening, because it persists on pure Juno stable installation
(2014.2.2).
** Changed in: horizon
Status: Invalid => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.laun
Public bug reported:
In the Access & Security view, regular users (Member, not admin role) do
not see the buttons to disassociate or delete Floating IP addresses.
This can be temporarily fixed by changing policy.json files for neutron that
are fed to Horizon:
< "update_floatingip": "rule:adm
Public bug reported:
When regular user (without admin role) tries to associate a Floating IP with an
instance, the list of ports is empty.
When the user has admin role, the problem doesn't appear. I believe the regular
user does not have access to something that is needed to ensure "reachability
Public bug reported:
Nova Version: master (and probably previous)
Tested with euca2ools 3.0.2-1 on Debian
Line numbers based on commit 48e8f992f46862cb4f50fe0cc9b77a3017e7bb23 in master
for nova, commit 8557e4756e8a326579df826076478d98ca634345 in master for
keystone.
EC2 protocol requires "Sign
Public bug reported:
These headers:
x-image-meta-container_format: bare
x-image-meta-disk_format: qcow2
x-image-meta-is_public: True
are not valid HTTP headers - these should not contain underscores.
HTTP proxies such as nginx (which are used e.g. for SSL termination)
strip these headers by defa
12 matches
Mail list logo
