Comment 2 for bug 2028809

I think, this is actually a keystone bug that happens during upgrade to 2023.1. And while we can workaround it for CI and service users in OpenStack-Ansible, it's worth to be fixed in Keystone, as that most surely also affects users, which will be unable to login after the upgrade.

While I totally do understand background beneath the path, release note to it is completely misleading and at very least should reflect, that the upgrade is breaking and should be performed with special care in case it is impossible to revert to original behaviour