15:00:46 <e0ne> #startmeeting horizon
15:00:48 <openstack> Meeting started Wed Feb  3 15:00:46 2021 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:51 <openstack> The meeting name has been set to 'horizon'
15:01:24 <vishalmanchanda> hi all.
15:02:12 <e0ne> hi
15:03:21 <e0ne> vishalmanchanda: let's wait few minutes to let people join us
15:03:55 <jopdorp> o/
15:04:10 <amotoki> o/
15:06:22 <e0ne> let's start
15:07:28 <e0ne> I don't have any announcements today, so let's start with topics in our etherpad
15:07:35 <e0ne> #link https://etherpad.opendev.org/p/horizon-release-priorities
15:08:19 <e0ne> #topic integration tests failure in master branch
15:08:44 <e0ne> it's line #71 in the etherpad
15:09:13 <amotoki> I added what I checked here.
15:09:31 <amotoki> It looks like the cause is xstatic-jquery-migrate upgrade to 3.
15:10:00 <e0ne> :(
15:10:04 <e0ne> rdopiera: are you around?
15:10:16 <e0ne> amotoki: did you check with previous version?
15:10:27 <e0ne> AFAIK, manila-ui is affected too
15:10:38 <amotoki> yes, see https://review.opendev.org/c/openstack/horizon/+/773824 and its Depends-On
15:10:40 <rdopiera> e0ne: sorry, I'm here, I have another meeting at the same time
15:11:12 <amotoki> The symptom we see with the new jquery-migrate is all tests fail.
15:12:18 <rdopiera> ugh, looking at it
15:12:54 <e0ne> amotoki: I see. I'm OK to cap requirements until we figure out what is going
15:13:17 <e0ne> I would like to see working and voting integration tests job
15:13:18 <amotoki> e0ne: yeah, it is the short-time workaround.
15:13:21 <rdopiera> it's possible that there are delays or some other interaction with it
15:13:50 <e0ne> I need to deploy a fresh env to reproduce the issue on my local env
15:13:50 <rdopiera> I never got the integration tests to work on my machine, so I did not test it
15:13:57 <e0ne> :(
15:14:19 <rdopiera> I will make an ubuntu vm and try there, I guess
15:15:04 <amotoki> looking at https://0eb2ef4e3dc4a9f8b9d1-e733834b89fbed1f5903272250bb3953.ssl.cf2.rackcdn.com/770870/3/gate/horizon-integration-tests/c86af1e/tox/test_reports/TestAdminGroupTypes.test_group_type_create_delete/video.mp4, we failed to open the target page. Only the login succeeds.
15:15:23 <amotoki> I checked about 10 test results but the behaviors are same.
15:15:59 <amotoki> unfortunately I have no more time to investigate the detail with the new xstatic-jquery-migrate. can someone investigate it?
15:16:19 <e0ne> I'll do it
15:16:20 <vishalmanchanda> there are many post on google acc. to that it's an geckodriver issue with Firefox browser but I am not sure.
15:16:28 <vishalmanchanda> https://stackoverflow.com/questions/59026421/python-selenium-unable-to-get-browser-console-logs
15:16:37 <vishalmanchanda> https://github.com/mozilla/geckodriver/issues/1698
15:16:53 <amotoki> vishalmanchanda: is it related to the full failure this time?
15:17:19 <vishalmanchanda> amotoki: error logs are same.
15:17:27 <amotoki> even without the failure this time, our integration tests fail too often. it might be related to this.
15:17:31 <e0ne> we don't have browser logs in a job
15:17:43 <amotoki> vishalmanchanda: which error log do you mean?
15:18:53 <vishalmanchanda> amotoki: error logs in post https://stackoverflow.com/questions/59026421/python-selenium-unable-to-get-browser-console-logs
15:19:23 <vishalmanchanda> same as our failed integration-job logs
15:19:27 <e0ne> I don't think it's related to the issue
15:19:39 <amotoki> vishalmanchanda: it is not new. we see this error even before we switch a browser.
15:19:56 <amotoki> buuuuuut, we first need to fix the complete failure of integration tests
15:20:18 <vishalmanchanda> amotoki: hmm
15:20:18 <amotoki> vishalmanchanda: your issue souds a next step to make the integration tests more stable.
15:20:38 <amotoki> vishalmanchanda: why do you think it is related to this failure?
15:21:11 <amotoki> what I see is ALL tests fail now. previously we see a few tests fail.
15:21:23 <amotoki> we usually see the error you mention.
15:21:31 <e0ne> amotoki:+1
15:22:02 <vishalmanchanda> amotoki: but we never see "HTTP method not allowed" error before
15:22:41 <amotoki> for example, https://zuul.opendev.org/t/openstack/build/c1bc885b5fe44136846eba8a97180dd2/log/job-output.txt#26274
15:22:52 <amotoki> this is a result of my DNM patch
15:23:07 <amotoki> we see only ONE error of "HTTP method not allowed"
15:23:30 <amotoki> but it does not happen for all tests.
15:23:52 <vishalmanchanda> hmm
15:23:52 <amotoki> i thikn ALL vs a couple of tests is very different symptom
15:24:25 <rdopiera> it could be that the jquery-migrade exacerbates the problem that exists already
15:24:34 <rdopiera> but it could be completely different too
15:25:02 <vishalmanchanda> e0ne: Could you try to run integration-test with latest xstatic-jquery-migrate but with another browser maybe chromium this time.
15:25:25 <amotoki> the evidence of my statement is found here. https://zuul.opendev.org/t/openstack/builds?job_name=horizon-integration-tests&branch=master&pipeline=periodic
15:25:31 <vishalmanchanda> e0ne: I tried it locally but not succeeded.
15:25:36 <e0ne> vishalmanchanda: I'll do it tonight. I need to setup a new devstack
15:25:51 <amotoki> Compere test failures after Jan 28 and before Jan 27. Failure symptoms are different.
15:26:04 <vishalmanchanda> amotoki: yeah.
15:28:40 <vishalmanchanda> What's are final call on this topic?
15:29:09 <vishalmanchanda> https://review.opendev.org/c/openstack/horizon/+/773824 merges these patches as of now to unblock CI.
15:29:38 <amotoki> I don't think we are in the stage to decide the final call but the short-term workaround would be to block the new xstatic-jquery-migrate.
15:29:57 <e0ne> amotoki: +2
15:29:58 <amotoki> and then we can investigate two things (1) failure with the new xstatic-jquery-migrate
15:30:23 <amotoki> and (2) failure reason in our integration tests we contineu to see since before this time failure.
15:30:27 <amotoki> thougtht?
15:30:40 <vishalmanchanda> amotoki: agreed.
15:30:40 <rdopiera> sounds like a plan
15:30:51 <rdopiera> and sorrry for causing this
15:31:09 <amotoki> rdopiera: no problem. everyone did not check it :(
15:31:40 <rdopiera> I will try to get the integration tests working on my machine one way or another
15:32:07 <amotoki> vishalmanchanda: you struggeled to run the integartion tests before. do you have tips you can share with rdopiera?
15:33:16 <vishalmanchanda> rdopiera: Make sure your credentials are right in 'openstack_dashboard/test/integration_tests/config.py' file.
15:33:47 <vishalmanchanda> rdopiera: ohh sorry wrong file reference.
15:34:00 <rdopiera> I know which file you mean
15:34:14 <vishalmanchanda> openstack_dashboard/test/integration_tests/horizon.conf
15:34:18 <rdopiera> yeah
15:35:18 <vishalmanchanda> rdopiera: please share your error logs once you try to run maybe I can help.
15:35:23 <rdopiera> I have problems with the gecko driver itself, but hopefully that will work if I try it on ubuntu
15:36:19 <e0ne> rdopiera: I used ubuntu VM without any issues
15:37:48 <rdopiera> I'm running fedora, because it's a work laptop
15:39:46 <amotoki> apart from how to run the integration tests, a different I see is that the current failure happens when moving to a page from /projects/ (just afterr login). Previously we usually succeeds to move a next page like /volumes/ from /projects/ and failures happen after that.
15:40:03 <amotoki> I confirmed this by checking video.mp4 under tox/test_reports.
15:40:40 <amotoki> we always see "HTTP method not allowed" vishalmanchanda mentioned in both cases but when it happens seems different.
15:41:19 <amotoki> that's all I see.
15:42:19 <amotoki> so, who takes care the next action?
15:42:58 <e0ne> I'll try to reproduce it locally
15:43:22 <e0ne> and I'll let you know tomorrow about progress
15:43:44 <amotoki> hopefully one of you can handle a requirements change.
15:44:22 <amotoki> I cannot do it soon tomorrow.
15:45:01 <e0ne> amotoki: do you mean this one https://review.opendev.org/c/openstack/requirements/+/773823?
15:45:08 <rdopiera> I'm looking into it as well, if I can get my setup to work
15:46:07 <amotoki> e0ne: yes, I proposed it just for testing. we can update it.
15:46:55 <rdopiera> I just had one of the integration tests pass, so I think I'm making progress
15:47:27 <e0ne> rdopiera: :)
15:48:07 <amotoki> we spend most of our time on this topic.
15:48:29 <amotoki> we see another topic in On-demand agenda. is it time to move?
15:49:13 <e0ne> let's move to the next topic
15:49:27 <e0ne> #topic nodejs 10 version going to EOL by April end
15:49:44 <e0ne> #link https://nodejs.org/en/about/releases/
15:49:44 <vishalmanchanda> I have added this topic.
15:50:46 <e0ne> vishalmanchanda: could you  please provide more details?
15:51:35 <vishalmanchanda> I think we should test horizon with next LTS version(v12 or v14) because v10 which are using now going to EOL by 2021-04-30.
15:51:53 <amotoki> what kind of things do we need to do? when we switched nodejs from 4 to 10, it was just to setup nodejs10 job and update related jobs.
15:52:47 <e0ne> vishalmanchanda: how much will it affect us?
15:53:20 <vishalmanchanda> e0ne: I have not  tested npm job with any latest version as of now
15:53:36 <vishalmanchanda> will try to do it this week
15:53:53 <e0ne> vishalmanchanda: ok. let's move this topic to the next week
15:54:00 <amotoki> zuul/zuul-jobs/zuul.d/js-jobs.yaml already defines node env with version 14.
15:54:07 <amotoki> so we can try it. that's all.
15:54:09 <e0ne> vishalmanchanda: you can test it locally
15:54:21 <vishalmanchanda> amotoki: cool
15:55:43 <amotoki> that would be a topic on not wallaby but xena
15:55:57 <vishalmanchanda> yeah
15:56:42 <amotoki> i have two updates I am working on before closing the meeting.
15:56:42 <vishalmanchanda> amotoki: there is a patch purpose for Xena runtime env for nodejs version that' why I added this topic.
15:56:55 <amotoki> about Merge tempest-horizon into tempest and Chinese locale rename
15:57:02 <vishalmanchanda> https://review.opendev.org/c/openstack/governance/+/770860/2/reference/runtimes/xena.rst#34
15:57:20 <amotoki> you can check my updates in  "Notices " section the etherpad
15:58:23 <amotoki> vishalmanchanda: we cannot use old version so we need to use a supported version. I think it is not more than that. can we do more?
15:58:45 <e0ne> amotoki: thanks
15:59:46 <vishalmanchanda> amotoki: no.
16:00:07 <e0ne> we're out of time. thanks everybody for your contributions
16:00:10 <e0ne> see you next week
16:00:20 <e0ne> #endmeeting