Wednesday, 2025-05-07

opendevreviewTakashi Kajinami proposed openstack/python-keystoneclient master: Replace deprecated datetime.datetime.utcnow  https://review.opendev.org/c/openstack/python-keystoneclient/+/94898205:55
opendevreviewTakashi Kajinami proposed openstack/python-keystoneclient master: Replace deprecated datetime.datetime.utcnow  https://review.opendev.org/c/openstack/python-keystoneclient/+/94898205:57
opendevreviewTakashi Kajinami proposed openstack/python-keystoneclient master: Replace deprecated datetime.datetime.utcnow  https://review.opendev.org/c/openstack/python-keystoneclient/+/94898207:54
opendevreviewArtem Goncharov proposed openstack/keystone master: Start building openapi doc  https://review.opendev.org/c/openstack/keystone/+/94818509:39
opendevreviewStephen Finucane proposed openstack/keystoneauth master: pre-commit: Bump versions  https://review.opendev.org/c/openstack/keystoneauth/+/94598011:28
opendevreviewStephen Finucane proposed openstack/keystoneauth master: Drop support for Python 3.9  https://review.opendev.org/c/openstack/keystoneauth/+/94900811:28
opendevreviewStephen Finucane proposed openstack/keystoneauth master: Bump Python version used for linters to 3.9  https://review.opendev.org/c/openstack/keystoneauth/+/94900911:28
opendevreviewStephen Finucane proposed openstack/keystoneauth master: Bump minimum Python version used for linters  https://review.opendev.org/c/openstack/keystoneauth/+/94901011:28
opendevreviewArtem Goncharov proposed openstack/keystone master: Start building openapi doc  https://review.opendev.org/c/openstack/keystone/+/94818511:30
opendevreviewStephen Finucane proposed openstack/keystoneauth master: Bump Python version used for linters to 3.10  https://review.opendev.org/c/openstack/keystoneauth/+/94901011:33
d34dh0r53#startmeeting keystone15:02
opendevmeetMeeting started Wed May  7 15:02:07 2025 UTC and is due to finish in 60 minutes.  The chair is d34dh0r53. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
opendevmeetThe meeting name has been set to 'keystone'15:02
d34dh0r53Reminder: This meeting takes place under the OpenInfra Foundation Code of Conduct15:02
d34dh0r53#link https://openinfra.dev/legal/code-of-conduct15:02
d34dh0r53#topic roll call15:02
d34dh0r53admiyo, bbobrov, crisloma, d34dh0r53, dpar, dstanek, hrybacki, lbragstad, lwanderley, kmalloc, rodrigods, samueldmq, ruan_he, wxy, sonuk, vishakha, Ajay, rafaelwe, xek, gmann, zaitcev, reqa, dmendiza[m], dmendiza, mharley, jph, gtema, cardoe, deydra15:03
gtemao/15:03
dmendiza[m]🙋‍♂️15:03
d34dh0r53o/15:03
d34dh0r53#topic review past meeting work items15:04
d34dh0r53#link https://meetings.opendev.org/meetings/keystone/2025/keystone.2025-04-23-15.02.html15:04
d34dh0r53no action items from the last meeting15:04
d34dh0r53#topic liaison updates15:04
d34dh0r53nothing from releases15:05
d34dh0r53anything from VMT?15:05
gtemanot that I would know about15:05
d34dh0r53ack, thanks15:06
d34dh0r53moving on then15:07
d34dh0r53#topic specification OAuth 2.0 (hiromu)15:07
d34dh0r53#link https://review.opendev.org/q/topic:bp%252Foauth2-client-credentials-ext15:07
d34dh0r53#link https://review.opendev.org/q/topic:bp%252Fenhance-oauth2-interoperability15:07
d34dh0r53External OAuth 2.0 Specification15:07
d34dh0r53#link https://review.opendev.org/c/openstack/keystone-specs/+/861554 (merged)15:07
d34dh0r53OAuth 2.0 Implementation15:07
d34dh0r53#link https://review.opendev.org/q/topic:bp%252Fsupport-oauth2-mtls (merged)15:07
d34dh0r53OAuth 2.0 Documentation15:07
d34dh0r53#link https://review.opendev.org/c/openstack/keystone/+/838108 (merged)15:07
d34dh0r53#link https://review.opendev.org/c/openstack/keystoneauth/+/838104 (merged)15:07
d34dh0r53no updates15:08
d34dh0r53#link https://review.opendev.org/c/openstack/keystonemiddleware/+/899911 is waiting on dependencies in Barbican and Tacker to merge and then it's good to go.15:09
d34dh0r53The others just need rebases once that is merged.15:09
d34dh0r53next up15:09
d34dh0r53#topic specification Secure RBAC (dmendiza[m])15:09
d34dh0r53#link https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html#z-release-timeline_15:09
d34dh0r532024.1 Release Timeline15:10
d34dh0r53Update oslo.policy in keystone to enforce_new_defaults=True15:10
d34dh0r53Update oslo.policy in keystone to enforce_scope=True15:10
d34dh0r53any updates dmendiza ?15:10
dmendiza[m]Negative, just getting back from PTO15:11
d34dh0r53Ack, thanks, and welcome back :)15:11
d34dh0r53#topic specification OpenAPI support (gtema)15:11
d34dh0r53#link https://review.opendev.org/q/topic:%22openapi%22+project:openstack/keystone15:11
gtemasince now the os-api-ref and openstackdocstheme requirements are raised I have updated openapi build change15:12
gtema#link https://review.opendev.org/c/openstack/keystone/+/94818515:12
gtemafrom my pov it can go this way, so feel free to review15:12
gtemaand then we can start discussing what and where is missing. It will also help landing jsonschema changes since we can see the schemas easier15:13
d34dh0r53cool15:14
gtemanothing else on that from me this week15:14
d34dh0r53Looks good to me15:15
d34dh0r53Thanks gtema 15:15
d34dh0r53That does it for specs15:15
d34dh0r53#topic open discussion15:15
d34dh0r53I don't really have anything15:15
gtemaanyone has ideas or proposals wrt modifying DB schema for the new federation support?15:16
gtemait is explicitly about the federated_user table linking to the idp_id and protocol_id while in the new implementation those both go away and instead there are few other attrs15:16
gtemacurrently there is not_null for both of them and therefore I can't use the table without easing those constraints15:17
gtemaI do not want to introduce new table (federated2_user) - it is going to be insane15:18
gtemamy idea was to drop the not_null constraint so that I can leave those fields empty while adding new fields and new FK constraints15:18
d34dh0r53I'm okay with dropping the constraint15:20
gtemaI think the code is good enough to handle those properly15:20
d34dh0r53Yeah, and if needed we can add some additional checks in the code15:21
gtemaok, I will then proceed this way15:21
d34dh0r53sounds good15:21
gtemathks15:22
d34dh0r53cool, any other open discussion topics?15:24
gtemanot from me15:24
d34dh0r53moving on15:25
d34dh0r53#topic bug review15:25
d34dh0r53#link https://bugs.launchpad.net/keystone/?orderby=-id&start=015:25
d34dh0r53Looks like three new bugs in keystone15:25
d34dh0r53#link https://bugs.launchpad.net/keystone/+bug/211008415:25
d34dh0r53#link https://bugs.launchpad.net/keystone/+bug/210998915:26
d34dh0r53#link https://bugs.launchpad.net/keystone/+bug/210969315:26
gtemauhm15:28
gtemaproject creation is another misuse of admin at domain scope15:28
d34dh0r53yeah, the first two look like they may be just configuration issues15:32
d34dh0r53moving on15:32
d34dh0r53#link https://bugs.launchpad.net/python-keystoneclient/?orderby=-id&start=015:33
d34dh0r53no new bugs for python-keystoneclient15:33
d34dh0r53#link https://bugs.launchpad.net/keystoneauth/+bugs?orderby=-id&start=015:33
d34dh0r53keystoneauth is good as well15:33
d34dh0r53#link https://bugs.launchpad.net/keystonemiddleware/+bugs?orderby=-id&start=015:33
d34dh0r53no new bugs in keystonemiddleware15:33
d34dh0r53#link https://bugs.launchpad.net/pycadf/+bugs?orderby=-id&start=015:33
d34dh0r53pycadf is good15:34
d34dh0r53#link https://bugs.launchpad.net/ldappool/+bugs?orderby=-id&start=015:34
d34dh0r53so is ldappool15:34
d34dh0r53#topic conclusion15:34
d34dh0r53Thanks folks!15:34
gtemathanks Dave Wilde (d34dh0r53) 15:34
d34dh0r53👍️15:35
d34dh0r53#endmeeting15:35
opendevmeetMeeting ended Wed May  7 15:35:11 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:35
opendevmeetMinutes:        https://meetings.opendev.org/meetings/keystone/2025/keystone.2025-05-07-15.02.html15:35
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/keystone/2025/keystone.2025-05-07-15.02.txt15:35
opendevmeetLog:            https://meetings.opendev.org/meetings/keystone/2025/keystone.2025-05-07-15.02.log.html15:35
WiniciusAllan[m]hi keystone team o/15:35
WiniciusAllan[m]Are you who maintains the identity part of terraform provider?15:36
gtemanope, terraform is not maintained by anybody from the OpenStack itself15:37
WiniciusAllan[m]oh, I see15:37
WiniciusAllan[m]may I share my pain? =)15:38
gtemasure, but not sure whether we would be able to help. wrt TF provider you should directly open issue in github repo of it15:39
WiniciusAllan[m]no problem, maybe you can help with a workaround 15:39
WiniciusAllan[m]I've configured LDAP driver for my environment and set the user_enabled_attribute to a boolean value in the LDAP schema15:41
WiniciusAllan[m]when I list all users from the configured domain, the "enabled" column shows "None" at one time and "True" at the other15:41
WiniciusAllan[m]this inconsistency is causing an error when requesting an user from API, because its receiving "enabled=true" as a filter15:42
WiniciusAllan[m]in practice, this does not affect the users, because the LDAP filter get the correct boolean status15:44
WiniciusAllan[m]this inconsistency it is a misconfiguration or an already reported bug?15:44
WiniciusAllan[m]s/it/could/, s/is/be/15:45
gtemawhat is the relation to TF?15:45
WiniciusAllan[m]terraform uses gophercloud and it passes Enabled=true as default 15:46
WiniciusAllan[m]I changed the code and set this value to nil (so do not append it in request params) and it works as expected15:46
gtemaI am confused that you use TF but say "when I list all users"15:47
WiniciusAllan[m]oh, sorry. When I list all users using the CLI15:48
WiniciusAllan[m]I did that to check their status and I ended up seeing that inconsistencyt15:49
gtema"" the "enabled" column shows "None" at one time and "True" at the other "" - what does that mean? For different users or different invocations?15:51
WiniciusAllan[m]for different invocations, the same users show different values across executions15:52
gtemaand you see that the request to the API is the same, right?15:52
WiniciusAllan[m]yeah. I can send the output for clarification15:54
gtemain such case I think there may be ldap synchronization issue. Otherwise I can't explain flaky results15:55
gtemamaybe you can debug the ldap queries from keystone to eventually spot the issue15:56
WiniciusAllan[m]$ openstack user list --domain LSD -c Name -c Enabled --long | grep winicius... (full message at <https://matrix.org/oftc/media/v1/media/download/AUsz3MiiEr-8yXV1E49kxG_meKsaPaapfeZ2AZFcHjjyuT1-88JEoSMmakkiVKSplnzl2cPsjbV4Vp734KhsgtZCeW84-a7wAG1hdHJpeC5vcmcvcFZkeEdoUlNZekVDUmFnWGFHekhaV2lU>)15:56
WiniciusAllan[m]gtema: I'll do that and see if I get something suspicious15:57
WiniciusAllan[m]thanks for the attention!15:58
gtemayou can also use --debug param to the cli to also see the raw data to exclude possibility of bug in the cli15:58
gtemaand maybe you can focus on the single user (user show) not to deal with huge data sets15:59
WiniciusAllan[m]what I may search with --debug? the raw response?16:00
gtemathe raw json that comes from the keystone api16:00
WiniciusAllan[m]another thing that I notice is that keystone logs show that the domain does not exists 16:00
WiniciusAllan[m]"domain LSD not exists"16:00
WiniciusAllan[m]even if the CLI return the users from that domain16:00
gtemaand check whether the "enabled" parameter is there is flaky as well16:01
WiniciusAllan[m]ack16:01
*** __ministry is now known as Guest1536016:06
WiniciusAllan[m]gtema: I was comparing the logs in the two cases that I mentioned. When the output from CLI returns Enable=True the logs show these entries17:25
WiniciusAllan[m]https://pastebin.com/baLekdQJ17:25
WiniciusAllan[m]the difference is in attrs for search_s17:26

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!