Public bug reported:
The gateway neutron-ovn-invalid-chassis previously used for the CR-LRP
gateway_chassis has been removed in [1]. At this way, the logical router
port event received at creation is considered as a new port attached to
the router to a tenant network, adding the LB to that LS,
Public bug reported:
Description
===
Attaching a pre-existing port with port security_disabled on a network
with port_security enabled which does not have any subnets fails. The
port_security setting on the network should not be relevant in this
case. It's only a default value for newly
Public bug reported:
``OVNL3RouterPlugin._port_update`` [1] is called AFTER_UPDATE the router
port is created (for example, when a subnet is attached to a router).
This event is guaranteed to be called after the Neutron DB has the
resource (port) in the database. However, as the code highlights
Reviewed: https://review.opendev.org/c/openstack/keystone/+/908760
Committed:
https://opendev.org/openstack/keystone/commit/6096457d7400c280f9ee07a9c5b9760e74ecee4b
Submitter: "Zuul (22348)"
Branch:master
commit 6096457d7400c280f9ee07a9c5b9760e74ecee4b
Author: Tobias Urdin
Date: Mon Feb
>From all the changes that have merged this seems to be complete, will
close.
** 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.
Seems this fix is released, will close.
** 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/1666779
Title:
Expose neutron
This seems to be complete, will close bug. Please re-open if I'm wrong.
** 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.
I am going to close this as it's been a number of years and the original
patch was abandoned. If someone wants to pick it up please re-open.
** Changed in: neutron
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
The documents have been updated many times over the past 6+ years, I'm
going to close this as they are much better now. If there is something
specific please open a new bug.
** Changed in: neutron
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member
As this has never been worked on am going to close. If anyone wants to
pick it up please re-open.
** Changed in: neutron
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
>From comment in the change that was linked above:
"BakedQuery is a legacy extension that no longer does too much beyond
what SQLAlchemy 1.4 does in most cases automatically. new development w/
BakedQuery is a non-starter, this is a legacy module we would eventually
remove."
For that reason I'm
Public bug reported:
Description
===
libvirt CPU power management does not support live migration
Steps to reproduce
==
1. Turn on libvirt CPU power management
2. Boot an instance with hw:cpu_policy=dedicated
3. Live migrate the instance
Expected result
===
Public bug reported:
Description
===
libvirt CPU power management does not handle `isolate` emulator thread policy.
Steps to reproduce
==
1. Turn on libvirt CPU power management
2. Boot an instance with hw:cpu_policy=dedicated and
hw:emulator_threads_policy=isolate
13 matches
Mail list logo
