Thursday, 2023-07-27

noonedeadpunkhey folks. I believe we see a regression in keystone during upgrade to 2023.1 in CI, when passwords are longer then 54 symbols using bcrypt. I assume that is related to https://review.opendev.org/c/openstack/keystone/+/82859506:46
noonedeadpunkSo basically, after upgrade working previously passwords stop working06:46
noonedeadpunkand we get 401 on operations that were working like 30mins ago in the same pipeline jsut before the upgrade06:50
noonedeadpunkWhile I do get that such verification is fair, since it's bcrypt limitation, though I am not getting why it cause regressions during upgrade from Zed06:51
noonedeadpunkANd not sure how I can deal with that from operator perspective, as I really have no idea what our users could set as a password06:51
noonedeadpunkd34dh0r53 knikolla will ping you as you might have some good ideas :)06:52
noonedeadpunkgood example of that is here: https://zuul.opendev.org/t/openstack/build/693d274e0b5341f38e84107a8741eb86/log/job-output.txt#24388 where on nova verification it fails with "Placement service credentials do not work" 06:54
noonedeadpunkWhile on line 16130 it was passing _before_ upgrade has happened06:54
noonedeadpunkso password got invalidated after upgrade, which kinda sucks06:55
noonedeadpunkWe got a bug report https://bugs.launchpad.net/openstack-ansible/+bug/2028809 and I'm inclined it to mark as this affects keystone06:57
noonedeadpunkAs while it's kinda our fault, that we generate passwords longer then 54 symbols, that catched this nasty thing that does affect users06:57
*** tobias-urdin-pto is now known as tobias-urdin07:34

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