15:00:15 #startmeeting horizon 15:00:15 Meeting started Wed Jun 14 15:00:15 2023 UTC and is due to finish in 60 minutes. The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:15 The meeting name has been set to 'horizon' 15:01:14 o/ 15:01:30 o/ 15:01:31 Hello everyone 15:02:25 agenda of meeting can be found here https://etherpad.opendev.org/p/horizon-release-priorities#L32 15:02:31 let's start the meeting 15:02:37 #topic Notices 15:02:53 hi 15:03:37 This week is OpenInfra Summit + PTG going on but no-one of us going there. 15:04:20 I hope maybe next time we may travel for the PTG. 15:04:32 moving to next announcement 15:05:06 I have purposed a patch to move horizon stable/stein branch to EOL and send a mail on open-discuss and no objection is raised so far. 15:05:23 https://review.opendev.org/c/openstack/releases/+/885109 15:06:08 we are good to move forward with moving horizon stable/stein branch to EOL. 15:06:24 moving to next announcement 15:07:25 I pushed a patch to Pin XStatic-Font-Awesome to <4.8.0.0 in openstack/requirements and it's also got merged. 15:07:31 https://review.opendev.org/c/openstack/requirements/+/885159 15:09:48 Now I guess next thing is to identify and pin more Xstatic packages which are not horizon deliverables https://governance.openstack.org/tc/reference/projects/horizon.html to avoid any failures. 15:11:11 that's all announcements from my side for this week. 15:11:21 moving to next topic 15:11:31 I am not sure pinning more xstatic packages makes sense or not 15:12:25 I think it does make sense for the data-only ones 15:12:44 rdopiera: +1 15:13:50 is there no issue from rhosp perspective? perhaps rhosp and other rh deliverables do not include moinmoin who is the other major user of xstatic, so it would not be a problem 15:14:59 I don't know the situation around ubuntu and debian 15:16:45 I think we can watch if automatic update of any Xstatic package break horizon and then decide if we need those update or not. 15:17:45 yeah, we don't care about the moin moin wiki 15:18:16 oen question: what is the actual problem around xstatic-font-awesome and is it documented somewhere? (launchpad bug or anywhere is okay) 15:18:17 I didn't think about the situation of distros that need it 15:18:45 the problem is that when it was upgraded, the names/paths were changed for no apparent reason 15:20:00 I see. it sounds a good reason to block the new version, but perhaps we need to make it searchable/findable anywhere. 15:21:09 how about filing a horizon bug and add a comment on it to g-r? 15:21:41 https://zuul.opendev.org/t/openstack/build/e5dd3c8fced64cf2b95ecc2d50bc0827/log/job-output.txt#20091 15:22:15 the files used to be named fontawesome.css and now are named font-awesome.css 15:22:16 amotoki: ok, I will open a open bug for that in horizon launchpad for future reference. 15:24:49 There is not much update on jQuery migrate this week. 15:25:17 Only one patch is not merged yet https://review.opendev.org/q/topic:update-jquery+status:open 15:25:52 I was waiting for https://review.opendev.org/c/openstack/horizon/+/883953 to get merged to fix the CI. 15:26:14 but horizon-integration jobs fails too much. 15:26:36 we looked into those failures a bit 15:26:51 it seems it's failing when it clicks on the user menu to go to the settings page 15:26:57 somehow the menu never opens 15:27:29 here you can find summary of failed tests https://etherpad.opendev.org/p/random-failed-horizon-integration-tests 15:27:33 I suspect a javascript error, but firefox doesn't let us retreve the javascript error logs, so we don't know 15:28:08 for different tests it's the same problem apparently: that user menu dropdown doesn't open 15:28:17 we looked at several different failures, they all fail trying to click that menu 15:31:12 of course we can't reproduce it locally 15:31:39 hmm, what we should do now? 15:32:34 I'm looking for a workarund to get js errors somehow, by using an error callback 15:33:33 we could also switch to chromium... 15:33:56 ok, we can try that. 15:34:36 I am just wondering if these issue happening due to my jQuery update patches. 15:34:40 https://review.opendev.org/q/topic:update-jquery 15:34:55 it is possible, but it's hard to tell without seeing the error 15:35:22 you can try and see if you can reproduce it locally 15:36:24 unfortunately I am unable to run integration job locally on my env. but I will try again today. 15:37:03 manual reproducer would work too, anything that lets you see the error 15:37:21 I am going to try on my other env too 15:37:23 it's random, so there must be some kind of a race condition perhaps 15:37:30 ok, yeah. 15:38:27 If we look at this data https://etherpad.opendev.org/p/random-failed-horizon-integration-tests 15:39:10 "test_instances_pagination" integration test fails too much 15:39:49 We've checked test_logout failure, and it's the same issue with that menu 15:40:08 tmazur: yes 15:40:16 But yeah, it seems pagination triggers it way more often 15:41:37 should we avoid recheck now on https://review.opendev.org/c/openstack/horizon/+/883953 15:42:14 until we found the fix or some workaround? 15:43:00 looking at the commits, the jquery changes are the last patches that merged 15:46:22 I can revert last 2-3 patches or maybe more of jquery update in a single patch and see. 15:52:46 I think I got dropped 15:53:34 vishalmanchanda: nobody commented since you wrote 15:54:49 let's try our best to fix the horizon integration job asap. 15:55:38 yeah 15:56:25 moving to next topic 15:56:35 #topic open-discussion 15:56:47 Does anyone have any other topic to discuss? 16:01:00 Thanks everyone for joining. 16:01:10 let's fix the CI asap. 16:01:16 see you next week. 16:01:27 #endmeeting