Friday, 2023-03-03

ianwwhat's interesting is that if you don't have a submit-requirement; or it seems that a submit-requirement of "is:true" also does this -- the votes come up in the "trigger votes" section00:00
clarkbya I think a submit requirement is anything that must be satisfied to make teh change mergeable and a trigger requirement is anything else00:00
ianwyep, but i think it adds another layer of confusion to the whole thing00:01
clarkbyup especially since the trigger requirements are defined as submit requirements in the acls00:01
ianwright, i've given everything a submit-requirement, even if it's just "is:true", for consistency00:02
opendevreviewMerged opendev/system-config master: Add gitea10-12 to our inventory  https://review.opendev.org/c/opendev/system-config/+/87620200:04
clarkbyup just confirmed it will be a bit before that gets to the giteas. I'll keep an eye on it through my evening but with progressively less attention.00:05
clarkbAssuming they deploy as easily as gitea09 this should be fine though00:05
opendevreviewIan Wienand proposed opendev/system-config master: doc/gerrit : update copyCondition  https://review.opendev.org/c/opendev/system-config/+/87623600:09
opendevreviewIan Wienand proposed opendev/system-config master: doc/gerrit : update to submit-requirements  https://review.opendev.org/c/opendev/system-config/+/87623700:09
opendevreviewIan Wienand proposed opendev/system-config master: doc/gerrit : update to submit-requirements  https://review.opendev.org/c/opendev/system-config/+/87623700:58
clarkbianw: I had a mini panic that I forgot to accept the ssh hostkeys on bridge, but I guess the new ansible host keys content takes care of that because is all fine01:42
clarkbtesting it it all works without my previous intervention. Thats awesome01:43
opendevreviewSteve Baker proposed openstack/diskimage-builder master: A new diskimage-builder command for yaml image builds  https://review.opendev.org/c/openstack/diskimage-builder/+/87624503:07
opendevreviewIan Wienand proposed openstack/project-config master: gerrit/acl : submit-requirements for deprecated NoOp function  https://review.opendev.org/c/openstack/project-config/+/87580403:42
opendevreviewIan Wienand proposed openstack/project-config master: gerrit/acl : add submit requirements to NoBlock labels  https://review.opendev.org/c/openstack/project-config/+/87599303:42
opendevreviewIan Wienand proposed openstack/project-config master: gerrit/acl : handle key / values with multiple =  https://review.opendev.org/c/openstack/project-config/+/87599403:42
opendevreviewIan Wienand proposed openstack/project-config master: gerrit/acl : Update Review-Priority to submit-requirements  https://review.opendev.org/c/openstack/project-config/+/87599503:42
opendevreviewIan Wienand proposed openstack/project-config master: gerrit/acl : Convert remaining AnyWithBlock to submit requirements  https://review.opendev.org/c/openstack/project-config/+/87599603:42
opendevreviewdaniel.pawlik proposed zuul/zuul-jobs master: Provide deploy-microshift role  https://review.opendev.org/c/zuul/zuul-jobs/+/87608107:44
opendevreviewdaniel.pawlik proposed zuul/zuul-jobs master: Provide deploy-microshift role  https://review.opendev.org/c/zuul/zuul-jobs/+/87608107:46
*** odyssey4me is now known as odyssey4me__10:58
*** odyssey4me__ is now known as odyssey4me10:58
*** jpena|off is now known as jpena11:00
opendevreviewEbbex proposed openstack/diskimage-builder master: Fix double-keyed json  https://review.opendev.org/c/openstack/diskimage-builder/+/87629211:04
*** odyssey4me is now known as odyssey4me__11:06
*** odyssey4me__ is now known as odyssey4me11:06
*** odyssey4me is now known as odyssey4me__12:02
bbezakis there any problems with this host? Server Error (\"Get \"https://mirror.iad3.inmotion.opendev.org:4447/v2/\": dial tcp 173.231.253.126:4447: connect: no route to host\")\\n'13:51
bbezakwill recheck my job, but I recall there were issues with it recently?13:52
mnasiadkafungi: is that possible that mirror is down again? ;-)14:13
fungiit just came up in the release meeting as well, i'm checking to see if the server spontaneously died again14:14
fungiOS-EXT-STS:power_state=Shutdown14:15
fungii'll start it again, but we should probably take the region out of service until someone can look into why that vm keeps getting turned off by nova14:15
fungi#status log Booted mirror.iad3.inmotion via Nova API after it was found in power_state=Shutdown since 13:39:47 UTC14:18
opendevstatusfungi: finished logging14:18
opendevreviewJeremy Stanley proposed openstack/project-config master: Revert "Revert "Temporarily stop booting nodes in inmotion iad3""  https://review.opendev.org/c/openstack/project-config/+/87636514:23
fungiinfra-root: ^14:23
Clark[m]I think you can go ahead and self approve that one. Also for everyone else looking at this problem all of our mirrors are externally available which allows you to check if this is consistent and reproducable 14:25
fungiwith the caveat that the name nodes usually access our mirrors in rackspace by aren't externally reachable, but there are externally-reachable names for them14:31
fungibut this case wasn't in rackspace anyway14:31
opendevreviewMerged openstack/project-config master: Revert "Revert "Temporarily stop booting nodes in inmotion iad3""  https://review.opendev.org/c/openstack/project-config/+/87636515:03
clarkbI'm catching up on email and some paperwork then I'm going to start on gitea brain transplants for gitea10-12. Hoping to get a change up to replicate to them today16:48
fungithanks!16:57
*** jpena is now known as jpena|off17:21
dtantsurcould someone try https://zuul.opendev.org/t/openstack/build/1b381b57ef304017b772da1b91d7839a, is it ridiculously slow for everyone or just me?17:21
dtantsurI mean, it opens, but even selecting text takes many seconds17:22
yoctozeptodtantsur: same here, overloaded DOM17:24
dtantsuryeah. it probably does not like large job outputs.17:24
fungiideally, redirect some of the noisier but less frequently referenced output to separate log files and collect those instead of having it all in the stdout/stderr stream17:30
yoctozeptofungi: hi! so we would prefer a separate tenant... how do I go about this? my guess is that I should adapt my change (https://review.opendev.org/c/openstack/project-config/+/876054) to include the creation of the zuul config repo and then it should be configured properly, right?17:30
yoctozeptodtantsur, fungi: as a matter of fact, that's what kolla has done and we have improved the speed of loading of these pages17:30
yoctozeptofungi: (continued) and then only create the tenant17:31
dtantsurfungi: that's just a tox unit test job...17:31
fungiyoctozepto: yes, we don't create new tenants very often, so it's possible we may have to break up the tenant creation and project addition changes separate, but testing should tell us one way or another17:31
yoctozeptoI see17:31
yoctozeptowhat testing do you mean?17:31
fungiyoctozepto: the tests we run on proposed changes to our configuration17:32
yoctozeptoah, this validation17:32
yoctozeptobut it's optimistic as far as I can tell, right?17:32
yoctozeptoit just tries to lint and weed out obvious deviations?17:32
yoctozeptoand only after merge we learn the truth17:33
* yoctozepto trying to wrap his head around these things to be a better opendev citizen17:33
fungiwell, i think the tenant config additions will run additional deployment test jobs, not positive17:33
yoctozeptook, then I will try this in one go and then we iterate on that17:34
fungiprobably we need to create the repositories in gerrit, then add the zuul tenant and can add the projects to it when we do that17:34
fungior we could create the zuul tenant with no projects in it, then create the projects, then add them to the tenant... but that's more changes i think17:35
fungiclarkb: ^ do you recall if there's any reason not to create repositories and then create the tenant with the projects added to it at the same time?17:35
fungibasically same as creating repositories and then adding them to an existing tenant, just you're also creating the new tenant in the second change17:37
clarkbgive me a few minutes then I can page things in17:37
fungibasically change #1 is to add the projects in gerrit/projects.yaml and their acls in gerrit/acls, then change #2 is to add the tenant and its projects in zuul/main.yaml17:39
fungithen once #1 deploys successfully, #2 can merge17:39
yoctozeptoyeah, that was my initial idea17:39
yoctozeptoso maybe I will go with this one17:40
yoctozeptoI will send a stack of patches soon17:40
yoctozeptojust need to handle one other thing17:40
fungiof the projects in change #1, one of them will need to be the new config project which contains your base job, pipeline definititions, nodesets, and so on17:40
fungibootstrapping a tenant may require we bypass zuul to merge the initial configuration in the config repo, i don't remember, but seems like there's a walkthrough of the steps in the zuul docs17:42
fungibecause config projects can't run proposed configuration, and without configuring the tenant you won't be able to merge any changes to the config repo for it17:42
fungiso there's an interim step to add a gate pipeline which just runs the builtin noop job17:43
fungiyeah, https://zuul-ci.org/docs/zuul/latest/tutorials/quick-start.html#configure-a-base-job details bypassing zuul in order to merge the base job change in the tenant's config repo17:46
fungier, wrong section, it's https://zuul-ci.org/docs/zuul/latest/tutorials/quick-start.html#configure-a-base-job to merge the pipeline configuration17:48
fungigah, pasted from the wrong buffer17:48
fungihttps://zuul-ci.org/docs/zuul/latest/tutorials/quick-start.html#configure-zuul-pipelines17:48
clarkbfungi: I think they are separate to prevent zuul errors17:48
fungiright17:49
clarkbfungi: zuul will clone the repos and you want ot nesure they are all present first17:49
clarkbalso lets not land those things today so that I can safely perform gitea brain surgery17:49
clarkbat least let me get that done first which is next on my todo list I think17:49
fungiwell, sure, i don't expect to merge them today17:49
yoctozeptogitea brain surgery sounds interesting17:52
clarkbyoctozepto: the easiest way to preserve historical project redirects in gitea is to transplant the database from an old server to a new server17:54
clarkbso thats what I'm doing for the new gitea servers I'm building17:54
yoctozeptoI see, sounds tedious tbh17:55
opendevreviewRadosław Piliszek proposed openstack/project-config master: Add the main NebulOuS repos  https://review.opendev.org/c/openstack/project-config/+/87605417:56
yoctozeptomeh, forgot the ACLs17:57
opendevreviewRadosław Piliszek proposed openstack/project-config master: Add the main NebulOuS repos  https://review.opendev.org/c/openstack/project-config/+/87605418:00
opendevreviewRadosław Piliszek proposed openstack/project-config master: Add the NebulOuS tenant  https://review.opendev.org/c/openstack/project-config/+/87641418:09
opendevreviewRadosław Piliszek proposed openstack/project-config master: Add the main NebulOuS repos  https://review.opendev.org/c/openstack/project-config/+/87605418:11
opendevreviewRadosław Piliszek proposed openstack/project-config master: Add the NebulOuS tenant  https://review.opendev.org/c/openstack/project-config/+/87641418:11
opendevreviewClark Boylan proposed opendev/system-config master: Replicate Gerrit repos to gitea10-12  https://review.opendev.org/c/opendev/system-config/+/87641918:23
clarkbinfra-root ^ please check gitea10-12 and if they look good I think we can land ^ to start replication18:24
yoctozeptofungi, clarkb: it seems there is no relevant validation to the tenant config - at least in the check pipeline - it passes happily with not-yet-existent repos18:32
clarkbya its done by zuul when it relaods its config which is why we have been cautious in the past18:33
yoctozeptofingers crossed then18:33
clarkbthose errors probably won't break zuul today though but once upon a time zuul was less able to handle errors loading base tenant configs? Either way I think splitting up the merges and making sure things are happy at each step is a good idea18:33
yoctozeptoyeah, I agree18:34
yoctozeptobetter to first create the repos, ensure they are there18:34
yoctozeptothen create the tenant18:34
yoctozeptoreload as need18:34
yoctozeptoed18:34
yoctozeptocheck again if it works18:34
yoctozeptoand then worry about other things18:34
fungiclarkb: gitea10-12 lgtm19:08
clarkbfungi: thanks. Its probably unlikely that anyone else would get to reviewing it today. Should we go ahead and approve it?19:11
fungii have done so now19:18
clarkbthanks!19:18
clarkbone thing I was looking for to check the redirects was a redirect due to a project rename and not an org move but I couldn't find any of those19:18
fungiforgot it's friday already (so saturday on the other side of the sphere). where has this week gone19:18
clarkbits been a quick one19:18
fungiproject rename... yeah i'm not sure we've done anything besides namespace moves since going from cgit to gitea19:19
fungiclarkb: oh! x/devstack-plugin-topiko -> x/devstack-plugin-tobiko maybe?19:22
fungiit was a typo correction, but presumably reflected in the redirects19:22
clarkblooking19:23
fungialso found openstack/charm-lxd -> openstack/charm-nova-lxd19:24
clarkbyup the topiko one redirects as expected19:24
fungiso there are some, just not many19:24
clarkbhttps://gitea10.opendev.org:3081/x/devstack-plugin-topiko19:24
clarkbwill take you to x/devstack-plugin-tobiko19:24
opendevreviewMerged opendev/system-config master: Replicate Gerrit repos to gitea10-12  https://review.opendev.org/c/opendev/system-config/+/87641919:36
clarkbhrm ^ didn't trigger a gerrit update?19:43
clarkbI see the issue19:43
clarkbwe had the same issue with gitea08 and I thought I fixed it but I hadn't...19:45
clarkbanyway change shortyl19:45
opendevreviewClark Boylan proposed opendev/system-config master: Fix infra-prod-service-review file matchers  https://review.opendev.org/c/opendev/system-config/+/87643019:48
clarkbfungi: ^19:48
fungioh right20:07
fungialso infra-prod-base failed, i'm checking logs now20:22
fungimirror01.regionone.osuosl.opendev.org "Failed to update apt cache: E:Failed to fetch http://ddebs.ubuntu.com/dists/focal-proposed/main/binary-arm64/Packages.xz  File has unexpected size (38816 != 38444). Mirror sync in progress?"20:23
fungia manual apt update doesn't error for me20:26
fungimust have been temporary20:26
Clark[m]Lunch now, but that happened yesterday too. It went away when I tried manually and on the next run20:33
fungiyeah, i remember that20:47
yoctozeptowhat's the plan to merge the addition of the new project?21:18
clarkbyoctozepto: I think we can probably land things early next week once we've stabilized the new giteas?21:20
clarkbthe next step is replicating all of the git repos to them from gerrit21:20
fungiand then usually we get two reviewers to go over the changes so we don't miss anything21:20
clarkbonce that is done it should be fine to add new projects21:20
yoctozeptoack, thanks21:22
clarkbfungi: once gerrit replication configs update I'll trigger replication for bindep against the three new servers to ensure general functioning then trigger global replication for the three21:34
clarkbthat will liekyl take the better part of the next 24 hours21:34
clarkbbut we should be in a good spot on monday to put them behind haproxy and pull out some of the old servers21:34
fungisounds good21:40
clarkbyoctozepto: the spelling of this word is such that I feel I need to check every occurrence of it to ensure we didn't swap an 'o' and a 'u' anywhere21:46
opendevreviewJulia Kreger proposed openstack/diskimage-builder master: Correct boot path to cover FIPS usage cases  https://review.opendev.org/c/openstack/diskimage-builder/+/87619222:12
opendevreviewMerged opendev/system-config master: Fix infra-prod-service-review file matchers  https://review.opendev.org/c/opendev/system-config/+/87643022:17
clarkbbindep replication seems to have gone well. I'm going to trigger full replication for those three nodes now22:48
clarkbI was going to shutdown gitea on gitea08 at this point but I'm fairly certain our daily jobs will just turn it back on again22:50
clarkbInstead I'll work on removing it and 05-07 together as the next step in this process22:50
fungiyeah, as long as it's out of the haproxy and replication config it should be fine until we can delete it22:52
clarkbya I think remove 05-07 from haproxy, then remove 05-07 from gerrit replication, then remove 05-08 from inventory, then delete 05-08 are the next steps22:54
clarkband they are all waiting on replication to run first22:55

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