Monday, 2021-03-29

*** spatel_ has joined #openstack-ansible00:31
*** spatel_ is now known as spatel00:31
*** sshnaidm|afk has quit IRC02:06
*** evrardjp has quit IRC02:33
*** evrardjp has joined #openstack-ansible02:33
*** jamesdenton has quit IRC02:45
*** jamesdenton has joined #openstack-ansible02:46
*** fresta has quit IRC03:17
*** fresta has joined #openstack-ansible03:18
*** spatel has quit IRC03:44
*** jamesdenton has quit IRC04:03
*** jamesden_ has joined #openstack-ansible04:03
*** raukadah is now known as chkumar|ruck04:06
*** jamesden_ has quit IRC04:37
*** jamesdenton has joined #openstack-ansible04:37
*** jamesdenton has quit IRC05:14
*** jamesdenton has joined #openstack-ansible05:15
*** yasemind has joined #openstack-ansible05:25
*** kleini has joined #openstack-ansible05:40
*** miloa has joined #openstack-ansible06:04
jrosserjonher: you'll probably need to squash 782837 into 783219 as i'm not sure either will be able to merge without the other06:36
noonedeadpunk_mornings06:37
*** miloa has quit IRC06:38
jrosserjonher: then we need to look at what other components need to be installed alongside cloudkitty to make the deployment meaningful for those tests, which could be gnocchii and ceilometer06:38
jrossermorning06:38
noonedeadpunk_yeah, we might need sort of telemetry added06:39
jonhermorning, it deploys without 782837 but one of the processes keeps on loop-crashing in the background, but if you think they should be squashed into one i can do that06:39
noonedeadpunk_somewhere here https://opendev.org/openstack/openstack-ansible/src/branch/master/tests/roles/bootstrap-host/vars/main.yml#L5006:39
noonedeadpunk_but maybe just ceilometer and gnocchi would be enough06:40
jonheri managed to get a working config this night for cloudkitty so i will need to push some more updates to that repo06:40
jonherkeystone gnocci ceilometer should be OK for testing i think06:41
jrosseri was thinking we should do something more minimal than just add the whole telemetry stack, the runtime will get too long otherwise06:41
jonherand it stores to mysql, but that will be there06:41
jrosserthere is a cloudkitty tempest plugin too06:41
jrosserso we'd add something like this https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/75404406:42
openstackgerritDmitriy Rabotyagov proposed openstack/openstack-ansible master: Set buster jobs to NV  https://review.opendev.org/c/openstack/openstack-ansible/+/78268106:43
openstackgerritDmitriy Rabotyagov proposed openstack/openstack-ansible master: Bump SHAs for master  https://review.opendev.org/c/openstack/openstack-ansible/+/78357706:43
jrosserlooks like we have an old master SHA bump patch lying around06:44
openstackgerritDmitriy Rabotyagov proposed openstack/openstack-ansible master: Disable ssl for rabbitmq during upgrade  https://review.opendev.org/c/openstack/openstack-ansible/+/78299606:45
noonedeadpunk_yeah06:45
openstackgerritDmitriy Rabotyagov proposed openstack/openstack-ansible master: Disable ssl for rabbitmq during upgrade  https://review.opendev.org/c/openstack/openstack-ansible/+/78299606:45
openstackgerritDmitriy Rabotyagov proposed openstack/openstack-ansible master: Bump SHAs for master  https://review.opendev.org/c/openstack/openstack-ansible/+/78357706:46
noonedeadpunk_don't we want to use newer pip?06:46
jrossersure06:47
openstackgerritDmitriy Rabotyagov proposed openstack/openstack-ansible master: Bump SHAs for master  https://review.opendev.org/c/openstack/openstack-ansible/+/78357706:47
noonedeadpunk_Oh, https://review.opendev.org/c/opendev/system-config/+/777968 has merged!07:01
noonedeadpunk_So we can try out Bullseye in https://review.opendev.org/c/openstack/openstack-ansible/+/78268107:01
*** luksky has joined #openstack-ansible07:03
noonedeadpunk_probably worth making a follow-up anyway...07:04
openstackgerritDmitriy Rabotyagov proposed openstack/openstack-ansible master: [DNM] Add Debian Bullseye support  https://review.opendev.org/c/openstack/openstack-ansible/+/78360607:10
*** jamesdenton has quit IRC07:10
openstackgerritDmitriy Rabotyagov proposed openstack/openstack-ansible master: [DNM] Add Debian Bullseye support  https://review.opendev.org/c/openstack/openstack-ansible/+/78360607:10
*** jamesdenton has joined #openstack-ansible07:11
jrossernoonedeadpunk_: i think we need to look at making bullseye images really first07:12
noonedeadpunk_yeah. making patch to nodepool07:12
jrosseroh cool07:13
noonedeadpunk_I just though it was already there for some reason :(07:13
jrosseri did notice on some of our stable branches we use debian-stable == stretch07:13
jrosserwe should probably change that before getting a surprise07:13
*** rpittau|afk is now known as rpittau07:15
* jrosser wonders why all the roles that start with 'm' are the ones which break07:20
noonedeadpunk_lol07:41
noonedeadpunk_yep, we probably should getting rid of stretch...07:42
noonedeadpunk_but porbably not the highest prio07:42
*** shyamb has joined #openstack-ansible08:09
*** tosky has joined #openstack-ansible08:28
*** noonedeadpunk_ is now known as noonedeadpunk09:08
*** shyamb has quit IRC09:31
*** shyamb has joined #openstack-ansible09:33
*** CeeMac has quit IRC09:37
noonedeadpunklooks like CI is totally broken...09:48
noonedeadpunkon neutron db expand09:49
noonedeadpunkdoh09:49
noonedeadpunkhave we merged smth for neutron...09:50
noonedeadpunksee only https://opendev.org/openstack/openstack-ansible-os_neutron/commit/e06c25eaa15c305ec2276fe256fe66719ce0d7d309:51
noonedeadpunkhttps://8b7bc396c22f90223dfa-906a8885044ac3b62edc724702c6de01.ssl.cf1.rackcdn.com/783577/5/check/openstack-ansible-deploy-aio_metal-centos-8/00474e0/logs/ara-report/results/1378.html09:52
*** frickler has joined #openstack-ansible09:55
*** shyamb has quit IRC10:03
*** shyamb has joined #openstack-ansible10:04
noonedeadpunklooking at trove config now, there's a lot more then just single bug with innobackupex10:10
*** sshnaidm|afk has joined #openstack-ansible10:18
noonedeadpunkjrosser: I guess this ends up weird to what I see in aio https://opendev.org/openstack/openstack-ansible-lxc_hosts/src/branch/master/tasks/lxc_cache_create.yml#L89 http://paste.openstack.org/show/803999/10:22
noonedeadpunkhave we accidentaly change behaviour with https://opendev.org/openstack/openstack-ansible-lxc_hosts/commit/7fc5e9950ea9e8b379295837fede70f864502439 ?10:22
noonedeadpunk(non related to recent neutron failure)10:23
noonedeadpunkoh, hm... there's even config for `ubuntu-bionic-amd64`10:25
noonedeadpunkhttp://paste.openstack.org/show/804000/10:25
jrossernoonedeadpunk: did i break something?10:32
jonherin regards to cloudkitty+tempest it looks like it's already enabled in the tempest role https://github.com/openstack/openstack-ansible-os_tempest/search?q=tempest_service_available_cloudkitty and should match/test unless i'm overlooking something which could be very likely10:35
noonedeadpunkwell, no, but having ubuntu-bionic-amd64 among lxc-ls is weird. And not sure how/when it appeared there10:35
noonedeadpunkJust guessed you might have a clue since you was looking through everything we're doing there pretty recently10:36
jrosserhmm10:38
jrosserjonher: yes i took a look and it's already there, though it doesnt actually seem to run any tests for cludkitty10:38
*** CeeMac has joined #openstack-ansible10:46
jonherhm yeah you are right, they are listed in "os_tempest : List tempest tests" but not executed according to the logs10:55
jrosserjonher: if you have your AIO might be worth having a poke at that, see if there is some allow/block list on the tempest tests, maybe we just don't enable them?11:03
jonheri've just deployed a VM to start testing that, so will give it a shot11:03
noonedeadpunkbtw regarding tempest..11:12
openstackgerritDmitriy Rabotyagov proposed openstack/openstack-ansible-os_tempest master: Log tempestconf inside tempest_log_dir  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/78363711:12
*** fanfi has joined #openstack-ansible11:22
*** sshnaidm|afk is now known as sshnaidm|off11:45
*** rh-jelabarre has joined #openstack-ansible11:57
jrossernoonedeadpunk: i have ubuntu-bionic-amd64 show up in lxc-ls on my victoria environment, so thats not new12:06
noonedeadpunkaha...12:06
noonedeadpunkthat's good and bad news at the same time I guess12:07
jrosseri wonder if the original image gets started at some point12:07
jrosserbecasue it's State: STOPPED with lxc-info12:07
noonedeadpunkas I don't have this in my upgraded envs12:07
jrossertheres no sign of it in /var/log/lxc/... though which suggests it has never been run12:09
noonedeadpunk`btrfs qgroup limit {{ item }} /var/lib/lxc/{{ lxc_container_base_name }}` makes operation against this exact path..12:09
noonedeadpunkso we might use it just for cache preparation12:10
noonedeadpunkand the thing that was not intended is having config12:11
jrosserit's odd becasue i thought the result of the cache prep ended up in /var/cache/lxc/download/....12:12
noonedeadpunkindeed12:13
jrosserlooking in a random CI job log i see no reference to ubuntu-focal-amd64 until right at the end when it does log collection12:14
noonedeadpunkwell, apt-file not sure helpfull in searching for packages that could provide config12:18
noonedeadpunkbut indeed it appeared 8 mins before any container on the aio12:19
jrosserif you have an AIO then you could look at the same timestamps in /openstack/log/ansible-logging/..12:20
noonedeadpunkand has different permissions...12:20
jrosserthat would show which tasks were running12:20
*** shyamb has quit IRC12:20
jrosserhere on my real environment the /var/lib/ubuntu-bionic-amd64 directory is much older than the dirs/files for the rest of the containers12:21
jrossermaybe this only happens with the image download/build12:22
noonedeadpunkum, log does not contain this time at all...12:23
noonedeadpunkalso it's super weird as consist like from facts?12:25
jrosseris this a new AIO you have?12:26
noonedeadpunkyep12:26
noonedeadpunkjust spawned today12:26
noonedeadpunkto see wtf is going on with neutron12:27
jrosseroh well, i wonder if this is a side-effect of using COW backing12:27
jrosseri have the rootfs tgz in /var/cache/lxc/download/ubuntu/bionic/amd64/default/12:28
jrosserbut thats no good for the ZFS backing store i have here, so the base image needs to be put into the ZFS somehow then the actual containers are snapshots off that12:29
jrosseri expect the same it true for btrfs if thats using snapshots too12:29
noonedeadpunkeventually it does not contain anything except gathered facts o_O12:29
*** pcaruana has quit IRC12:30
jrosserhmm? http://paste.openstack.org/show/804007/12:30
jrosserhttps://github.com/openstack/openstack-ansible-lxc_container_create/blob/master/tasks/lxc_container_create_cow.yml#L3412:32
*** fanfi has quit IRC12:37
*** pcaruana has joined #openstack-ansible12:39
*** fanfi has joined #openstack-ansible12:40
*** cloudnull has joined #openstack-ansible12:41
jonheri have 2 aio's that's 30days+ old if you want me to check something12:46
noonedeadpunkjrosser: oh, really looks like that's it12:49
jrossermaybe we don't expect to find that with dir backing i guess12:50
jrosseri would expect each container to be a freshly unpacked copy of whats in /var/cache/lxc in that case perhaps12:51
noonedeadpunkbut I guess in aio we should have `lxc_container_backing_store: dir`12:52
noonedeadpunkyeah12:53
* jrosser looks at config_template broken jobs12:54
jrosserwtf is this test stuff doing 8-O12:54
noonedeadpunkoh, there's really complicated testing there...12:54
noonedeadpunkit's more like unit tests with mock on ansible12:55
jrossersomehow with the host and a container too12:55
jrosserbut only looks like it tests one set of outcomes12:55
jrosserunless i totally misunderstand how handlers work12:55
*** spatel_ has joined #openstack-ansible13:11
*** spatel_ is now known as spatel13:11
noonedeadpunkhm, they used to work recently13:12
spatelnoonedeadpunk jrosser not sure why it failed - https://review.opendev.org/c/openstack/openstack-ansible/+/78331813:13
noonedeadpunkbut agree, that they are weird and not easy readable13:16
jrosserwhat i see is this https://github.com/openstack/ansible-config_template/blob/master/tests/test-yaml.yml#L2613:22
jrosserreturns "prepared": "{\n    \"added\": {},\n    \"changed\": {},\n    \"removed\": {}\n}"13:22
jrosserso i wonder if config_template is no longer doing the right thein for ansible run with --diff13:22
jrosserwhich could have broken with an ansible upgrade13:22
noonedeadpunkiirc it didn;'t work properly with diff for a while13:24
noonedeadpunkI can recall dmsimard has pointed to this a while back when tried out having a diff recorded in ara or smth like that13:25
jrosserthis whole section of asserts is relying on the diff results being correct https://github.com/openstack/ansible-config_template/blob/master/tests/test.yml#L81-L11213:27
*** d34dh0r53 has joined #openstack-ansible13:32
noonedeadpunkfound what's wrong with our CI overall13:48
noonedeadpunkit's importlib-metadata 3.9.0. 3.9.1 has been released half an hour ago and fixes the issue13:48
*** MrClayPole has quit IRC13:49
jrosserthats pinned in u-c13:49
noonedeadpunkthe question is why in the world I did have importlib-metadata-3.9.0 installed13:50
noonedeadpunkyeah13:50
* jrosser looks at new resolver13:50
*** d34dh0r53 has quit IRC13:52
*** MrClayPole has joined #openstack-ansible13:54
noonedeadpunkI think it's neutron only though13:55
*** d34dh0r53 has joined #openstack-ansible13:55
noonedeadpunknova for example has 3.7.2 installed13:55
noonedeadpunkaha, for neutron we retrieve content and do some replacement13:56
*** spatel has quit IRC13:57
noonedeadpunkjrosser: seems, that content is trimmed to 400 lines13:59
jrosseroh no14:00
noonedeadpunkhttp://paste.openstack.org/show/804012/14:00
*** spatel_ has joined #openstack-ansible14:00
*** spatel_ is now known as spatel14:00
jrosserthis maybe https://github.com/openstack/openstack-ansible-os_neutron/blob/master/tasks/neutron_install.yml#L54-L6514:01
noonedeadpunkyeah14:01
noonedeadpunkI was jsut looking at it, and my /var/www/repo/os-releases/22.0.0.0rc2.dev114/neutron-22.0.0.0rc2.dev114-source-constraints.txt does not simply have importlib-metadata14:01
jrosser400 is just too much a round number14:03
noonedeadpunkwell, at least we'vecatched that...14:04
jrosseryeah14:05
jrossercould be in all sorts of places, uri only returns 400 lines, or only 400 in the registered var, ......14:05
noonedeadpunknot sure about workaround though...14:07
noonedeadpunkmaybe we should save it as usual, just drop content with lineinfile...14:07
jrosserit needs to end up as a file on the repo server14:08
noonedeadpunkand pass list of things to drop with another var to python_venv_build?14:08
jrosseryeah i think thats the only way, as we don't know where the file needs to be places14:08
noonedeadpunkyeah14:08
jrosseronly python_venv_build knows that14:08
noonedeadpunkand since we can't jsut pass content for some reason...14:09
jrosserseems like a good improvement, new var for patterns to drop, then remove those tasks i added in the roles14:09
jrossertheres a few places that was needed14:09
noonedeadpunkwell yes, but we will have to loop with removing line by line14:09
noonedeadpunkwhile you did that in memory... so not sure about how much improvement that is..14:09
jrossermaybe some debug statements to see where the data gets lost14:10
jrosseri think that the tripleo people needed something similar14:10
noonedeadpunkit fails on get url I believe14:13
noonedeadpunk`"transfer_encoding": "chunked"`14:13
spateljamesdenton are you around? I have few question related OVN14:15
jrosseri wonder if we can set some accept_encoding to prevent chunked14:17
jrossernoonedeadpunk: is this valid? https://github.com/openstack/ansible-config_template/blob/master/tests/test.yml#L78-L7914:22
jrosserit seems to ignore the delegate, running all the tasks again against localhost14:23
noonedeadpunkyou mean after ansible update? dunno. but I guess it used to be14:25
jrosseri think that the diff is coming out empty because it targets localhost again rather than container114:26
jrosseri see it run again here https://zuul.opendev.org/t/openstack/build/31c89962d3354d33a4e821c84f474bc6/log/job-output.txt#10766-1076914:26
jrosserwith "ok" rather than "changed"14:26
fanfiHi, could I ask for help? during installing new deployment i got following error. http://paste.openstack.org/show/804004/14:32
jrosserfanfi: you are using the master branch i think?14:34
fanfigood point...i will check it14:34
jrosserbest to pick the most recent tag on a stable branch unless you are doing development work14:35
fanfi git branch14:36
fanfi* master14:36
openstackgerritJonathan Rosser proposed openstack/ansible-config_template master: Run tests against localhost and container  https://review.opendev.org/c/openstack/ansible-config_template/+/78366114:46
fanfijrosser and I am up to date with master repo14:47
jrosserfanfi: the master branch is the one that will become the *next* release of openstack-ansible, i.e Wallaby14:48
jrosserif you want a Victoria deployment, which is the current stable release then you need to use a tag from the stable/victoria branch14:48
jrosseri knew you have master checked out becasue the 'admin' user on the database is something thats not yet in a released stable version14:49
noonedeadpunkbtw I didn't thought it should fail like that14:53
jrosserno, though i wonder if thats ever been tested on a multinode though14:54
jrosseron well infra jobs should do that14:55
jrosser*oh14:55
jrosserdid you see there is a mariadb jira about the 10.5.8->10.5.9 upgrade troubles?14:55
noonedeadpunknope, I haven't14:55
jrosserseems they have a mistake with superuser grants being br0k across the upgrade14:55
jrosserhttps://jira.mariadb.org/browse/MDEV-2503014:56
noonedeadpunkdoh. so it's not our issue with 10.5.9 atm14:56
noonedeadpunkor we should switch to admin earlier?14:57
jrosserwell, we did some AIO work here last week and gshippey sees something similar but different with the root user getting broken14:57
jrosserafter the upgrade we saw access: "0", i.e root user looses all grants totally14:57
noonedeadpunkI wonder if we can jsut create admin user _before_ galera upgrade...14:58
noonedeadpunkwith upgrade scripts14:58
jrosserright, yes14:58
jrosserwe still rely on the root user for replication though14:59
noonedeadpunkwell, according to bug, replication should left as a permission14:59
noonedeadpunkbut yeah, not sure...15:00
fanfijrosser when I switch branch 'stable/victoria' from 'origin' and pull the repo i got message Already up to date.15:03
jrosserfanfi: ok, i think thats normal15:04
jrossergit usually keeps all the branches locally for you15:04
fanfiperfect thanks, i will try it ...and are you editing any mariadb parameters like max_connections ..atc ?15:09
fanfior you have it all in default15:10
*** jamesdenton has quit IRC15:12
*** jamesdenton has joined #openstack-ansible15:13
*** macz_ has joined #openstack-ansible15:15
jrosserfanfi: the defaults applied are here https://github.com/openstack/openstack-ansible-galera_server/blob/master/defaults/main.yml#L148-L15215:22
noonedeadpunkmaybe it was just that interminent issue in galera we see sometimes in CI15:34
*** rh-jelabarre has quit IRC15:43
*** rh-jelabarre has joined #openstack-ansible15:43
*** rh-jelabarre has quit IRC15:44
*** rh-jlabarre has joined #openstack-ansible15:44
*** Guest76033 is now known as jroll15:50
noonedeadpunko_O we catch the same issue with importlib-metadata on V for buster https://zuul.opendev.org/t/openstack/build/931b57810ec2442189d7e3771595ac74/log/logs/host/keystone-wsgi-public.service.journal-10-53-22.log.txt#27515:50
jrosserhttps://github.com/redhat-openstack/infrared/blob/master/infrared/common/roles/create_venv/tasks/main.yml#L118-L13715:52
noonedeadpunkwell...15:52
noonedeadpunkanyway, wtf on V15:52
jrosserjust looking on my V deployment here and i have 3.0.0 in the keystone container15:54
noonedeadpunkdog15:55
noonedeadpunk*doh15:55
noonedeadpunk`importlib-metadata===1.7.0;python_version=='3.6'`15:55
noonedeadpunkbuster has 3.715:55
noonedeadpunk*facepalm*15:55
noonedeadpunkhttps://opendev.org/openstack/requirements/src/branch/stable/victoria/upper-constraints.txt#L26915:56
noonedeadpunkthat is so... frustrating...15:58
jrosserhere is where that came in https://github.com/openstack/requirements/commit/2d7a41b64c8f891a0c6c0a76f30ff7fe7557163a15:58
* jrosser asks the requirements people16:00
noonedeadpunkhonestly - there're also pretty a number of constraints for 3.6 and 3.8 only16:00
noonedeadpunkthat does not take into account 3.716:00
jrosserwith the new resolver this does kind of point to needing "remove these lines" / "insert these other lines" function for python_venv_build16:01
noonedeadpunkdo we want to add some extras as well?16:02
jrosseri guess that depends if we can get suitable additions/changes made to u-c for python versions like 3.716:03
jrosserif we can't, then new releases of stuff with "unhelpful" entries in UC will break us on buster, or anything else with a slightly out of the ordinary python version16:04
noonedeadpunkShouldn't we just push to have u-c set properly?16:05
jrosserideally yes, agreed16:05
jrosseri guess that needs == changing to >=16:05
noonedeadpunkregarding things where we can do nothing (ie tempest, gnocchi, dunno) yes, we should remove from contraints..16:05
noonedeadpunkfor python? yeah..16:06
noonedeadpunkdoesn't really clear what to do with https://opendev.org/openstack/requirements/src/branch/master/upper-constraints.txt#L257-L258 though16:06
noonedeadpunkor https://opendev.org/openstack/requirements/src/branch/master/upper-constraints.txt#L385-L38616:06
*** rpittau is now known as rpittau|afk16:08
jrosseri guess we are testing those unconstrained right now on osa/buster16:09
jrosserwhich means that the 3.8 version is probably OK16:09
jrosserfeels really like this should be a lint test on u-c16:10
noonedeadpunkyeah16:10
jrosserprometheanfire: are we getting confused here with the 3.7 issue16:22
jrosserthe end result is we have patches which work everywhere, like bionic/focal/centos but blow up on buster16:22
jrosserlike here just fails all the buster jobs https://review.opendev.org/c/openstack/openstack-ansible/+/783580/16:23
prometheanfireok, we should compare the two requirements batches16:25
jrosseri think we are generally concerned with seeing a lot of ==3.6 and ==3.8 in u-c and what that means for a 3.7 system16:26
prometheanfirewell, the officially supported python versions for that release were 3.6 and 3.816:26
jrosserwell https://governance.openstack.org/tc/reference/runtimes/victoria.html16:28
prometheanfirehere are the updates to upper-constraints16:28
prometheanfirehttps://github.com/openstack/requirements/compare/0e97a6d7a11dce9bf2571f86de2bf3ba48daaa38...628ba9dff2189b5392c8a9b5c232c1f261803a9e16:28
prometheanfirebasically, not sure what triggered it here16:28
prometheanfirehttps://github.com/openstack/requirements/commit/ac8bcb00122ccd4c4c8cc22612c14c3c37624026 was the revert, as part of the bot run16:34
prometheanfireso, maybe something in gate happened, we haven't changed the constraints generation command in a while16:36
mgariepyhttps://github.com/openstack/requirements/blob/master/upper-constraints.txt#L109-L11016:37
mgariepyif python is 3.7 maybe some pkg are missing ??16:37
prometheanfireya, the constraints generation command doesn't include 3.7 iirc16:37
noonedeadpunkI don't think they're present for 3.6 and for 2.8 but not for 3.716:37
noonedeadpunk*3.816:38
prometheanfirein project-config16:38
prometheanfireplaybooks/proposal/propose_update.sh16:38
prometheanfirethe generate-constraints command16:38
prometheanfiregenerate-constraints -b blacklist.txt -p /usr/bin/python3.6 -p /usr/bin/python3.8 -r global-requirements.txt > upper-constraints.txt16:38
jrosseris that something that just runs for master branch?16:39
*** klamath_atx has joined #openstack-ansible16:39
prometheanfireya16:39
prometheanfirejust pointing out that 3.7 is not included there16:39
prometheanfirethat gate runs 3.7 was not expected16:39
jrosserno well that might be OK really, as i'm not sure there is a 3.7 which can run W anyway16:40
noonedeadpunkbuster can't so yeah16:40
jrosserour issue is really about V i think16:40
noonedeadpunk+116:41
prometheanfireya, I don't think so, wallaby is explicitly 3.6 and 3.816:41
prometheanfirefor victoria, 3.7 is only for CI16:41
noonedeadpunkwhich would be incorrect16:41
noonedeadpunkbecause of not constrained things16:42
prometheanfirehttps://governance.openstack.org/tc/reference/runtimes/victoria.html says for CI only16:43
noonedeadpunkand it's broken:)16:44
noonedeadpunkwell, at least was, until package has been fixed16:44
prometheanfirewhat's confusing to me is that it's broken NOW16:44
jrosserup to this point whatever the latest version of importlib was OK, by luck16:44
prometheanfirebecause the review you provided doesn't include a reqs change that should trigger it16:44
prometheanfire https://github.com/openstack/requirements/compare/0e97a6d7a11dce9bf2571f86de2bf3ba48daaa38...628ba9dff2189b5392c8a9b5c232c1f261803a9e16:44
noonedeadpunkyes, exactly https://pypi.org/project/importlib-metadata/#history16:45
prometheanfireso, submit a patch to victoria for python==3.7 :P16:45
noonedeadpunkthey did bunch of releases in 2 days. and it might be broken for 3.8 at some point as well16:46
prometheanfireya, though for 3.8 we are using builtin, or should be16:46
noonedeadpunkah, right16:47
noonedeadpunkwhy do we have it constrained then?16:47
prometheanfirebecause it's not included for 3.6 (or 3.7) as part of base python16:48
noonedeadpunkstill for 3.6?16:48
noonedeadpunkok, gotcha16:48
prometheanfirebasically, copy th 3.6 line, and change 3.6 to 3.716:48
prometheanfirefor upper-constraints16:48
prometheanfirewe don't update stable branches so it'll stick16:48
prometheanfirehttps://review.opendev.org/c/openstack/requirements/+/78371516:50
noonedeadpunkalso weird about importlib-resources btw16:52
noonedeadpunkit's native only in 3.9?16:52
noonedeadpunkbut it's https://github.com/openstack/requirements/blob/stable/victoria/upper-constraints.txt#L50116:52
jrosseroh - that may be my fault16:53
prometheanfireif the review needs more stuff pinned for 3.7 feel free to update it16:54
prometheanfiregiven how osa points to a sha though it'll take merging before osa can test in gate I think16:55
jrosseri think we can depends-on it16:56
jrosseroh hrrm actually that may not be true16:56
noonedeadpunkwe can depends-on, but eventually things are fixed by themselves in 3.9.116:56
jrosserwe can depends-on it if we land my u-c cache patches :)16:56
prometheanfireso, since it's unconstrainted you can recheck?16:56
*** gyee has joined #openstack-ansible16:57
noonedeadpunkwell, infra pip mirrors will need to get updated as well I guess16:57
noonedeadpunkbut generally yes16:57
prometheanfireso, transient failure, but updating constraints would be best16:58
noonedeadpunkyes, as eventually they're here to avoid these things from happening16:58
jrossernoonedeadpunk: whilst we look at u-c things, should re remove setuptools from global-requirement-pins17:00
jrosserthat used to be OK with the old pip resolver that we had a specific version in OSA, but the new one breaks every time we are != the version in u-c17:01
jrosseri'm just debugging openstack-ansible-tests broken and thats why17:01
noonedeadpunkI was thinking about that as well. I guess we added it locally since there were periods when they were unconstrained locally17:01
noonedeadpunks/locally/in u-c/17:01
jrosserfeels like we should take out the pin on our side17:02
noonedeadpunkand eventually it worked nicely with old resolver)17:02
noonedeadpunkyeah, I guess so17:02
*** yasemind has quit IRC17:03
jrosseroh17:04
jrosserwe use the same file for the ansible-runtime venv don't we?17:04
noonedeadpunkwe do17:04
noonedeadpunkand for all venvs as well17:05
noonedeadpunkhttps://opendev.org/openstack/openstack-ansible/src/branch/master/inventory/group_vars/all/all.yml#L149-L15017:05
jrosserthe runtime venv is OK https://github.com/openstack/openstack-ansible/blob/master/scripts/scripts-library.sh#L8017:05
jrosserand i think the others will be covered by u-c, except maybe for things like stackviz where it's not used17:07
*** djhankb has joined #openstack-ansible17:07
noonedeadpunkwill push patches to python_venv_build first time in the morning. want to test on fresh head17:09
* noonedeadpunk also remembers about patch to nova regarding qemu open files limit17:10
openstackgerritJonathan Rosser proposed openstack/openstack-ansible master: Use the version of setuptools specified in upper-constraints  https://review.opendev.org/c/openstack/openstack-ansible/+/78372017:10
*** gyee has quit IRC17:14
*** gyee has joined #openstack-ansible17:14
*** gyee has quit IRC17:38
*** gyee has joined #openstack-ansible17:49
*** cloudnull has quit IRC18:43
*** jamesdenton has quit IRC19:02
*** jamesden_ has joined #openstack-ansible19:02
*** cloudnull has joined #openstack-ansible19:21
*** akahat has quit IRC20:56
*** akahat has joined #openstack-ansible21:20
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-tests master: Do not filter setuptools from upper-constraints  https://review.opendev.org/c/openstack/openstack-ansible-tests/+/78374721:21
*** jamesdenton has joined #openstack-ansible21:56
*** jamesden_ has quit IRC21:59
*** jamesden_ has joined #openstack-ansible22:07
*** cloudnull has quit IRC22:09
*** jamesdenton has quit IRC22:09
*** spatel has quit IRC22:11
*** dasp has quit IRC22:13
*** dasp has joined #openstack-ansible22:19
*** luksky has quit IRC22:23
*** jamesdenton has joined #openstack-ansible22:25
*** jamesden_ has quit IRC22:28
*** cloudnull has joined #openstack-ansible22:52
*** macz_ has quit IRC23:12
*** macz_ has joined #openstack-ansible23:19
*** macz_ has quit IRC23:23
*** macz_ has joined #openstack-ansible23:55
*** macz_ has quit IRC23:59

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