Friday, 2022-02-04

*** ysandeep|out is now known as ysandeep01:14
*** dviroel|afk is now known as dviroel01:16
*** dviroel is now known as dviroel|out01:22
*** ysandeep is now known as ysandeep|afk01:40
*** akahat is now known as akahat|rover05:29
*** ysandeep|afk is now known as ysandeep07:09
*** amoralej|off is now known as amoralej07:28
*** akahat|rover is now known as akahat|lunch08:30
*** ysandeep is now known as ysandeep|lunch08:36
*** akahat|lunch is now known as akahat|rover09:22
*** ysandeep|lunch is now known as ysandeep10:04
ralonsohhi folks, is gerrit today a bit slow? or is just me that I dind't pay my Interner connection?10:16
*** dviroel|out is now known as dviroel|ruck10:46
fricklerralonsoh: I don't see any issue. might have been only temporarily or really a local problem?10:55
ralonsohfrickler, is just that any time I try to open a review, it takes several seconds10:56
ralonsohthis could be something local, for sure10:56
fricklerralonsoh: might be your v4 is broken with fallback to v6 or the other way round?10:58
ralonsohI'll check that10:58
*** rlandy|out is now known as rlandy|ruck11:10
*** ysandeep is now known as ysandeep|mtg11:17
elodilleshi, i think the following patch introduced some new gate / periodic job failures for really old branches (queens and pike): https://review.opendev.org/c/zuul/zuul-jobs/+/82758811:36
elodillessome example: https://zuul.opendev.org/t/openstack/builds?job_name=build-openstack-sphinx-docs&project=openstack%2Fnova&project=openstack%2Fneutron&project=openstack%2Fironic&branch=stable%2Fqueens&skip=011:38
*** ysandeep|mtg is now known as ysandeep12:02
fricklerelodilles: can't we finally retire these more than 2 years after py2 went eol?12:26
elodillesfrickler: well, some projects already EOL'd their old branches, but some still accept patches12:32
elodillesi wouldn't say that the amount of patches are high though12:32
elodillesso probably yes, that is one option. but on the other hand i don't think this is the best approach to do it12:35
fricklerwell projects can still accept patches, but testing them with python2 no longer seems reasonable. actually I see that those jobs use ubuntu-xenial, we should have dropped supporting that image even before dropping centos812:35
frickleroh, wait, that's 18.04, not 16.04, so it would have one more year12:37
elodilles18.04 is bionic12:38
elodillesso if we think the same way then ussuri, train and stein would have 1 year at most12:41
elodillessurely there are vendors / operators who would use those for some more years12:43
fricklersurely then those vendors / operators will soon show up here and work on keeping the CI alive12:58
elodillesgood point :)13:01
sean-k-mooneyelodilles: by they regarding pip13:20
sean-k-mooneyusing pip form ubuntu is broken13:20
sean-k-mooney*by the way13:20
sean-k-mooneyit will istall the packages and devstack can stack but ubuntu's pip cannot uninstall them13:21
sean-k-mooneyor upgrade them13:21
sean-k-mooneyit complains that they are not in env /usr13:21
sean-k-mooneyso the recent chagne to devstack while it work it only works once13:22
sean-k-mooneyon your local dev system you will need to revert to pip form pypi13:22
fungithat sounds like another new pip behavior13:31
elodillessean-k-mooney: oh, thanks for the info. i haven't noticed that yet13:32
fungielodilles: any reason those old branches can't use the available python3 to build their documentation, even if they still do other testing with python2?13:32
fungipreserving the ability to use python2 to build documentation seems like it's not all that important13:33
sean-k-mooneyfungi: it appearntly has been a thing in ubuntu since 18.04 or possibel earlier based on stack overflow13:33
sean-k-mooneywe are only seeing that now with devstack since we stopt usign pip from pypi13:34
sean-k-mooneyfungi: i was also seeing issue with pbr13:34
fungisean-k-mooney: yes, earlier versions of pip also refused to uninstall things which were installed by distro packages13:34
sean-k-mooneyi could not get pip install -e to work properly13:34
sean-k-mooneynova could not find the version wehn it started up13:34
fungia minimal reproducer would probably help us to have a clearer discussion about the behavior, or change thereof13:35
sean-k-mooneyi can try doing it in a docker container13:35
sean-k-mooneyand see if that repoduces13:35
fungiwell, more like the minimal number of steps required to create the problem, without one of the steps being "install and run devstack"13:35
*** dasm|off is now known as dasm13:36
fungilike "install this package, then uninstall it, observe an error" that sort of ting13:36
sean-k-mooneyfungi: its just git clone nova, sudo pip install nova, sudo pip uninstall nova13:36
sean-k-mooneythe devstack connection is devstack uses sudo13:37
fungiahh, okay, so pip is refusing to uninstall a package it has installed. and which version of pip specifically?13:37
fungi22.x or something earlier?13:37
sean-k-mooneythis was on my other laptop let me grab it13:37
sean-k-mooneyill see if i can repodcue in a doceker file too brb13:37
fungiand is it specifically only if you `sudo pip install -e ...` and then try to `sudo pip uninstall ...`?13:38
sean-k-mooneyyou do not need -e13:38
sean-k-mooneybut i think its only with sudo13:38
fungiokay, you mentioned editable mode, so i was curious if it only happened with editable installs13:38
sean-k-mooneyoh so my normal workflow13:38
sean-k-mooneyis to have a second copy of the repos in /opt/repos13:39
fungiyeah, so for a while pip has refused to uninstall things which were installed by distro packages using distutils instead of setuptools13:39
sean-k-mooneyand i sudo pip install -e . and restart the service  13:39
sean-k-mooneywhen i want to work on a change13:39
fungibut pip refusing to uninstall something it installed is a new one on me13:39
sean-k-mooneyit was python3-pip version 20.0.2-ubuntu1.613:41
sean-k-mooneyi did a clean install form iso yesterday in this vm and just insalled the latest pip but i saw this on a could image last week too13:41
fungiokay, so not a behavior related to a new pip release13:42
fungipip --version reports 20.0.2?13:42
fungiworth noting that the actual installed pip version may not be the same as what the distro package manager thinks is there if devstack did a `sudo pip install --upgrade pip` or similar13:42
sean-k-mooneyill have to reinstall it but ill check13:43
sean-k-mooneyso ya its reporting as 20.0.2 not 22*13:46
sean-k-mooney22* from pypi could uninstall things but pbr was kind of borked let me see if i can create a docker file that repoduces the issue and ill past bin it13:47
elodillesfungi: i'll try to debug the py35 based doc gen if i'll get there. i guess that should be doable13:49
*** ysandeep is now known as ysandeep|mtg13:59
sean-k-mooneyfungi: odd in the contianer it works as i expect14:03
sean-k-mooneyi wonder if i am some how getting a mix14:03
sean-k-mooneylike coudl this be related to safe path and python -m pip vs pip14:03
sean-k-mooneywith sudo14:03
sean-k-mooneyin the contaienr i also dont get the warnign about you shoudl not use pip as sudo14:06
sean-k-mooneyso im not convince its the same14:06
sean-k-mooneyfungi: if i figure out what caused it on my laptop ill let you konw i think it might be the setuptoos dist utis flag different https://paste.opendev.org/show/812526/14:23
sean-k-mooneythe isntall is how devestack would do it14:23
sean-k-mooneybtu it seams to just work when i use podman to buidl it so dont really know what to say at this pint14:23
fungiyeah, i'll try to keep an eye out for the problem14:24
sean-k-mooneyi have hit it on 2 vms in the last week 1 ubuntu 20.04 cloud the other ubuntu 20.04 arm form iso14:24
fungithanks for the heads up14:24
sean-k-mooneymaybe i should go back to running devstack in a contaienr :)14:25
sean-k-mooneycause appently contaier fix everythign these days :P14:25
fungimagic container pixie dust14:26
sean-k-mooneyin other new devstack/openstack appear to work runing in a 6G ubuntu vm on a mac book air14:27
sean-k-mooneythe slightly concerning things is it installes faster then on my work laptop or home server14:28
sean-k-mooneythere are a few things i need to go fix however. like not using x86 cirros on arm hosts14:29
sean-k-mooneyyou can overidee that in the local.conf but it would nice if it just worked out of the box14:29
fricklersean-k-mooney: seems the effort to produce a CI job for that have stalled, but maybe you want to take a look https://review.opendev.org/q/topic:story%252F200719614:33
sean-k-mooneyif i keep using the mac ya perhaps14:39
sean-k-mooneyi really dont like osx but i have been puting of replacing my dell xps 13 for 2 years and picked up the cheapest referbished m1 model just to see if i could live with osx14:41
sean-k-mooneyi have to say the hardware is nice but really wish the linux support was a little more advanced14:41
sean-k-mooneyfrickler: for context on a clean vm i was getting a sub 5 minute devstack install14:42
sean-k-mooneytotal runtime 244sec speedup of 1.5 ish from parallel14:43
fricklerwow, that's impressive. but I assume that that includes have local repo copies and also pre-cached wheels available?14:43
sean-k-mooneynope14:44
sean-k-mooneypulled directly form the internet over wifi14:44
sean-k-mooneywell actlly 244 was a second stack14:44
sean-k-mooneythe first one with the conles was a little longer14:44
sean-k-mooneybut not much14:44
sean-k-mooneyim not a fan of the lack of repairablity or 0 upgrade path but integrating everyting on an soc has some advandagtes for sure14:46
*** ysandeep|mtg is now known as ysandeep|out14:53
opendevreviewMerged openstack/project-config master: Add cirros/cirros project  https://review.opendev.org/c/openstack/project-config/+/82771914:59
*** dviroel|ruck is now known as dviroel|ruck|lunch15:17
*** akahat|rover is now known as akahat|dinner15:45
*** markzijdemans_ is now known as markzijdemans15:46
*** dviroel|ruck|lunch is now known as dviroel|ruck16:22
*** rlandy|ruck is now known as rlandy|ruck|brb16:30
clarkbralonsoh: frickler: we do notice appreciable slowdowns after a gerrit restart as cache data is flushed. There is work upstream to change the cache implementation to make it more persistent to alleviate that. But other than that situation I am not aware of anything that should be slowing down gerrit currently. We didn't restart recently either16:44
ralonsohclarkb, thanks for the info!16:45
ralonsohin this is better now. This morning, just for me, everything was working fine except gerrit16:45
fungigerrit's webui relies on lots of rest api calls, which if sufficiently serialized could be very sensitive to round-trip latency16:48
*** rlandy|ruck|brb is now known as rlandy|ruck16:54
*** amoralej is now known as amoralej|off17:41
*** akahat|dinner is now known as akahat|rover17:59
opendevreviewJeremy Stanley proposed openstack/pbr master: Test that pbr.json is included in sdists  https://review.opendev.org/c/openstack/pbr/+/82791318:40
opendevreviewJeremy Stanley proposed openstack/pbr master: Correctly evaluate whether we're in a dist context  https://review.opendev.org/c/openstack/pbr/+/82791418:40
sean-k-mooneyfungi: will ^ fix pbr so that it can support -e again18:49
fungisean-k-mooney: i dunno, did it not support -e?18:49
fungiit fixes the missing pbr.json files in sdists/wheels18:49
sean-k-mooneythat was also broken with my weird pip issue18:49
sean-k-mooneypbr was fine but the version discorver when you started nova was broken18:50
sean-k-mooneysaying that it must be a sdist of git tree18:50
fungiyeah, missing pbr.json metadata was a regression in pbr 5.8.0, so if your problem went away with a downgrade to building with pbr 5.7.0 then that change will likely fix it18:51
fungiit only just came to my attention earlier today, but trying to knock it out asap18:51
fungithe sooner we fix it, the fewer releases we'll publish without git data18:52
sean-k-mooneyhttps://paste.opendev.org/show/812529/18:53
sean-k-mooneythat is the error i got when i did -e18:53
sean-k-mooneyand restarted nova18:53
sean-k-mooneyso that is broken in 5.8.018:54
sean-k-mooneylet me check the pbr version i have18:54
sean-k-mooneyya 5.8.018:55
clarkbit is odd that would break when using -e since that should rely on the git install18:55
clarkbI would expect it to be broken without -e and not the other way around18:55
sean-k-mooneysudo pip install was fine since it built the sdist18:55
sean-k-mooneybut -e didnt work for some reason18:55
sean-k-mooneyalso with -e i could not do pip show18:56
sean-k-mooneythe package did not show as installed system properly18:56
sean-k-mooneyso i think this broke the discover 18:56
sean-k-mooneyfungi: did ye pull that form pypi?18:57
fungipull what from pypi?18:57
sean-k-mooneymark it as not discoverable18:57
sean-k-mooneyi was wonderign if that is why i could not repoduce my other git issues in the container18:57
fungioh, yank the release? i think that might break projects which require pbr>=4.8 for pep 517 builds18:57
sean-k-mooneyi was going to see what version of pbr the contaienr had18:57
clarkbI don't think it has been pulled. I'm not sure pulling is appropriate here since it would berak ya18:57
fungier, pbr>5.818:58
fungii can't type. it must be friday18:58
sean-k-mooneyya its not good to yank things18:58
sean-k-mooneyjust wondering if that is why i could not repocue my other pip issue sould like no18:58
fungi5.8.0 added a feature, so projects depending on that feature would be broken if we yanked it18:58
sean-k-mooneyi assume we are going to exclude it in global requirements18:59
sean-k-mooneysince its a knonw broken release18:59
clarkbsean-k-mooney: you can't. PBR is a setup_requiers so doesn't work that way18:59
sean-k-mooneyah right18:59
clarkbif all of openstack switch to pep 517 then you could control the version per project in pyprojcet.toml19:00
fungiit's basically already installed and used to build other things before you reach the point where you'd be applying constraints19:00
clarkbbut otherwise you get what easy_install resolves to which is whatever you have already installed or latest19:00
sean-k-mooneyya19:00
fungianyway, we should have it fixed and released forthwith, early next week at the latest19:01
sean-k-mooneythe contaienr had 5.8.0 as well anyway19:02
sean-k-mooneyfungi: the fact that pip install -e was broken was my original issue19:03
sean-k-mooneyas i said previoul my workflow is to run stack.sh then pip install -e /opt/repos/nova19:03
sean-k-mooneyand restart the nova services 19:04
clarkbfungi: any projects tht are worried about their sdists can bump the bug number and make new releases on the previous commits too19:04
clarkbbut I agree fixing quickly is desireable19:04
fungiyep19:04
opendevreviewJeremy Stanley proposed openstack/pbr master: Test that pbr.json is included in sdists  https://review.opendev.org/c/openstack/pbr/+/82791319:33
opendevreviewJeremy Stanley proposed openstack/pbr master: Correctly evaluate whether we're in a dist context  https://review.opendev.org/c/openstack/pbr/+/82791419:33
opendevreviewJeremy Stanley proposed openstack/pbr master: Correctly evaluate whether we're in a dist context  https://review.opendev.org/c/openstack/pbr/+/82791420:06
opendevreviewJeremy Stanley proposed openstack/pbr master: Test that pbr.json is included in sdists  https://review.opendev.org/c/openstack/pbr/+/82791320:50
opendevreviewJeremy Stanley proposed openstack/pbr master: Correctly evaluate whether we're in a dist context  https://review.opendev.org/c/openstack/pbr/+/82791420:50
opendevreviewJeremy Stanley proposed openstack/pbr master: Import pbr.util directly to break import loops  https://review.opendev.org/c/openstack/pbr/+/82792220:50
elodillesfungi: i've tried to 'quick fix' the sphinx-docs tox target locally without py27, using py35 on stable/queens (nova) and it's quite complex as there are requirement conflicts, and multiple doc changes that were added in rocky (for py3 compatibility and other updates) so i haven't succeded with it yet. and this is only one repo and one branch but there are multiple repos and branches that are 20:55
elodillesfailing due to lack of py27 support for sphinx20:55
elodillesso it's not that trivial to use py35 based sphinx-docs instead of py27 based one... (for old stable branches)21:00
fungielodilles: next question... what's the importance of continuing to build docs for new patches to those branches? is anyone fixing/updating the docs there?21:16
elodilleswell, probably not that important, and for EM it is said that CI support might be downgraded. so i guess that's the easiest option if sphinx-docs jobs will be removed for queens and pike branches where it fails now21:19
opendevreviewJeremy Stanley proposed openstack/pbr master: Test that pbr.json is included in sdists  https://review.opendev.org/c/openstack/pbr/+/82791321:38
opendevreviewJeremy Stanley proposed openstack/pbr master: Always write pbr.json  https://review.opendev.org/c/openstack/pbr/+/82792721:38
opendevreviewJeremy Stanley proposed openstack/pbr master: Always write pbr.json  https://review.opendev.org/c/openstack/pbr/+/82792721:47
opendevreviewClark Boylan proposed openstack/pbr master: Break pbr() recursion via alternative method  https://review.opendev.org/c/openstack/pbr/+/82793021:58
opendevreviewJeremy Stanley proposed openstack/pbr master: Avoid recursive calls into SetupTools entrypoint  https://review.opendev.org/c/openstack/pbr/+/82793121:58
*** dviroel|ruck is now known as dviroel|out22:06
*** dasm is now known as dasm|off22:13
opendevreviewJeremy Stanley proposed openstack/pbr master: Avoid recursive calls into SetupTools entrypoint  https://review.opendev.org/c/openstack/pbr/+/82793123:36

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