Closing out bugs created before migration to StoryBoard. Please re-open
if you are of the opinion it is still current.
** Changed in: barbican
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Closing out bugs created before migration to StoryBoard. Please re-open
if you are of the opinion it is still current.
** Changed in: barbican
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron
Glad to hear that!
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1980058
Title:
Openstack keystone LDAP inte
Public bug reported:
I have an error in keystone logs, with debug turned on:
2022-03-06 19:32:32.502 173 WARNING keystone.server.flask.application
[req-cb061f74-f48a-4c71-be47-6dda08f65c96
b731e56863e44d3e985aab70f01b054c 2722b2f6760745ab902d73de100b0ef4 -
default default] sequence item 0: expect
Public bug reported:
If a server disconnects after a pooled connection is created, it fails
withe an ldap.TIMEOUT which is Unhandled.
The ReconnectLDAPObject used by ldappool only catches the
ldap.SERVER_DOWN exception in _apply_method_s which is applied to
synchronous methods, whereas ldap.TIMEO
Public bug reported:
When the user specifies a list of LDAP servers to connect, both ldappool
and ldap try these in order. Depending on which server fails, this
causes a waiting period of the set timeout. If the first servers on the
list are down, this results in a delay of all requests.
This beh
Public bug reported:
When connecting to some LDAP servers, the LDAP library returns bytes
data instead of strings, resulting in unexpected errors, ex:
a call to
/v3/projects/x/groups/y/roles/z
results in keystone.exception.GroupNotFound: Could not find group: b'Q'.
After adding more debug logs
** Changed in: keystone
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1928650
Title:
RBAC tests in keystone-tempest-pl
Public bug reported:
LDAP Group ID may exceed the current table limit:
String length exceeded. The length of string '***' exceeds the limit of
column local_id(CHAR(64)). (HTTP 400) (Request-ID: req-bf68d05f-dc7b-
4f4b-bbb0-d2a11728de86)
>From an upstream bug[1] we had the following solution:
Th
Public bug reported:
The keystone-dsvm-functional CI tests fail with syntax errors like:
Failed to import test module: keystone_tempest_plugin.tests.rbac.v3.test_user
Traceback (most recent call last):
File
"/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/unittest2/loade
Public bug reported:
Eventlet has been deprecated since the Kilo release and is scheduled for
removal in Mitaka:
https://review.openstack.org/#/c/157495/
There was discussions about this at the summit:
https://etherpad.openstack.org/p/keystone-mitaka-summit-deprecations
** Affects: keystone
, specifically drops and alters, like in Nova:
https://github.com/openstack/nova/blob/stable/liberty/nova/tests/unit/db/test_migrations.py#L224-L225
** Affects: keystone
Importance: Undecided
Assignee: Grzegorz Grasza (xek)
Status: In Progress
** Changed in: keystone
Assignee
*** This bug is a duplicate of bug 1317804 ***
https://bugs.launchpad.net/bugs/1317804
** This bug has been marked a duplicate of bug 1317804
InstanceActionEvent traceback parameter not serializable
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
This is a duplicate of #1317804
** Changed in: nova
Assignee: Grzegorz Grasza (xek) => (unassigned)
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Ope
g handled by
the AMQP server, so message rescheduling has to be implemented in Nova
(by the application logic).
To reproduce the error, I added ipdb.set_trace() in
nova/scheduler/filter_scheduler.py:287 before returning selected_hosts
in the _schedule method.
** Affects: nova
Importance: U
15 matches
Mail list logo