[Yahoo-eng-team] [Bug 1749574] Re: [tracking] removal and migration of pycrypto

2023-04-25 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1818649] Re: [pike] neutron-lbaasv2 with barbican error: LookupError: Container XXXXX could not be found

2023-04-25 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1980058] Re: Openstack keystone LDAP integration | openstack user list --domain domain.com | Internal server error (HTTP 500)

2022-07-18 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1965316] [NEW] No traceback on 400 "sequence item 0: expected str instance, bytes found" (TypeError)

2022-03-17 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1953627] [NEW] [ldappool] Downing one of the configured LDAP servers causes a persistent failure

2021-12-08 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1953622] [NEW] LDAP Failover behavior is unexpected and random, depending on which server on the configured list fails

2021-12-08 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1952458] [NEW] create_id_mapping method caches bytes with LDAP backend

2021-11-26 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1928650] Re: RBAC tests in keystone-tempest-plugin broke queens and rocky keystone-dsvm-functional

2021-09-29 Thread Grzegorz Grasza
** 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

[Yahoo-eng-team] [Bug 1929066] [NEW] String length exceeded local_id mapping to LDAP

2021-05-20 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1928650] [NEW] RBAC tests in keystone-tempest-plugin broke queens and rocky keystone-dsvm-functional

2021-05-17 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1517929] [NEW] Eventlet removal

2015-11-19 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1509944] [NEW] Rolling upgrades: online schema migration

2015-10-25 Thread Grzegorz Grasza
, 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

[Yahoo-eng-team] [Bug 1338403] Re: circular reference detected with exception

2015-03-11 Thread Grzegorz Grasza
*** 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,

[Yahoo-eng-team] [Bug 1338403] Re: circular reference detected with exception

2015-03-10 Thread Grzegorz Grasza
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

[Yahoo-eng-team] [Bug 1402574] [NEW] No fault-tolerance in nova-scheduler

2014-12-15 Thread Grzegorz Grasza
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