Thursday, 2020-09-10

*** zzzeek has joined #openstack-infra00:01
*** rlandy has quit IRC00:21
*** armax has quit IRC00:33
*** zzzeek has quit IRC00:38
*** zzzeek has joined #openstack-infra00:42
*** gyee has quit IRC00:50
*** d34dh0r53 has quit IRC00:57
*** armax has joined #openstack-infra01:21
*** eandersson has quit IRC01:44
*** eandersson has joined #openstack-infra01:45
*** vishalmanchanda has joined #openstack-infra01:58
*** zzzeek has quit IRC02:14
*** stevebaker_ is now known as stevebaker02:15
*** zzzeek has joined #openstack-infra02:15
*** artom has quit IRC02:28
*** zzzeek has quit IRC02:45
*** zzzeek has joined #openstack-infra02:48
*** rcernin has quit IRC02:50
*** ramishra has joined #openstack-infra02:59
*** rcernin has joined #openstack-infra02:59
*** armax has quit IRC03:02
*** stevebaker has quit IRC03:19
*** stevebaker has joined #openstack-infra03:19
openstackgerritIan Wienand proposed openstack/project-config master: Add Fedora 32 builds  https://review.opendev.org/75064203:45
openstackgerritMerged openstack/project-config master: Add Fedora 32 builds  https://review.opendev.org/75064204:06
*** dave-mccowan has quit IRC04:12
*** ykarel|away has joined #openstack-infra04:22
*** ykarel|away is now known as ykarel04:23
*** ykarel has quit IRC04:30
*** bhagyashris|rove is now known as bhagyashri|rover04:32
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-infra04:33
*** ykarel has joined #openstack-infra04:37
*** ykarel_ has joined #openstack-infra04:51
*** ykarel has quit IRC04:54
*** matt_kosut has joined #openstack-infra05:01
*** sorrison has joined #openstack-infra05:03
sorrisonHi, I'm converting a project (networking-midonet) over to zuulv3 and I'm having some issues with the multinode. Wondering if I can get SSH access to the nodes to debug further?05:04
sorrisonjhesketh you around?05:08
jheskethsorrison: yes, but I'm not longer infra-root/core sorry05:09
sorrisonah ok, hi by the way05:10
sorrisonknow anyone in this timezone who is?05:10
jheskethianw might be around05:12
jheskethalso hi! :-)05:12
*** ykarel__ has joined #openstack-infra05:12
*** ykarel_ has quit IRC05:14
*** jtomasek has joined #openstack-infra05:18
*** ysandeep|away is now known as ysandeep05:18
*** ykarel__ is now known as ykarel05:22
*** jtomasek has quit IRC05:22
*** lmiccini has joined #openstack-infra05:42
ianwsorrison: what's the job / change?05:54
sorrisonhttps://review.opendev.org/#/c/749857/05:55
sorrisonits the networking-midonet-ml2-tempest-multinode05:55
sorrisonmy theory is that the multinode bridge playbook is somehow conflicting with what midonet is doing but I haven't been able to replicate locally05:56
*** zzzeek has quit IRC05:57
ianwone sec, let me log in and put a hold on it06:00
*** zzzeek has joined #openstack-infra06:01
*** ykarel_ has joined #openstack-infra06:01
*** ykarel has quit IRC06:03
sorrisonIt's not running, want me to recheck?06:05
ianwsorrison: this you? -> https://github.com/sorrison.keys06:05
sorrisonyip thats me06:05
ianwok, it might take a little.  the 0600 periodic job kick offs are always fun06:09
*** ricolin has quit IRC06:10
sorrisoncould always pick this up tomorrow morning sometime instead06:15
*** ykarel_ is now known as ykarel06:15
ianwsorrison: it should start in a sec and then the nodes will hold till you shut them down or we kill them06:18
sorrisonok great, thanks06:20
sorrisonianw: what username do I log in as?06:24
ianwsorrison: try roo@198.72.124.1806:26
ianwroot even06:26
sorrisonI'm in06:27
*** eolivare has joined #openstack-infra06:28
*** ralonsoh has joined #openstack-infra06:34
*** dklyle has quit IRC06:43
*** slaweq has joined #openstack-infra06:44
openstackgerritAndreas Jaeger proposed openstack/openstack-zuul-jobs master: Remove legacy-tempest-dsvm-zeromq-multibackend  https://review.opendev.org/75087806:45
*** hashar has joined #openstack-infra06:50
*** jaosorior has joined #openstack-infra06:58
openstackgerritMerged openstack/project-config master: pynotedb: remove project from infrastructure systems  https://review.opendev.org/75063506:58
*** jtomasek has joined #openstack-infra06:59
sorrisonianw: Could I get access to 198.72.124.208 too please (the other node in the same job)07:07
ianwsorrison: umm, you should be able to bounce via the first node07:11
sorrisonAh, I see I can get to the other one through the internal network07:11
sorrison:-)07:11
*** priteau has joined #openstack-infra07:16
*** tosky has joined #openstack-infra07:32
AJaegerconfig-core, please review https://review.opendev.org/750878 to remove a broken job (repo was retired)07:32
*** jpena|off is now known as jpena07:40
*** jcapitao has joined #openstack-infra07:42
*** priteau has quit IRC07:47
*** andrewbonney has joined #openstack-infra07:47
*** zzzeek has quit IRC07:48
*** zzzeek has joined #openstack-infra07:50
*** priteau has joined #openstack-infra07:53
fricklerlyarwood: ianw: the fedora32 image seem to have built successfully. does it also need some new repo mirror setup?07:55
*** xek has joined #openstack-infra07:55
*** xek has quit IRC08:09
*** xek has joined #openstack-infra08:10
*** lucasagomes has joined #openstack-infra08:11
*** xek has quit IRC08:17
*** jcapitao has quit IRC08:27
*** jaicaa has quit IRC08:29
*** jaicaa has joined #openstack-infra08:31
*** ysandeep is now known as ysandeep|lunch08:34
*** ykarel_ has joined #openstack-infra08:35
*** rcernin has quit IRC08:35
*** ykarel has quit IRC08:36
*** jcapitao has joined #openstack-infra08:36
*** ykarel_ is now known as ykarel|lunch08:40
*** jcapitao has quit IRC08:41
*** jcapitao has joined #openstack-infra08:42
*** jtomasek has quit IRC08:45
*** slaweq has quit IRC08:46
*** gfidente has joined #openstack-infra08:49
*** derekh has joined #openstack-infra08:52
*** ralonsoh has quit IRC08:54
*** ralonsoh has joined #openstack-infra08:54
*** ricolin has joined #openstack-infra09:09
*** ykarel|lunch has quit IRC09:12
*** dtantsur|afk is now known as dtantsur09:14
*** ykarel has joined #openstack-infra09:19
lyarwoodfrickler: I'm not sure if we've done that before with Fedora, any idea where that would be configured and I can take a look?09:23
fricklerlyarwood: I was just looking for that ;) https://review.opendev.org/712680 seems to be the reference plus some followup for the updates/ part09:27
lyarwoodI think that should be *remove* releases/29 FWIW09:29
lyarwoodfrickler: do you already have a change in progress?09:29
lyarwoodhttps://review.opendev.org/#/c/713177/ already removed f2909:30
lyarwoodargh configure-swap is failing still on f3209:32
lyarwoodit started to fail on f31 after a recent kernel update09:32
lyarwoodappears fallocate on ext4 now leaves holes in the filesystem that borks swapon09:33
* lyarwood pushes a fix09:33
*** ysandeep|lunch is now known as ysandeep09:35
fricklerlyarwood: https://review.opendev.org/713169 is the fup I was talking about. removing f30 will have to wait until no one uses it anymore09:37
fricklerlyarwood: also the swap failure seem to happen only on a subset of our cloud providers, but if you can fix it, that's great. I did look into it some time ago but didn't follow up09:38
lyarwoodfrickler: https://bugzilla.redhat.com/show_bug.cgi?id=1827115 - it doesn't cover what has actually changed just that it's borked for other people, I can reproduce locally as well09:39
openstackbugzilla.redhat.com bug 1827115 in kernel "[upstream kernel]swapon failed if the swap file is created by fallocate in ext4 partition" [Medium,New] - Assigned to kernel-maint09:39
lyarwoodthe workaround doesn't appear to work for me however so meh09:39
fricklerlyarwood: ah, now I seem to remember that we discussed swapping swapfile generation to dd and also reduce the size to 1G in order to spend less time on it09:43
lyarwoodfrickler: kk, I can push a change for this now as I can't find a workaround for this locally tbh09:52
* lyarwood assumes all distros will hit this eventually09:52
openstackgerritLee Yarwood proposed openstack/openstack-zuul-jobs master: configure-swap: Always use dd and limit swap size to 1024MB  https://review.opendev.org/75094109:55
*** hashar has quit IRC09:58
*** hashar has joined #openstack-infra09:58
fricklerlyarwood: there's a trailing space in that, otherwise I agree09:59
lyarwoodgah sorry10:01
openstackgerritLee Yarwood proposed openstack/openstack-zuul-jobs master: configure-swap: Always use dd and limit swap size to 1024MB  https://review.opendev.org/75094110:02
*** slaweq has joined #openstack-infra10:20
*** StevenK has quit IRC10:21
*** jaosorior has quit IRC10:24
*** Lucas_Gray has joined #openstack-infra10:32
*** rcernin has joined #openstack-infra10:39
*** dmellado has quit IRC11:18
*** StevenK_ has joined #openstack-infra11:19
*** dmellado has joined #openstack-infra11:19
sean-k-mooneydoes disk image builder use anything for tracking features by the way. in my copious free time.... i have started playing with creating a alpine element and i need to create a apk element next for the package installer11:20
*** jcapitao is now known as jcapitao_lunch11:21
sean-k-mooneythe end goal is to build a replacment for cirros11:22
sean-k-mooneygiven its more or less un maintained now11:22
*** StevenK_ is now known as StevenK11:23
*** artom has joined #openstack-infra11:31
*** jpena is now known as jpena|lunch11:31
*** dmellado has quit IRC11:33
*** dmellado has joined #openstack-infra11:34
*** thiagop has joined #openstack-infra11:42
*** dave-mccowan has joined #openstack-infra11:46
*** arxcruz|ruck is now known as arxcruz|pto12:05
*** rlandy has joined #openstack-infra12:06
*** dmellado has quit IRC12:10
*** rfolco has joined #openstack-infra12:11
*** dmellado has joined #openstack-infra12:11
*** jcapitao_lunch is now known as jcapitao12:16
*** rfolco is now known as rfolco|ruck12:18
*** hashar has quit IRC12:31
sean-k-mooneysmcginnis: frickler ^ any comment on diskimage-build "feature" tracking by the way12:34
sean-k-mooneyi was just going to submit the patches when it worked and figure it out then12:34
*** hashar has joined #openstack-infra12:37
*** stephenfin has joined #openstack-infra12:37
*** jpena|lunch is now known as jpena12:39
*** hashar has quit IRC12:40
*** ykarel_ has joined #openstack-infra12:48
*** ykarel has quit IRC12:51
sean-k-mooneyoh my vpn is down12:54
sean-k-mooneyi tought downstream irc was terrible quite today12:55
*** derekh has quit IRC12:58
fungisean-k-mooney: probably could get by with just good commit messages and talking things through in irc, diskimage-builder has an #openstack-dib irc channel of their own and uses https://launchpad.net/diskimage-builder for defect tracking so might also use that to do feature planning13:00
fungialso mailing lists are a fine place to do feature planning, in my opinion13:00
sean-k-mooneycool13:01
sean-k-mooneyi have the basic downloading of the mini root filesystem working13:01
sean-k-mooneyall of the other image they provide are ISOs for some reason13:02
sean-k-mooneyso i was going to use the filesystem tar as a base eventhough that is normally for containers13:02
sean-k-mooneybut sicne we are building via a chroot i think it makes sense13:02
sean-k-mooneywhat im currenlty failing on is the lack of install-pacakges but that just because i have not create the apk element yet13:03
sean-k-mooneyanyway ill pop into the dib channel and say hi at some point13:03
sean-k-mooneythe only disadvantage of the Mini root filesystem is i need to remember to add a kernel and bootloader13:05
*** priteau has quit IRC13:11
*** sorrison has quit IRC13:14
*** sorrison has joined #openstack-infra13:14
*** priteau has joined #openstack-infra13:16
*** xek has joined #openstack-infra13:18
*** lmiccini has quit IRC13:21
*** lmiccini has joined #openstack-infra13:23
openstackgerritSean McGinnis proposed openstack/project-config master: Remove noop jobs for python-adjutantclient  https://review.opendev.org/75099013:25
*** ykarel_ is now known as ykarel13:25
*** Goneri has joined #openstack-infra13:26
*** piotrowskim has joined #openstack-infra13:28
*** armax has joined #openstack-infra13:38
*** hashar has joined #openstack-infra13:48
*** d34dh0r53 has joined #openstack-infra14:01
*** thiagop has quit IRC14:15
AJaegerfungi, clarkb, could you check the mailthread at http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017169.html about cinder old branches, please? What's the best way forward here with the broken jobs?14:17
*** ykarel is now known as ykarel|away14:18
*** jtomasek has joined #openstack-infra14:23
AJaegerconfig-core, please review https://review.opendev.org/750878 to remove one broken job14:25
openstackgerritAndreas Jaeger proposed openstack/project-config master: Retire devstack-plugin-pika project  https://review.opendev.org/74871214:40
fricklerconfig-core, please also review https://review.opendev.org/750941 to the the issues with swap setup that we've been seeing on fedora for a while14:40
fricklers/the the/fix the/14:41
AJaegerconfig-core, and review 748712 to retire another repo, please14:41
*** ykarel|away has quit IRC14:45
*** d34dh0r53 has quit IRC14:45
*** d34dh0r53 has joined #openstack-infra14:46
fungiAJaeger: i was following it, sounds like there's some concern that deleting those branches will have a cascade effect for devstack jobs on similar branches of other integrated openstack services?14:50
*** dklyle has joined #openstack-infra14:54
*** sreejithp has joined #openstack-infra14:56
AJaegerfungi: yeah, that's the concern. I wonder what to do with the broken jobs, I would like to get that solved soonish.14:58
clarkbdeleting branches that define jobs causes zuul to s top running thosejobs in other projects iirc15:00
clarkbso for example grenade can delete its jobs on the oldeat branch and that oldest branch across openstack will stop running the grenade jobs15:00
fungisure, more concerned about deleting cinder branches which devstack is trying to checkout for testing nova changes on related branches there15:01
fungii suppose devstack needs to switch to checking out the eol tags for those first15:02
clarkbor disable cinder15:04
*** lmiccini has quit IRC15:08
AJaegerso, do we care about those broken jobs that I try to remove - or wait until those branches are really deleted?15:11
AJaegerI wanted to have again at some point zero Zuul failures in the openstack tenant15:11
*** __ministry1 has joined #openstack-infra15:15
*** __ministry1 has quit IRC15:16
*** hashar has quit IRC15:17
*** hongbin has joined #openstack-infra15:25
clarkbIf openstack wants to delete the branches together we should land the fixes in cinder15:32
AJaegerclarkb: could you followup on the thread then, please?15:42
clarkbya I am doing a start of school year thing in a minute then should be back to help in an hour or so15:43
AJaegerclarkb: thanks, this is not urgent - just wanted to discuss it while it's on my mind ;)15:45
*** rcernin has quit IRC15:50
*** Lucas_Gray has quit IRC15:52
*** lucasagomes has quit IRC16:02
*** jcapitao has quit IRC16:16
*** dtantsur is now known as dtantsur|afk16:22
*** ysandeep is now known as ysandeep|away16:25
openstackgerritOleksandr Kozachenko proposed openstack/project-config master: Add some more monasca projects in vexxhost tenant  https://review.opendev.org/75104616:31
*** hamalq has joined #openstack-infra16:32
openstackgerritOleksandr Kozachenko proposed openstack/project-config master: Add some more monasca projects in vexxhost tenant  https://review.opendev.org/75104616:32
*** dmellado_ has joined #openstack-infra16:33
*** dmellado has quit IRC16:34
*** dmellado_ is now known as dmellado16:34
*** artom has quit IRC16:34
*** dmellado has quit IRC16:39
*** dmellado has joined #openstack-infra16:39
clarkbAJaeger: [cinder][stable] branch freeze for ocata, pike <- that thread right?16:41
*** dmellado has quit IRC16:49
*** jpena is now known as jpena|off16:49
*** dmellado has joined #openstack-infra16:55
elodclarkb: does force-merge works even if the branch has *-eol tag? ( regarding http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017183.html )16:58
elodif yes, then I'll remove my -2 and let Cinder team decide16:58
clarkbelod: if the branch is still open (it must be if zuul si complaining) then yes16:58
clarkbbut why did they eol tag it and not delete the branch?16:58
clarkbsounds like that is the actual issue. Those two things should happen together16:58
elodyes, that was my understanding too16:59
clarkbpreviously to the extended maintenance changes we'd usually give someone like tonyb powers to do them together16:59
clarkb(via gerrit acl changes)16:59
elodI guess Cinder thought other projects have already eol'd their ocata branches16:59
clarkbif they've already tagged it maybe the best thing is to delete the branchse and openstack deals with the fallout?17:00
clarkbfungi: ^ thoughts?17:01
elodand realized that they'd be the first 'core' project to EOL, which could cause issues17:01
fungiyes, the idea behind the -eol tag was that no new changes would be merged to that branch (most easily enforced by deleting the branch itself)17:02
elodclarkb: Brian wrote it'd be good to wait with the delete after RC >>> http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017171.html17:02
fricklerclarkb: I agree with deleting the branches, if other projects still want to test eol branches, it is up to them to amend their jobs17:02
fungiif we merge changes after the -eol tag and then delete the branch, those changes will be orphaned (no longer appear in the history of any branch or tag)17:02
*** gyee has joined #openstack-infra17:03
fricklerwell we could tag -eol2 but that might be even more confusing17:04
fungiit's so end-of-lifed we tagged it twice!17:04
fungii wonder if rosmaita's concern for disrupting development this close to release is really warranted, seeing as how it would at worst disrupt development for other stable branches not the branch which is being groomed for release17:04
elodmy question: if those experimental job removal patches are not merged for a couple of weeks more, does that cause any issues anywhere?17:05
clarkbelod: it causes zuul to continue to complain17:05
clarkbits not critical and waiting for the RC is probably sane. I think if we take anything from this its that branches must be deleted when eol tagged17:06
clarkbthis not happening is the underlying bug17:06
elodclarkb: I agree17:06
fungialso one of the reasons we took to deleting eol branches long ago was so that people pulling in their local clones would actually get an error when the remote branch ceased to exist, and that would hopefully get their attention to notice the -eol tag17:07
*** gfidente is now known as gfidente|afk17:07
elodfungi: that sounds logical17:09
clarkbalso we might consider deleting zuul configs as a pre eol tag step17:10
elodclarkb: yes, I was thinking about that in the past17:10
*** dmellado has quit IRC17:12
elodclarkb: but during some discussions we agreed the the process is enough if just contain the step to remove the job definitions *outside* of the "to be EOL'd" branch, which are not used anymore17:12
openstackgerritMerged openstack/project-config master: Add some more monasca projects in vexxhost tenant  https://review.opendev.org/75104617:12
*** dmellado has joined #openstack-infra17:13
clarkbya if we're deleting the branch it shouldn't be necessary. Would mostly be a safety net for when we don't delete the branch17:13
elodclarkb: i can add that to the process steps (between 2 and 3) if you agree17:13
clarkbprobably just focus on the branch deletion and that is more important17:14
elodclarkb: here I mean: https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life17:14
clarkbya that alreadys says the branch should be deleted so we should be ok17:15
clarkbjust need to follow the process17:15
*** tonyb has quit IRC17:15
elodclarkb: ack17:15
elodclarkb, fungi:  so I guess we can wait for the RC and then delete cinder's stable/ocata and stable/pike17:16
fungithat works for me17:20
elodok, thanks for the clarification, I'll answer to clarkb's mail on the mailing list that let's wait for the RC17:23
elodjust to have it there, too :)17:24
*** xek has quit IRC17:25
*** dmellado has quit IRC17:27
openstackgerritClark Boylan proposed openstack/project-config master: Pause image builds on nb04.opendev.org  https://review.opendev.org/75106617:31
*** Lucas_Gray has joined #openstack-infra17:42
*** dmellado has joined #openstack-infra17:46
*** tonyb has joined #openstack-infra17:57
*** thiagop has joined #openstack-infra17:59
*** thiagop has quit IRC18:04
*** thiagop has joined #openstack-infra18:05
*** artom has joined #openstack-infra18:09
*** gmann is now known as gmann_afk18:11
*** andrewbonney has quit IRC18:13
openstackgerritMerged openstack/project-config master: Pause image builds on nb04.opendev.org  https://review.opendev.org/75106618:14
smcginnisfungi: Wow, I had never noticed the Issues and Proposed changes links on opendev.org repos. Was that always there?18:31
clarkbsmcginnis: they've been there for a while18:31
fungismcginnis: maybe 6 months or so18:31
smcginnisHuh18:31
clarkbbut weren't there when we first rolled out gitea18:31
smcginnisI like it.18:32
fungithanks! i don't think i implemented either of those things, but just nice to see a service i help run get some compliments occasionally18:34
*** artom has quit IRC18:43
clarkbI think ttx did that work (at least for the changes)18:44
fungithat sounds right18:48
*** rfolco has joined #openstack-infra18:54
*** piotrowskim has quit IRC18:54
*** smarcet has joined #openstack-infra18:56
*** rfolco|ruck has quit IRC18:56
*** hashar has joined #openstack-infra19:01
*** xek has joined #openstack-infra19:07
AJaegerclarkb: yes, that thread19:10
*** rfolco is now known as rfolco|ruck19:12
*** priteau has quit IRC19:16
AJaegerconfig-core, please review https://review.opendev.org/750941 https://review.opendev.org/748712 https://review.opendev.org/749834 https://review.opendev.org/750643 https://review.opendev.org/75087819:16
*** hamalq_ has joined #openstack-infra19:23
*** hamalq has quit IRC19:24
*** ralonsoh has quit IRC19:27
*** slaweq has quit IRC19:53
clarkbI've approved https://review.opendev.org/#/c/750941/2 and we should try to remembre that if job runtimes get worse that may be one to revisit19:53
clarkb(it converts swap file creation from fallocate to dd)19:54
openstackgerritMerged openstack/openstack-zuul-jobs master: configure-swap: Always use dd and limit swap size to 1024MB  https://review.opendev.org/75094120:05
openstackgerritMerged openstack/project-config master: Retire devstack-plugin-pika project  https://review.opendev.org/74871220:05
AJaegerthanks, clarkb20:05
*** matt_kosut has quit IRC20:06
*** xek has quit IRC20:08
openstackgerritMerged openstack/openstack-zuul-jobs master: Remove legacy-tempest-dsvm-zeromq-multibackend  https://review.opendev.org/75087820:10
openstackgerritMerged openstack/project-config master: Add openstack/osops  https://review.opendev.org/74983420:18
openstackgerritMerged openstack/project-config master: Set neutron-lib stable ACLs  https://review.opendev.org/75064320:18
*** hashar has quit IRC20:33
*** openstackgerrit has quit IRC20:36
*** dklyle has quit IRC20:40
*** david-lyle has joined #openstack-infra20:40
*** artom has joined #openstack-infra20:46
*** thiagop has quit IRC20:55
*** outbrito has joined #openstack-infra20:55
*** david-lyle is now known as dklyle20:56
*** rfolco|ruck has quit IRC21:00
*** jtomasek has quit IRC21:11
*** outbrito has quit IRC21:11
*** openstackgerrit has joined #openstack-infra21:20
openstackgerritSean McGinnis proposed openstack/openstack-zuul-jobs master: Run openstack-tox-lower-constraints on bionic  https://review.opendev.org/75110721:20
*** gfidente|afk has quit IRC21:21
*** rosmaita has joined #openstack-infra21:37
rosmaitahello infra people21:39
clarkbhello21:39
rosmaitacan i get some eyes on: https://review.opendev.org/#/c/751107/ ?21:39
rosmaitathis is why:21:39
rosmaitahttps://zuul.opendev.org/t/openstack/builds?job_name=openstack-tox-lower-constraints&project=openstack%2Fcinder&branch=master21:39
clarkbthta makes sense21:40
rosmaitayes, and we are seriously stuck right at feature freeze time21:41
rosmaitagmann has been trying to sort out what the problem is, our py38 job runs fine in focal, but when the lower-constraints job runs those same tests, no dice21:42
smcginnisThere are a bunch of other repos failing now because of running on focal too.21:42
clarkbits because you specifically run on python3.6 in the job but python3.6 doesn't exist on focal21:43
clarkbERROR: InterpreterNotFound: python3.621:43
rosmaitathat was from an experiment21:43
smcginnisProblem was running under py38.21:43
rosmaitawe just use basepython=python3 normally21:43
clarkbis there a specific failure that is representative then?21:43
clarkbit could be that the constraints set a version that explicitly doesn't work with 3.821:44
clarkbusually we have version specific constraints to deal with that21:44
rosmaitahttps://review.opendev.org/#/c/743080/21:44
clarkbbecause constraints for 3.6 may be different than 3.821:44
smcginnisWell, part of this too is lower-constraints should be testing our minimum versions, so it kind of doesn't make sense to run on the highest version runtime we have.21:45
clarkbandopening logs hasused all the memory again. I really need a new laptop21:45
rosmaitai think sean's patch makes sense in general21:46
rosmaitabut at least it can get cinder un-hosed for a while, while we figure out what to do next21:47
clarkbya I think it does too, but your lower constraints should be publised for each python version iirc21:47
fungiyeah, some of the py36 and py37 jobs got pinned to ubuntu-bionic already, but possible some were missed21:47
clarkbwhoch means there should be a working list for 3.6 and 3.821:47
rosmaitaclarkb: you mean in the cinder l-c we should be distinguishing 3.6 and 3.8?21:48
clarkbrosmaita: yes mit probably already does21:48
smcginnisclarkb: Two sets of lower-constraints?21:49
*** Goneri has quit IRC21:49
clarkbno, one set with python version specific constraints21:49
smcginnisI suppose we could denote ;python_version=3.621:49
smcginnisYeah21:49
clarkbwe've already been doing that fir a while21:49
smcginnisThat makes sense.21:49
rosmaitawell, i guess i could take our current l-c file and append ;python_version=3.6 to each line21:50
smcginnisWe can run py38 on bionic, right? We could test things that way.21:50
clarkbI think so? you shouldn't need to though, you can make a variant of the constraints job that runs on focal21:51
clarkbis the job timeout representative of the issue?21:51
rosmaitano21:52
clarkbis there a link to the issue then?21:52
rosmaitahttps://review.opendev.org/#/c/743080/21:53
rosmaitathere's a comment about what we tend to see when the job doesn't time out21:53
clarkbcan you link to the job? I started there and it took me to a timeout job21:53
rosmaitalooking21:53
rosmaitahttps://c8a82e6058c8d023a45b-f54a194f01fabbfbf1677f1f837bd08c.ssl.cf2.rackcdn.com/743080/9/check/openstack-tox-lower-constraints/b080b14/testr_results.html21:54
clarkbthanks21:54
rosmaitawhen it doesn't time out, we see these21:54
rosmaitabut not the same jobs each time21:55
rosmaitai mean tests21:55
smcginnisAnd weird behavior from stestr that it prints out Captured stdout and Captured stderr for every individual test.21:56
smcginnisAnyway, several repos have this issue, so I think keeping this job on bionic for now is the best bet.21:56
smcginnisThen we can look at adding version flags to the lower-constraints.21:56
smcginnisTraditionally, we didn't have that in those constraints files. But we've done that for upper-constraints, so no reason we can't.21:57
smcginnisAnd then it's even more betterer for telling downstream what our expected ranges are.21:57
fungithe other thing which didn't really get tackled as part of this transition is that the normal python3.6 jobs should move to centos-8, because ubuntu-bionic is not an official tested runtime platform for victoria21:58
fungipython3.6 was kept as a tested python runtime for victoria because it's what's in centos-8, so continuing to test it on ubuntu-bionic makes very little sense21:59
rosmaitawe could try smcginnis's patch specifying centos-8 nodes and see what happens22:00
smcginnisfungi: Is the node name centos-8?22:00
fungiyes22:00
fungii honestly have no idea if anybody's even tested doing that22:00
rosmaitait will be interesting to see what happens22:00
openstackgerritSean McGinnis proposed openstack/openstack-zuul-jobs master: Switch py36 jobs to centos-8  https://review.opendev.org/75111222:01
fungibecause for ussuri we had python3.6 jobs since they were the default python3 on ubuntu-bionic22:01
smcginnisPretty sure it fill fail a lot of places. I've seen a lot of bindep.txt files that don't specify rpms.22:01
fungihowever it gets tricky, because stable/ussuri should almost certainly continue to test py36 on ubuntu-bionic, but we haven't previously made distro-specific python unit test jobs (at least not in any widespread manner)22:02
sorrisonanyone around to help me with a zuul v3 config question? I have a job that inherits from devstack-tempest but I don't want it to run the multinode-bridge ansible role defined in the multinode job that is inherited from. Can I disable it somehow instead of reinventing the whole hierarchy22:02
clarkblooking at the subunit file it almost looks like its the test harness that may be failing?22:02
clarkbsmcginnis: rosmaita basically oyu get a test failure that ran in 0 seconds and with no additional details22:02
openstackgerritSean McGinnis proposed openstack/openstack-zuul-jobs master: Switch py36 jobs to centos-8  https://review.opendev.org/75111222:03
clarkbsmcginnis: rosmaita: it might be worth running those tests without stestr and see if there is anything suspicous about the output22:03
clarkbsorrison: that role acts on particular ansible groups, I think if you drop those groups it will noop22:03
clarkbsorrison: that is how it noops on the single node jobs iirc22:04
fungiwhich is likely easier than having to fork an ancestral job and descent from that22:04
*** rlandy has quit IRC22:04
clarkbsmcginnis: rosmaita: also maybe check if it is always those jobs that have trouble22:04
sorrisonclarkb: Ah ok, thanks, I'll look into that22:04
rosmaitaclarkb: well, we know it's something about the l-c, because our py38 unit tests are basically the same job, and they run fine in focal22:05
sorrisonclarkb: I'm a bit of a ansible newbie, do you happen to know of some example you can point me to?22:05
sorrisonI know I need to drop the switch and peers group, just not exactly sure how22:06
openstackgerritSean McGinnis proposed openstack/openstack-zuul-jobs master: Switch py36 jobs to centos-8  https://review.opendev.org/75111222:06
clarkbsorrison: https://opendev.org/openstack/devstack/src/branch/master/.zuul.yaml compare single node and 2 node nodesets in that file22:08
clarkbbasically oyu remove the switch and peers group entries22:08
clarkbrosmaita: I might even juts try something as simple as bumping python-subunit and testtools in lower-requirements for python3.822:10
sorrisongreat, thanks, so I basically define my own nodegroup with the same name22:10
clarkbsorrison: you might need to use a different name and tell the job to use the different name22:10
clarkbsorrison: but yes make a new nodeset and use that22:11
sorrisonok cheers22:11
clarkbsorrison: out of curiousity why not set up the shared networking ?22:12
sorrisonclarkb: this is for a networking-midonet job, the vxlan interface that is created conflicts with midonet vxlan for some reason I don't understand22:14
sorrisonessentially doing a `sudo ip l del vxlan_sys_4789` inside the multinode job fixed it so I was just trying to do it in a nicer way22:15
clarkboverlapping with the vxlan ids maybe?22:17
clarkbwe do some large offset to avoid what neutron uses by default which is to start low and increment from there iirc22:17
rosmaitaclarkb: bumped those both up to what's in u-c, let's see what happens22:18
sorrisonclarkb: yeah maybe, I'm no networking expert but from what it looks like midonet tries to control it all, it expects to have free reign I think22:19
clarkbthe problem that bridge is trying to solve is that dependingon the cloud our test nodes may get a /32 network or no ipv6 at all etc22:20
clarkbwhat that bridge does is create an l2 network across the hosts that can be used to work around that if necessary22:21
clarkbor if you just need an l2 network22:21
*** vishalmanchanda has quit IRC22:21
sorrisonyeah ok, don't think we need an of that for this case22:21
sorrisonI have access to a couple nodes put on hold for me which I've been testing with22:22
*** zzzeek has quit IRC22:26
*** zzzeek has joined #openstack-infra22:27
*** Lucas_Gray has quit IRC22:35
*** sreejithp has quit IRC22:38
*** tosky has quit IRC22:42
*** gmann_afk is now known as gmann22:49
rosmaitaclarkb: no luck with bumping testtools and subunit22:50
clarkbrosmaita: was it the same tests? and any more debugging info with newer tools?22:50
rosmaitano, different tests but in that same general area22:52
rosmaitafungi: how do you feel about https://review.opendev.org/#/c/751107/1 ?22:54
*** rcernin has joined #openstack-infra22:58
*** rcernin has quit IRC22:59
*** rcernin has joined #openstack-infra22:59
openstackgerritMerged openstack/openstack-zuul-jobs master: Run openstack-tox-lower-constraints on bionic  https://review.opendev.org/75110723:04
rosmaitaworks for me!23:07
*** smarcet has quit IRC23:07
gmannclarkb: fungi rosmaita smcginnis i think we should run l-c on Focal. replied no review -https://review.opendev.org/#/c/751107/123:17
clarkbgmann: yes that is what I was saying, but I think for now not doing so isn't a major risk23:17
clarkbsince focal is newer we can expect newer deps there23:18
gmannit can break many projects where Focal fixes are merged and if those constraint re not present in Bionic23:18
gmannit can make all ongoing and already merged work back to bionic then23:19
clarkbgmann: we need constraints for both versions of python23:20
clarkbwe've done that with upper constraints for many relases now iirc23:20
gmannyou mean two jobs then23:20
clarkbnot sure about lower23:20
clarkbmaybe, I'm not sure if we tested uppet constraints with all of the python versions23:20
clarkbbut we list them all23:20
gmannbut default should be what distro we have right23:21
gmannand we can add another job if we want to add 3.6 constraints checks also23:21
clarkbyes, I think once the issue is sorted out switching back to 3.8 is sensible23:21
clarkbif we're deciding thats the primary platform (iirc 3.6 is still supported)23:22
gmannyou mean cinder issue?23:22
clarkbgmann: yes, but they said it affects other projects too23:22
gmanni do not think so. only cinder and keystone are failing which i am debugging currently. many other projects ~200 repos have been merged to fixes and were running on focal but now back to bionic23:23
gmannand can fail many of newer added version are not on Bionic23:23
clarkbgmann: I was going off what I was told "21:42:31        smcginnis | There are a bunch of other repos failing now because of running on focal too."23:24
*** zzzeek has quit IRC23:24
gmannhumm. as per my status in last email i listed the repos failing or under fix. and those are very few and more than 200 repo were fixed and working fine23:25
gmannheat has been fixed in morning too23:25
openstackgerritGhanshyam Mann proposed openstack/openstack-zuul-jobs master: Revert "Run openstack-tox-lower-constraints on bionic"  https://review.opendev.org/75111623:25
gmannclarkb: ^^ i am reverting it to avoid breaking the more things than solving/.23:26
gmannand let's fix cinder and keystone and other if there is any23:26
clarkbsmcginnis: ^ any clarification on what the other repos are?23:27
clarkbgmann: do we know why l-c is failing? I looked at it briefly and it appears that subunit isn't recording anything23:27
gmannthis is cinder and keystone in-progress fixes  https://review.opendev.org/#/c/743080/ https://review.opendev.org/#/c/743117/1123:27
gmannclarkb: keystone failing on some sql things and cinder facing some timeout in tests which is caused by one of the package seems23:28
fungiyou've basically got a revolt on your hands because projects are dealing with a flood of changes for feature freeze, and to them getting features finished for what they've promised will be included in the release is more important than making sure their jobs test what we've said we'll be releasing platform support for23:28
*** zzzeek has joined #openstack-infra23:29
clarkbfwiw I do think there is something to the argument that lower constraints should be tested with the oldest python23:29
fungiso folks need to decide whether they want to release software which will only work on outdated platforms or software which has to punt features to a future cycle23:29
clarkbso in this particular case I don't think we're violating the ensur jobs test what we've said we'll release for23:29
clarkband the correct way to address conflicts between lower values for python3.8 and 3.6 is to use env markers which upper constraints do23:30
fungifair, the question i suppose is whether lower-constraints also indicates installation on an older system23:31
gmannwe have fixed almost ~80% of the repo (till today) to make it work on Focal, not sure reverting it to Bionic is good or not breaking.23:31
clarkbgmann: right I think l-c is a bit of an exception is what I'm saying23:32
clarkbsince its specifically there to test the oldest versions of thing we support23:32
clarkbfor everything else I agree23:32
gmannoldest versions of thing on runtime distro version right? or any distro version ?23:33
clarkbgmann: the supported runtimes which are currently 3.6 and 3.823:33
clarkbpreviously it was just 3.6 so it was a bit simpler23:33
gmanni mean Distro version Ubuntu Focal or Bionic becasue 3.8 on bionic is different then 3.8 on Focal23:34
fungiwell, "3.6" in ussuri meant ubuntu-bionic23:34
clarkbgmann: well in thiscase it would be centos8 3.6 and focal 3.8 as fungi pointed out23:34
clarkbfor the current release23:34
fungi"3.6" in victoria supposedly means centos-823:34
fungibut jobs aren't currently set up to split py36 jobs for ussuri and victoria to different platforms23:35
gmannok, we can discuss this how we should do but for Focal migration can we proceed with 3.8 and keep all fixed things and not reverting them ?23:35
gmannand we can make it clear how we should test l-c when two  different python versions supported in testing runtime23:36
gmannbut for now i thin we should not change what already done23:36
clarkbagain in tis case I think this is a fix because smcginnis' argument that lower constraints should test the oldest python is a good one imo23:36
clarkbthe job is there specifically to test that the old stuff still works23:37
fungii'm willing to side with the qa team for now as the tc has theoretically delegated project-wide testing decisions to them, but ultimately concerns with their choice need to be taken up with the tc i guess23:37
clarkbthats fair23:37
clarkbgmann: can you communicate with them that this is just as important as theirfeatures ?23:38
gmannwhom? project side23:38
fungiand if cinder wants a cinder-specific lower-constraints job which runs on bionic rather than using the standard one, then i'm for that too and they and qa can bring their respective concerns over each choice to the tc23:38
clarkbyes cinder and whoever else has broken l-c jobs23:38
gmannok but for then we need to revert it and if we are not able to solve it on time then it is fair as fungi suggested to keep their job on bionic instead of  moving back all23:40
gmannbecause now in-progress fixes started running  on bionic and cannot be continued23:41
clarkbgmann: you can run the job on focal until it is ready23:41
clarkb(same thing the other way around as I mentioned in my commnt on your change)23:42
gmannlet me add their l-c on bionic and then we revert this so that all other projects keep doing on focal and i can work on fixes in paralell23:42
clarkbit may require a bit of template expansion but is doable23:42
fungiand yes, when there's more time for rational debate i do think deciding what the expected target platform for a typical lower-constraints job should ideally be would make a good topic (forum cfp is open through monday!)23:48
gmann+123:50
gmanni think we should discuss runtime testing things itself so that we can decide things are doable also.23:51
fungiit could warrant clarifying in the pti, and also is worth talking about whether lower-constraints jobs are expected to be kept stable on stable branches or can be removed sooner in the interest of dropping ancient node types from our ci system23:51
gmannespecially in current situation23:51
fungigmann: as smcginnis indicated, 751116 could use at least a sentence of rationale for the revert added to the commit message. then i'll approve it23:55
gmannfungi: yeah adding bionic version of l-c on cinder and keystone side. I will update the commit msg23:56
fungicool, thanks23:56
*** tetsuro has joined #openstack-infra23:58
smcginnisI do not think that should be reverted. This is an issue for a lot of folks, right when we should be locking things down and getting last minutes features landed. This was the absolute worst timing to switch the platform. The least we can do is still run lower-constraints on our lowest constraints.23:58
*** zzzeek has quit IRC23:58
clarkbsmcginnis: supposedly its just keystone and cinder?23:59
fungithere are "a lot of folks" working on keystone and cinder23:59

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