Public bug reported:
OpenStack 2024.1
Neutron 25.0.0.0b2.dev189 (grabbed from master branch)
OVN 24.03.3
TLDR: VIP port does not come up when its virtual-parents are trunk sub-
ports
Lets say I have two instances in an internal network which form some kind of
high availability cluster using a
** Also affects: ovn-bgp-agent
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2080492
Title:
[OVN] VIP port does not come up when its virtual-
Public bug reported:
Description
===
We got the mtu error as below on the source compute node, when live
migrating an instance which have two interface from both vxlan tenant
network and vlan provider networks.
"Target network card MTU 0 does not match source 1450:
libvirt.libvirtError:
Public bug reported:
With Dalmatian release (2024.2) Keystone has finally added support for domain
managers:
https://review.opendev.org/c/openstack/keystone/+/924132
This type of users have a Domain scoped tokens and have a `manager` role
assigned to the domain.
With these privileges they are a
Public bug reported:
Steps to reproduce:
1. Upgrade keystone from zed to bobcat
2. Run keystone-manage db_sync --check
Expected:
Expand: 29e87d24a316 (head: 11c3b243b4cb)
Contract: e25ffa003242 (head: c88cdce8f248)
Return status 2
Observed:
Expand: 29e87d24a316 (head: 29e87d24a316)
Contract:
Public bug reported:
Downstream we had an interesting but report
https://bugzilla.redhat.com/show_bug.cgi?id=2311875
Instances created after liberty but before victoria
that request a numa topology but do not have CPU pinning
cannot be started on post victoria nova.
as part of the
https://specs
6 matches
Mail list logo
