Tuesday, 2022-11-22

opendevreviewGhanshyam proposed openstack/tempest master: Add new tempest job enable the rbac scope checks and new defaults  https://review.opendev.org/c/openstack/tempest/+/61448401:19
*** tkajinam is now known as Guest216202:04
*** tkajinam is now known as Guest217403:28
*** yadnesh|away is now known as yadnesh04:03
*** pojadhav- is now known as pojadhav05:03
*** tkajinam is now known as Guest217905:36
*** pojadhav- is now known as pojadhav05:57
opendevreviewNobuhiro MIKI proposed openstack/devstack master: Skip installing and starting dstat service if it's disabled  https://review.opendev.org/c/openstack/devstack/+/86523708:02
*** yadnesh is now known as yadnesh|afk08:20
*** jpena|off is now known as jpena08:22
*** yadnesh|afk is now known as yadnesh08:51
*** jpena is now known as jpena|off08:56
*** jpena|off is now known as jpena08:57
opendevreviewMerged openstack/devstack stable/yoga: Mark centos-9-stream as n-v on stable/yoga  https://review.opendev.org/c/openstack/devstack/+/86471609:52
yadneshhey folks, can someone help me figure out a ssl issue. I see this while running telemetry tempest tests https://paste.openstack.org/show/bnvuGM6Hi0N9Fd4STSfS/10:58
kopecmartin#startmeeting qa15:00
opendevmeetMeeting started Tue Nov 22 15:00:14 2022 UTC and is due to finish in 60 minutes.  The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'qa'15:00
kopecmartin#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours15:00
kopecmartinagenda ^15:00
lpiwowaro/15:00
kopecmartin\o15:00
kopecmartinlet's quickly go through the usual 15:03
kopecmartin#topic Announcement and Action Item (Optional)15:03
kopecmartinnothing here15:03
kopecmartin#topic Antelope Priority Items progress15:03
kopecmartin#link https://etherpad.opendev.org/p/qa-antelope-priority15:03
kopecmartini've seen some progress on "Clean up deprecated lib/neutron code"15:04
kopecmartin#link https://bugs.launchpad.net/devstack/+bug/199674815:04
kopecmartinthank you slaweq for working on that 15:04
kopecmartinregarding s-rbac, there has been some progress too , the s-rbac job seems to be passing now \o/15:05
kopecmartin#link https://review.opendev.org/c/openstack/tempest/+/61448415:05
kopecmartinthanks gmann for that patch ^^15:05
kopecmartin"Use admin clients *only if* admin access needed"15:06
kopecmartinanything new here ^^ arxcruz15:06
arxcruzkopecmartin: waiting feedback from gmann 15:06
kopecmartin#link https://review.opendev.org/c/openstack/tempest/+/85237715:07
kopecmartinbut didn't we concluded that we don't need to add those parameters? 15:07
arxcruzbasically, the code that enable us to use different client is there, once i get a green light, i can start working replacing tests that calls the manager to use non-admin client15:07
arxcruzdepending on the test/requirements 15:07
kopecmartinwell, we know that situation when one test uses demo and the other one admin can't happen, it's either one or the other and then considering the amount of jobs (which is either voting on tempest patches or in general where tempest is used) we can switch only those methods to demo which will work/perform their action successfully all the time, in any case15:10
* frickler sneaks in late, reads backlog15:11
arxcruzyes, that's the idea 15:11
arxcruzthe actual patch doesn't change anything, but enable us to do that 15:11
kopecmartinso that just brings question whether we need that parameter because at the end, the method is using either admin client or demo client15:12
kopecmartini'm not sure we need to be able to that, that's all i'm saying, but the patch won't hurt 15:12
kopecmartinit will add an option to change the client, whether it's needed / or will be needed is tough to answer 15:13
kopecmartinmoving on15:14
kopecmartin#topic OpenStack Events Updates and Planning15:14
kopecmartinskipping for now15:14
kopecmartin#topic Gate Status Checks15:14
kopecmartin#link https://review.opendev.org/q/label:Review-Priority%253D%252B2+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade)15:14
kopecmartinnothing there, any urgent / gate blocking patch to review?15:14
kopecmartin#topic Bare rechecks15:15
kopecmartin#link https://etherpad.opendev.org/p/recheck-weekly-summary15:15
fricklerthere might have been https://review.opendev.org/c/openstack/devstack/+/864848 to discuss but I think we've circumvented that now15:15
* kopecmartin checking15:15
kopecmartinbtw, recheck status looks good15:16
fricklerit won't look so good next time15:17
fricklerdid an awful lot of rechecks on the devstack-plugin-ceph patch to pin to focal15:17
frickleruntil I gave up and made it non-voting15:17
kopecmartinfrickler: i saw, thank you for rechecking and getting the patches merged 15:19
kopecmartin#link 15:19
kopecmartin#link https://review.opendev.org/c/openstack/devstack/+/86484815:19
kopecmartincan it cause any harm?15:19
kopecmartinthe project is archived under openstack namespace 15:20
fricklerwell "harm" I'm not sure, it just doesn't match our policy.15:20
kopecmartini need to check that, i 15:21
fricklerbut also a new version of cursive is now on pypi and https://review.opendev.org/c/openstack/barbican/+/864226 + its dep should solve that urgent issue15:21
kopecmartini'm not very familiar with that15:21
kopecmartinoh, yeah, released yesterday 15:21
kopecmartinso it seems, barbican is no longer blocked by that patch then?15:22
fricklerstill waiting for CI but I hope so15:22
kopecmartinok, then it's ok, better to implement it according the policies 15:23
kopecmartinthanks for pointing that out 15:23
kopecmartin#topic Periodic jobs Status Checks15:23
kopecmartinstable 15:24
kopecmartin#link https://zuul.openstack.org/builds?job_name=tempest-full-yoga&job_name=tempest-full-xena&job_name=tempest-full-wallaby-py3&job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&job_name=tempest-full-zed&pipeline=periodic-stable15:24
kopecmartinmaster15:24
kopecmartin#link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic15:24
kopecmartinlooks good, although latest tempest-all timeouted 15:24
* kopecmartin checking the logs15:24
kopecmartini wonder whether that can be related to jammy, i've seen similar timeouts on cs-9 fips jobs where the reason was that certain operations just took longer on that distro15:25
kopecmartinlet's keep an eye on that 15:26
kopecmartin#topic Distros check15:27
kopecmartincs-915:27
kopecmartin#link https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=015:27
kopecmartinfedora15:27
kopecmartin#link https://zuul.openstack.org/builds?job_name=devstack-platform-fedora-latest&skip=015:27
kopecmartindebian15:27
kopecmartin#link https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bullseye&skip=015:27
kopecmartinjammy15:27
kopecmartin#link https://zuul.openstack.org/builds?job_name=devstack-platform-ubuntu-jammy&job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&skip=015:27
kopecmartinrocky15:27
kopecmartin#link https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx15:27
kopecmartinthere have been some failures, but the latest builds look good15:28
fricklercs-9 seems broken on stable branches. do you intend to look into fixing it or should we drop it instead of having it non-voting?15:28
kopecmartini'm not planning to fix that :/ 15:29
kopecmartinlast week i proposed a patch to make it n-v on yoga15:29
kopecmartinthe next logical step will be probably dropping the jobs on stable branches entirely 15:29
fricklerack15:30
kopecmartinthere isn't that much of a traffic there (on stable branches) and seeing the failure rates .. it will be better to save some resources instead 15:30
fricklerwe also need to check platform-focal job now instead of -jammy15:30
kopecmartingood point15:31
fricklerhttps://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-focal&project=openstack/devstack15:31
*** pojadhav is now known as pojadhav|afk15:32
fricklerlooking good so far15:32
kopecmartinperfect, let me update the agenda right away15:32
kopecmartin#topic Sub Teams highlights15:34
kopecmartinChanges with Review-Priority == +115:34
kopecmartin#link https://review.opendev.org/q/label:Review-Priority%253D%252B1+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade)15:34
kopecmartinnothing there15:34
kopecmartin#topic Open Discussion15:34
kopecmartinanything for the open discussion?15:35
kopecmartin#topic Bug Triage15:36
kopecmartin#link https://etherpad.openstack.org/p/qa-bug-triage-antelope15:36
kopecmartinthis relatively new bug in devstack has caught my attention 15:36
kopecmartin#link https://bugs.launchpad.net/devstack/+bug/199701715:36
kopecmartinit looks like the user set a wrong ip in HOST_IP which got me thinking, is it recommended to set that value?15:37
opendevreviewElod Illes proposed openstack/tempest master: Set back to use Bionic for Ussuri, Train and Stein  https://review.opendev.org/c/openstack/tempest/+/86530015:37
kopecmartinwell, the fact i don't set it doesn't mean it's not an option ..15:37
fricklerI think the issue is with py3.915:38
frickleruwsgi won't use that15:38
frickleron 20.04 one should use py3.815:38
kopecmartinoh, i see15:38
frickleralthough also I don't see where in the config the switched to py3.915:39
fricklerbut the logs show it being used15:39
kopecmartinpy3.9 is the default python3 on the env maybe/15:40
kopecmartin?15:40
kopecmartinthey wanted to use that version of python specifically based on the first sentence 15:40
frickleryes and we don't support that15:41
kopecmartinwill you comment there please? 15:42
fricklersure15:42
kopecmartinthen there's another new bug15:42
kopecmartin#link https://bugs.launchpad.net/devstack/+bug/199646515:43
kopecmartinseems like devstack didn't configure nova-cpu.conf correctly 15:43
kopecmartini'm not sure i've ever tried devstack on multinode setup 15:43
fricklerI wonder what this devstack-vagrant is meant to be15:43
fricklerone needs to prepare local.conf specifically for the second node15:44
fricklerour docs for that are likely outdated15:44
fricklerso the reference would be the multinode job in our .zuul.yaml15:44
fricklerI will comment and ask for more data15:45
kopecmartinthank you frickler15:45
kopecmartinthis is all from my side15:45
kopecmartinif there isn't anything else15:46
fricklerso one thing about the ceph plugin15:46
kopecmartinsure15:46
fricklerit is working with jammy now in general15:46
fricklerbut there is a failure during the tempest deployment15:46
fricklerso that would best need some tempest expert to look at15:46
kopecmartini can take a look15:47
kopecmartindid anything change?15:47
fricklerno, it never ran on jammy before. so something about python-ceph plugin dependencies confliction with tempest venv15:49
fricklerI can't find the proper zuul result right now15:49
fricklermaybe create a revert of https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/864948 and that should show the failure now that devstack default has changed15:50
kopecmartinack, i'll have a look15:51
fricklerhttps://zuul.opendev.org/t/openstack/build/8c70f6060c3141b890a7f32d6594a62c has the issue15:51
fricklernote that the "ERROR: cowardly refusing to delete `envdir` (it does not look like a virtualenv): /opt/stack/tempest/.tox/tempest" is not the original failure15:52
kopecmartinERROR: Could not install packages due to an OSError: [Errno 13] Permission denied: '/usr/local/lib/python3.10/dist-packages/future'15:52
fricklerright15:52
kopecmartinvery weird, i'll have a look15:53
kopecmartinanything else?15:53
fricklermaybe also something for clarkb who has been successful in similar issues15:53
fricklerthat's it from me then15:53
kopecmartinthank you frickler15:54
kopecmartinsee you around15:54
kopecmartin#endmeeting15:54
opendevmeetMeeting ended Tue Nov 22 15:54:48 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:54
opendevmeetMinutes:        https://meetings.opendev.org/meetings/qa/2022/qa.2022-11-22-15.00.html15:54
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/qa/2022/qa.2022-11-22-15.00.txt15:54
opendevmeetLog:            https://meetings.opendev.org/meetings/qa/2022/qa.2022-11-22-15.00.log.html15:54
frickler\o15:54
*** yadnesh is now known as yadnesh|away16:12
opendevreviewMerged openstack/devstack stable/yoga: Use proper sed separator for paths  https://review.opendev.org/c/openstack/devstack/+/86345116:36
clarkbfrickler: kopecmartin: the first thing I would try is pip intsall future in a jammy container16:38
clarkbjust to check if this is a bug with the packaging somehow on jammy16:38
clarkband work backward from there16:38
clarkboh wait its trying to install globally but this is a tox venv install16:45
clarkbtox updated on the 13th16:47
clarkbfrickler: kopecmartin: is this tox install issue only affecting ceph jobs? If so that adds even more mystery16:50
kopecmartinclarkb: thanks, i'll try it16:52
kopecmartinyeah, it's just a tox install and it affects only that one job o.O 16:52
clarkb`pip install {opts} {packages}` is set as the install command. I wonder if that is not running relative to the tox env dir anymore for some reason16:54
clarkbhowever, I would expect that to affect all tempest jobs if that was a problem16:54
* clarkb looks for a recent jammy tempest run that succeeded16:54
clarkbside note: I see nova and neutron in the gate right now and they don't have a shared tempest job (this is what broke things with the ovn changes)16:55
clarkbhttps://zuul.opendev.org/t/openstack/build/8c70f6060c3141b890a7f32d6594a62c/log/job-output.txt#20438-20556 that is the context for the failure. The last line in that block does seem to show it using global pip17:01
clarkbcompared to https://zuul.opendev.org/t/openstack/build/819962de74584064890d1e25d010f65e/log/job-output.txt#21057-21174 which pretty clearly uses the venv pip17:02
clarkbfungi: ^ have you seen this before? tox commands installing globally and not into a venv?17:13
fungiclarkb: new pip doesn't need to be installed in a venv to run, so if there's a pip entrypoint wrapper in $PATH that might do it17:16
fungihow long ago did this start?17:16
clarkbaiui this is specific to the ceph jobs on jammy which were never on jammy before and other jammy jobs don't do this17:17
fungiokay, so seems likely to be a jammy vs focal thing?17:17
clarkbI don't know if this ran on focal either17:17
clarkbit might be easiset to hold a node and interact with tox directly17:18
clarkband check things like pip in paths and so on17:18
clarkbcomparing the two tox install steps between a succeeding job on jammy and this failure they look identical though. Makes me suspect some sort of side effect earlier in the devstack run17:19
fungiwhere is the install command being set? tox.ini in what project?17:19
clarkbfungi: tempest17:19
clarkbthis is running `tox -r -e full --notest` in tempest17:19
clarkballowlist_externals = * is also set17:20
fungiany idea why that install_command is even being set there? what is it trying to accomplish?17:20
clarkbmaybe removing that line so that tempest records external commands is a good place to start17:20
clarkbfungi: I have no clue17:20
clarkbandreaf added it when they switched from tox_install.sh to using just pip17:21
clarkbI agree that seems unnecessary here since that looks like a very default string?17:22
fungii bet the proper thing to do would have been to remove it17:22
fungientirely17:22
fungirather than changing it to something that wants to be default behavior but actually isn't17:22
clarkbpython -m pip install {opts} {packages} is the default17:23
clarkbwhich is slightly different17:23
clarkbI can push up a change that drops the allowlist and install_command and set up a depends on to see if that gives us better info17:23
clarkbwait that job succeeded later?17:24
fungimy guess is that pip is no longer being installed into the venv (because pip can now manage a venv without being installed in it), and as such the execution path is falling back to a globally-installed one17:24
clarkbkopecmartin: frickler: I'm really confsused as to whether or not this is still a problem? can you clarify?17:24
fricklercurrently the problem isn't there because we pinned the devstack-plugin-ceph jobs to focal. I'll push up a partial revert and then we can hold a node there17:26
clarkbfrickler: oh let me push that and I'll make the edits to tox.ini too17:26
clarkbfrickler: the job is defined in nova?17:28
clarkboh it must be the parent that sets the nodeset17:29
opendevreviewClark Boylan proposed openstack/tempest master: Cleanup tox.ini  https://review.opendev.org/c/openstack/tempest/+/86531417:31
opendevreviewDr. Jens Harbott proposed openstack/devstack-plugin-ceph master: Revert "Temporary pin the ceph jobs nodeset to Focal"  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/86531517:32
fricklerclarkb: ^^17:32
fricklernova-multinode-ceph inherits from that17:33
*** jpena is now known as jpena|off17:33
clarkbfrickler: that should depends on 86531417:34
clarkbfrickler: or would you prefer the tempest change depend on that?17:35
fricklerclarkb: lets wait for initial results for both patches to verify the failure is still there, then I can add depends-on to the ceph patch17:37
clarkbok17:37
clarkbif this fixes things we may need to send an email calling it out. https://codesearch.opendev.org/?q=install_command&i=nope&literal=nope&files=tox.ini&excludeFiles=&repos= shows a fair bit of this going on17:41
fungiyes, i looked for the same and saw lots of cases of it. cargo cult copy-pasta17:43
fungibut longer term, i doubt we can rely on pip inside venvs with the direction the packaging ecosystem is headed. pip development is focused on being usable as a stand-alone utility outside your venv now (can even be downloaded and run directly as a zipapp)17:45
clarkbbut thats a tox problem to solve17:45
fungiso whether and what pip you've installed in a venv may not implicitly mean anything, and we might need to get a lot more specific about where we're using pip from17:45
clarkbassuming we aren't doing any crazy overrides tox has an interface they need to maintain17:45
fungiyeah, it may manifest as new tox options17:45
fungiideally backward-compatible defaults at least with some deprecation period before changing behavior17:46
fungia lot of these new behaviors are coming about because python has been notoriously hard for newcomers to use on windows, and so there's a push within the packaging community to both make things easier on windows and make all other platforms work more like windows17:49
clarkbsure, I just think that we should be able to ignore those problems as long as we are using tox (or possibly fix tox if necessary). Tox is a tool that abstracts this from us already and we shouldn't need to think too hard about how to ensure tox actually installs into a venv17:50
clarkbof course if we're overriding the commands to do this then we are on our own so we hsoul dstop doing that if we can17:50
fungiexactly17:52
*** dmellado_ is now known as dmellado18:01
*** dmellado_ is now known as dmellado18:04
fricklerclarkb: https://zuul.opendev.org/t/openstack/build/f6fb61d3ca6049b1b51311154f903122 looks different yet again18:15
fricklerI'll dep on your tempest patch anyway18:15
opendevreviewDr. Jens Harbott proposed openstack/devstack-plugin-ceph master: Revert "Temporary pin the ceph jobs nodeset to Focal"  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/86531518:16
clarkbfrickler: that looks like a failure setting up the venv. Whereas before we seemed to not even try to steup a venv18:16
clarkbinteresting18:16
clarkbfrickler:  Ithink it is trying to use python2 and not finding it18:17
clarkbwhy are we recreating the env though that seems like a bug18:19
clarkbwe just went through all this effort to instll the env with constraints and all that, then we delete it and start over ...18:20
opendevreviewDr. Jens Harbott proposed openstack/devstack master: Bump cirros version to 0.6.1  https://review.opendev.org/c/openstack/devstack/+/85977318:20
clarkbbasepython is set to python3 so thats weird18:21
clarkbya looks like devstack/lib/tempest install_tempest does all that effort to intsal lthe venv. Then configure_tempest says "just kidding" and deletes it all18:22
clarkband does it again.18:22
clarkbcan probbaly speed up tempest jobs by not doing that18:22
clarkbwe also install tempest globally. I think we end up installing tempest 3 times18:27
clarkband only one of those installs happens in install_tempest18:28
clarkblooks like it is still failing to find python, this is the weirdest thing. its like something is mangling path and that leads to pip and python problmes19:01
clarkbI'm not familiar enough with tempest and dvestack at this point or that plugin to have a hunch as to what might be doing it19:01
clarkbbut maybe simplifying things like my change and also perhaps not installing tempest 3 times each run would help reduce the places it could break19:01
clarkbbut also lets hold a node. I can work on getting that setup after my meeting19:14
clarkbfrickler: I put a hold in place and rechecked your change20:04
clarkbfrickler: fungi: interestingly it seems that the venv being created by tox isn't a valid venv21:17
clarkband that is what causes it to try and use global `python` which doens't exist on the node21:18
clarkbfrickler: fungi: ok the issue is that the virtualenv installed by `virtualenv` is creating fooenv/local/bin not fooenv/bin21:23
clarkbwe had this before and it had to do with things I don't recall but I've got a pip branch somewhere with details21:23
clarkbhrm no the pip branch I'm thinking of is for a different problem21:24
clarkbupgrading virtualenv fixes it in the held node I think https://github.com/pypa/virtualenv/pull/2415 was the fix. However, python3-distutils is alredy installed on the node when it is broken and they indicated that would fix it so I dunno21:32
clarkbI also cannot reproduce this in a jammy container21:36
clarkbI've mangaed to reproduce it finally. It breaks when latest setuptools is installed which vendors distutils and virtualenv finds that22:53
clarkbthe devstack plugin for ceph pip install -U --force PasteDeploy which for some reason also upgrades setuptools from the distro version to latest22:53
clarkbthis is why other jobs are fine, they use distro setuptools22:53
clarkbI believe this happens because pastedeploy==2.1.1 has an install_requires on setuptools22:58
clarkbalso the pip --force flag seems to be undocumented but definitely changes the behavior here22:58
clarkbfungi: ^ do you know what pip instal --force is meant to do? I'm having a hard time finding it in the source and git history23:02
clarkbbut it definitely seems to force setuptools to be upgraded here. Dropping it only updates PasteDeploy23:02
clarkb--ignore-installed and --force-reinstall produce similar behavior so I guess its something along those lines23:04
fungiclarkb: yeah, i was about to ask if it was like --force-reinstall23:07
fungiclarkb: --upgrade-strategy=eager might have a similar effect23:08
fungiused to be pip's default behavior when specifying -U but now it does only-if-needed upgrades by default23:09
opendevreviewClark Boylan proposed openstack/devstack-plugin-ceph master: Revert "Temporary pin the ceph jobs nodeset to Focal"  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/86531523:10
clarkbfungi: ^ I've worked around it by using --no-deps23:10
clarkbI think that should work23:10
fungiand yes, with python 3.12 completely removing distutils, setuptools is getting more aggressive about using its own copy23:10
clarkbwell in this case its any import distutils finding the setuptools copy23:11
clarkbno setuptools involved23:11
clarkbI hvae to say after spending most of a day debugging this people who say python environments are too complicated are correct23:11
clarkbthe job is running tempest but that is unhappy23:47

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!