15:00:33 <vishalmanchanda> #startmeeting horizon
15:00:33 <opendevmeet> Meeting started Wed Sep 21 15:00:33 2022 UTC and is due to finish in 60 minutes.  The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:33 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:33 <opendevmeet> The meeting name has been set to 'horizon'
15:00:50 <tmazur> o/
15:01:02 <opendevreview> Merged openstack/horizon stable/zed: Update TOX_CONSTRAINTS_FILE for stable/zed  https://review.opendev.org/c/openstack/horizon/+/858692
15:01:06 <opendevreview> Merged openstack/horizon master: Update master for stable/zed  https://review.opendev.org/c/openstack/horizon/+/858693
15:01:22 <ganso> o/
15:01:27 <rdopiera> o/
15:01:30 <vishalmanchanda> Hello everyone
15:02:25 <vishalmanchanda> ok let's start the meeting
15:02:53 <vishalmanchanda> Agenda of meeting can be found here https://etherpad.opendev.org/p/horizon-release-priorities#L39
15:03:02 <vishalmanchanda> #topic Notices
15:03:19 <vishalmanchanda> few announcements from my side
15:03:31 <vishalmanchanda> As you may noticed, a stable/zed branch is created for horizon.
15:03:39 <vishalmanchanda> https://review.opendev.org/c/openstack/horizon/+/858691
15:03:58 <vishalmanchanda> Now master branch is Antelope(2023.1)
15:04:51 <vishalmanchanda> Now if any bug you wants to fix in zed cycle you have to backport it to stable/zed branch.
15:05:25 <vishalmanchanda> moving to next announcement
15:05:51 <vishalmanchanda> TC & PTL election result is out.
15:05:59 <vishalmanchanda> For more info, please refer https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030541.html
15:06:46 <vishalmanchanda> that's all announcements from my side. if anyone have any announcement to make, please go ahead.
15:07:50 <vishalmanchanda> moving to next topic
15:08:08 <vishalmanchanda> #topic On-Demand Agenda
15:08:44 <vishalmanchanda> there is a request for patch review https://review.opendev.org/c/openstack/horizon/+/856308
15:08:51 <ganso> that's ^ me =)
15:08:54 <vishalmanchanda> ganso: that's you
15:09:11 <ganso> so, I wanted to discuss it as it might be a controversial bug
15:09:12 <vishalmanchanda> ganso: honestly I am not sure about the bug
15:09:19 <ganso> and/or a controversial fix
15:09:28 <ganso> vishalmanchanda: yup I suspect that might be the case =)
15:09:48 <vishalmanchanda> Just before the meeting I try to resproduce it but it's work fine for me.
15:10:14 <ganso> vishalmanchanda: did you try as a cloud adminsitrator or domain adminsitrator?
15:10:18 <vishalmanchanda> I am unable to reproduce this bug https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1827120
15:10:42 <vishalmanchanda> cloud adminsitrator
15:11:03 <vishalmanchanda> I have also done some changes in my keystone.conf file
15:11:23 <vishalmanchanda> [resource]
15:11:23 <vishalmanchanda> admin_project_domain_name = admin_domain
15:11:23 <vishalmanchanda> admin_project_name = admin
15:12:00 <ganso> vishalmanchanda: so, I don't remember all the details, but I remember I wasn't able to reproduce it early on as well, but then upon adjusting the roles I was able to
15:12:12 <ganso> and I reproduced it on Yoga, so I'm not sure about master
15:12:22 <ganso> but, the main use case here is not as a cloud admin
15:12:26 <ganso> because the cloud admin has an easy workaround
15:12:34 <ganso> that I wasn't able to find for domain admins
15:12:46 <ganso> and looking at the code, the bug is very clear
15:13:28 <ganso> because every time there is a domain_token, that overrides  the user_token, and it sends that token to keystone when doing authentication
15:13:41 <ganso> keystone, using that token, will not include a project_id context
15:14:07 <ganso> so it is about which token you send to keystone, as the token contain the context, it doesn't seem to me as a keystone fault
15:14:46 <ganso> the trick to reproduce the issue, is that the user HAS to have a domain admin role
15:15:03 <ganso> if it is just a user that is member of a project, it always works. When the user becomes the domain admin, it enables the bug
15:16:17 <ganso> so, I'd love to know a workaround for the domain admin user, if there is any. The only workaround I've found is to inject  the missing project_id in the database, in the app credential entry, until the fix lands
15:16:32 <ganso> I suspect it might be possible there is a workaround by playing with all knobs
15:16:41 <ganso> but I haven't found any
15:17:52 <ganso> vishalmanchanda: so if you are unable to reproduce it as a non-cloud user with a domain admin role, I'd love to hear more details
15:19:06 <vishalmanchanda> ganso: ok thanks for your input. I will definately try to reproduce it.
15:19:09 <ganso> but the key point I intended to discuss here in the meeting was, assuming that the bug could be reproduced, is whether the bug is actually intended behavior, this is the "controversial" aspect I was referring to
15:19:31 <ganso> because I am not sure about how things are expected to work. Maybe it was intended behavior
15:19:31 <vishalmanchanda> ganso: I still have few doubts, will get back to you once I try again.
15:19:52 <ganso> vishalmanchanda: thank you
15:19:58 <vishalmanchanda> ganso: I am also not sure.
15:20:22 <vishalmanchanda> amotoki: maybe amotoki rdopiera knows more.
15:24:19 <vishalmanchanda> ganso: thanks for working on this. I will try to understand this bug and get back to you.
15:24:29 <ganso> vishalmanchanda: thanks!
15:25:09 <vishalmanchanda> ganso: if it's working with CLI then it should definately works with horizon.
15:25:34 <ganso> vishalmanchanda: yes, with the CLI it is fine, even if the user has the domain admin role
15:26:35 <vishalmanchanda> ganso: So you have enabled Multi domain in your env. to reproduce it?
15:30:00 <vishalmanchanda> Do we have any other topics to discuss?
15:32:43 <vishalmanchanda> If nothing more to discuss, Let's end this meeting.
15:32:50 <vishalmanchanda> Thanks evryone for joining!
15:33:04 <vishalmanchanda> #endmeeting