Reviewed: https://review.opendev.org/c/openstack/neutron/+/855257
Committed:
https://opendev.org/openstack/neutron/commit/91f0864dc0ccf0f67be7162f011706dbc6383cb3
Submitter: "Zuul (22348)"
Branch:master
commit 91f0864dc0ccf0f67be7162f011706dbc6383cb3
Author: Rodolfo Alonso Hernandez
Date:
Putting the bug to Opinion/Wishlist as this sounds half a Nova problem
(since we set the chmod) and half a distro-specific configuration.
I'm not against any modification but we need to correctly address this
gap as a blueprint ideally.
** Changed in: nova
Status: Triaged => Opinion
**
Setting to High as we need to bump our requirements on master to prevent
older releases of oslo.concurrency.
Also, need to backport the patch into stable releases of
oslo.concurrency for Yoga.
** Also affects: nova/yoga
Importance: Undecided
Status: New
** Changed in: nova/yoga
Public bug reported:
Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=2125828
Neutron server issues over 300 messages per second during startup with
debug on:
2022-09-10 21:55:32.998 55 DEBUG networking_ovn.common.hash_ring_manager
[-] Disallow caching, nodes 0<26
I added a task for sssd here to not miss this other bug report which is
a dup of this one (#1989358). However, I am not sure how sssd is
involved on this issue. Please, provide more information and detailed
steps on how to reproduce the issue.
** Also affects: sssd (Ubuntu)
Importance:
Public bug reported:
When the port associated to a VM is deleted, no event is received by the
driver agent, so basically the LB reflects a wrong ONLINE
operating_status of the member associated to the affected VM.
As the port associated to the VM can be deleted, that case need to be
covered.
**
Reviewed:
https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/856900
Committed:
https://opendev.org/openstack/neutron-dynamic-routing/commit/1c15cd1bc594201dc5cc1dc3593ee7264c8759e2
Submitter: "Zuul (22348)"
Branch:master
commit 1c15cd1bc594201dc5cc1dc3593ee7264c8759e2
Author:
Looking a little more into it, the tests [0] actually always have a "/"
prefix in their "path_prefix", which works fine, because the "routes"
library calls "stripslashes()" in the "resource()" call and thus we
shouldn't end up with double-slashes.
[0]
8 matches
Mail list logo