Wednesday, 2021-09-01

*** queria is now known as Guest595202:30
*** arxcruz is now known as arxcruz|training08:16
*** sshnaidm|afk is now known as sshnaidm09:08
*** Guest5533 is now known as marlinc10:01
*** rlandy is now known as rlandy|rover11:38
mlozafrickler: hi, did you get a chance to reproduce the bug?15:53
fricklermloza: I tried, but it does seem to work just fine for me. what versions are you using for osc and openstack? I tested with a fresh devstack on master16:22
mlozafrickler: stable/ussuri17:16
mlozadid you add reader role to the user at system or domain level ?17:17
fricklermloza: system. nova doesn't support domain scope, see
*** tavasti__ is now known as tavasti18:19
marlincHey, I'm running into a strange issue where sometimes when creating a trust Keystone returns an error saying the role doesn't exist even though it does. It's extra strange because when specifying the rule in the trust I actually use the name of the role not the id, but in the error message it says (with the correct id) that that id cannot be found18:36
marlincas a role:
mlozafrickler: I see. Does it matter if the user that I assign reader role at system level is from LDAP ?19:36
mlozaI haven't tested local acount 19:36
*** rlandy|rover is now known as rlandy|rover|mtg20:29
*** rlandy|rover|mtg is now known as rlandy|rover21:19
*** rlandy|rover is now known as rlandy|rover|bbl22:23
*** queria is now known as Guest601523:02
*** queria is now known as Guest601723:30

Generated by 2.17.2 by Marius Gedminas - find it at!