Wednesday, 2024-06-05

tonybclarkb: the reviews seem good.   I have an idea to make things a little clearer.00:40
tonybclarkb: I'll look over the whole redirection process as it's somewhat confusing at best00:41
fricklerclarkb: I already deleted my autohold, so no blocker from my side07:43
fricklerif seems there are lots of stuck instances and images in that cloud, since it is going to be redeployed anyway, going ahead with the next cleanup changes should be fine I think07:52
opendevreviewBernhard Berg proposed zuul/zuul-jobs master: prepare-workspace-git: Add allow deleting current branch  https://review.opendev.org/c/zuul/zuul-jobs/+/91753909:40
opendevreviewJens Harbott proposed opendev/system-config master: Increase the number of mailman3 outgoing runners to 4  https://review.opendev.org/c/opendev/system-config/+/92076509:41
oschwarthey folks, good day. Can I ask zuul admins for an autohold, for this change https://review.opendev.org/c/openstack/designate-tempest-plugin/+/920653, this job designate-bind909:47
oschwartreason: I would like to debug this failure https://zuul.opendev.org/t/openstack/build/100d3262cda94ed2947435a353e5cf7e/console, I just got a 255 after I ran  subprocess.CalledProcessError, but I don't really know what happened there09:48
frickleroschwart: hold set up, we'll need your ssh public key later to give you access10:12
oschwartfrickler: sorry, I only see now that you recheck to hold the node https://review.opendev.org/c/openstack/designate-tempest-plugin/+/920653/comments/a7aacd7e_d4c26fac10:29
oschwartI uploaded another patch-set that prints additional exception details (maybe something will appear)10:30
oschwartfrickler: so as far as I understand, my new patch-set will trigger the same event as the recheck for the autohold, right? like we will still get it10:32
frickleroschwart: yes, the filter will match any patchset, and the next failing job will be held, regardless of how it was triggered10:39
oschwartfrickler: ack, thanks10:40
frickleroschwart: ssh root@104.239.136.190 should work for you now, let us know if you need more help or once you are done with debugging11:29
oschwartfrickler: I could ssh the host, thanks11:33
oschwartfrickler: how much time can I have that autohold? I would like to consult with a colleague that will start working soon12:38
frickleroschwart: any time you need, we'd likely start asking whether you stiil need to node after a week or so, but no real pressure anywhere12:49
oschwartgreat, thanks12:56
yoctozeptonebulous will be moving out of opendev because of the in-consortium pushback of the technology stack (gerrit, zuul, launchpad) being too different to the well-established, more-integrated, de-facto standard of github; fungi, clarkb, corvus, frickler and others - thank you for the common journey so far and here's hoping I get to play with the13:54
yoctozeptoopendev community in the future :-)13:54
Clark[m]frickler: yes, we can land the extra cleanup changes and then use nodepool erase when done if anything remains14:18
clarkbyoctozepto: thank you for the heads up. Maybe let us know when you aren't using zuul anymore (basically no more merging of stuff in gerrit) and we can wind down the zuul tenant14:40
clarkbI've approved https://review.opendev.org/c/openstack/project-config/+/921073 as the next step in inmotion cleanup14:46
opendevreviewMerged openstack/project-config master: Clean up diskimages from inmotion cloud  https://review.opendev.org/c/openstack/project-config/+/92107315:25
clarkbI'll check on that in a bit and continue to approve the other two changes if that looks good15:25
clarkblooking at the gerrit 3.9 to 3.10 upgrade logs it does look like the reindexing is done online. That should make the next upgrade straightforward from a reindexing standpoint15:33
clarkbthe only inmotion images left are in a deleting state. I guess we can proceed with the next change now15:51
clarkbI need to finish up some morning thigns then I'll approve that and get ready to run the erase command15:52
opendevreviewMonty Taylor proposed zuul/zuul-jobs master: Remove default value from ensure_nodejs  https://review.opendev.org/c/zuul/zuul-jobs/+/92106616:13
opendevreviewMonty Taylor proposed zuul/zuul-jobs master: Remove deprecated javascript jobs  https://review.opendev.org/c/zuul/zuul-jobs/+/92106716:13
clarkbI have approved https://review.opendev.org/c/openstack/project-config/+/921074 and will check the nodepool state after that applies16:40
clarkbtonyb: any cahnce you can review https://review.opendev.org/c/opendev/system-config/+/921075 it is the other step in inmotion cleanup16:40
opendevreviewMerged openstack/project-config master: Remove the inmotion cloud entirely  https://review.opendev.org/c/openstack/project-config/+/92107417:01
clarkbI think that applied cleanly. At least the nl02 logs lookabout how I woudl expect them to17:14
clarkbI've run the nodepool erase command which cleaned up the deleting nodes and images as expected. I did have to docker exec -it the command because it asks for confirmation. Took me half a second to realize that was why it threw an exception first17:17
clarkbtonyb: https://review.opendev.org/c/opendev/system-config/+/921075 is next up if you have time to review that17:17
tonybclarkb: done17:37
clarkbthanks I think that gets us in a state where I can tell yuriys we're ready for them to do the clodu side changes when I talk to them later today17:44
fungiyoctozepto: good luck! i just count myself lucky i get to work on projects who value open source services and aren't lured by the siren song of proprietary commercial services who leech off open source community efforts17:45
funginot everyone sees free/libre open source as a goal though, some only consider it a means to an end17:46
tonybclarkb: when you have the call details please pass them on.17:48
tonybclarkb: Are you okay with me +A'ing Fixups: for jitsi-meet | https://review.opendev.org/c/opendev/system-config/+/921320 ?18:08
clarkbtonyb: yup I don't expect that to have any issues18:18
opendevreviewMerged opendev/system-config master: Remove inmotion cloud management  https://review.opendev.org/c/opendev/system-config/+/92107518:56
opendevreviewMerged opendev/system-config master: Increase the number of mailman3 outgoing runners to 4  https://review.opendev.org/c/opendev/system-config/+/92076518:56
clarkbthe complaints from mailman are due to the database image being updated and the service losing connectivity to it. I don't think we've applied the new extra config data yet and that is unrelated. Working to confirm this19:55
clarkbnevermind looks like services all restarted just now and the new instances count is there19:55
clarkbit must've updated the db first before stopping the other services, then noticed config updated and restarted everything?19:56
clarkbthose restarts are not fast, but web is responding for me again now19:58
fungiin the past we saw it send similar errors during a db container restart20:17
fungithough they were being sent to the wrong address previously and ended up kicked back as undeliverable a week later20:17
fungihopefully now they come through ~immediately instead20:18
*** dasm is now known as Guest871620:46
Clark[m]Yes I think it was immediate based on docker timestamps 21:36
clarkbinfra-root I followed up to the thread with yuriys with the two things they wanted from us to start setting up the new cloud. The first thign is ssh keys which I pointed to in our config management. The other is a list of email addrs to create dashboard accounts in the system that manages the openstack stuff (so a level above openstack not horizon). I asked that each of us that wants23:05
clarkbone explicitly opt into that which you can do replying to my email in the thread23:05

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