Tuesday, 2025-08-12

opendevreviewGoutham Pacha Ravi proposed openstack/project-config master: Retire Monasca project  https://review.opendev.org/c/openstack/project-config/+/95706304:51
opendevreviewGoutham Pacha Ravi proposed openstack/project-config master: Retire Monasca project  https://review.opendev.org/c/openstack/project-config/+/95706304:59
opendevreviewGoutham Pacha Ravi proposed openstack/project-config master: Retire Monasca project  https://review.opendev.org/c/openstack/project-config/+/95706305:01
mnasiadkaIs it just me - or creating a revert using Gerrit UI is broken now, even if I add signed-off-by header in the commit message?07:17
mnasiadkaHmm, worked after I did add a whitespace before the header and revert reason07:17
mnasiadkas/whitespace/newline/07:18
opendevreviewSimon Westphahl proposed zuul/zuul-jobs master: Add default for build diskimage image name  https://review.opendev.org/c/zuul/zuul-jobs/+/95621910:03
fungimnasiadka: yes, that first line (or block of lines) is the subject of the commit, the last block of lines is the trailer, everything in between is the commit message body. those sections are separated by blank lines13:16
fungicorrectly formatting commit messages is important, even just for readability, but especially when it comes to satisfying message parsers13:17
mnasiadkafungi: maybe the template should include Signed-off-by: <PUT YOUR NAME AND EMAIL HERE>?13:24
mnasiadka(for revert)13:24
fungii don't know if it's configurable at all in gerrit, but if it is then we'd need a way to configure it independently per-project since only openstack repositories require signed-off-by13:26
fungior at least not all projects hosted in opendev require it at any rate (some besides openstack also do, but not all)13:27
Clark[m]My personal opinion on that is if the Gerrit UI doesn't do the exact specific thing you want for revert/rebase/etc you really should be using git locally and pushing the result once confirmed to be the exact specific desired output13:33
fungi#status log Deleted the eavesdrop01.opendev.org server instance, which was replaced by eavesdrop02 last week13:33
Clark[m]The Gerrit UI tools are there for the simple case. Git on your local machine allows you to do whatever specific thing you want 13:33
opendevstatusfungi: finished logging13:34
fungiinfra-root: remember we also need to merge https://review.opendev.org/956832 to clean up the dns records for eavesdrop0113:34
fungi#status log Deleted the refstack01.openstack.org server instance (serving the old refstack.openstack.org site) per https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/WNI4PE2TZ3G52C3U5FT2YNVRUAJB3CMO/13:36
fungii did make sure the snapshot for that one ^ is showing completed in rackspace first13:37
opendevstatusfungi: finished logging13:37
fungiso if we need to bring it back for some reason we still have the old rootfs13:37
opendevreviewMerged opendev/zone-opendev.org master: Clean up old eavesdrop01 records  https://review.opendev.org/c/opendev/zone-opendev.org/+/95683214:53
fungithanks!14:56
fungifrickler: are you okay un-wip'ing https://review.opendev.org/c/opendev/zuul-providers/+/956428 Revert "Disable openmetal provider"15:42
fungiyesterday was the end of the maintenance schedule15:42
clarkbfor some reason I had it n my head that it was the 13th but you're right. Reading the email it was yesterday (the 11th)15:42
fricklerfungi: can you check whether the mirror is running fine before we merge that?15:42
fungialready did15:43
fungiand i removed it from our emergency disable list too15:43
fricklerah, cool, fine to go then15:43
fungithanks!15:44
fungiapproved it just now15:46
opendevreviewMerged opendev/zuul-providers master: Revert "Disable openmetal provider"  https://review.opendev.org/c/opendev/zuul-providers/+/95642815:46
mnasiadkaIs it just me seeing occasional "Server Unavailable" from Gerrit UI for the last couple of months?16:58
clarkbmnasiadka: that happens to me when my local wifi connection bounces17:01
mnasiadkaI don't think that's the case, everything else works, I see that also from office - so two independent locations17:02
clarkbI think gerrit notices because it checks for udpates to changes in the background and when that connection breaks it notices when other things would only notice if you ask for an explicit update17:02
clarkbbut no other than ^ I haven't noticed anything new along those lines17:03
fungii haven't seen it, but i mostly don't use the webui17:04
fungii've deleted the refstack-related records out of openstack.org dns now too (a, aaaa, cname, and also two cnames for acme challenges)18:55
clarkband we never had opendev.org records for that service so that should be all the dns18:56
fungiright19:01
fungido our test node names still start with "np"? ovh just sent us an incident notice with a list of np... instances impacted20:59
clarkbfungi: yes its np and then a suffix. That suffix was a sequential id number from 0 to current boot in nodepool. With zuul launcher its a uuid of some sort so more random21:07
fungiokay, just making sure those weren't necessarily old leaked instances21:07
corvusyep.  the "np" is so that we can guess that it's probably a nodepool instance21:19
corvusthe suffix is the first N characters of the full node id21:19
corvusso np3062cf3cb3bd4 is node uuid 3062cf3cb3bd482c98b379491d8235e421:22
corvusyou can just grep for 3062cf3cb3bd4 on the launchers and that's typically unique enough.  that would get you the active timespan for when we owned it.21:22
clarkbcorvus: does zuul support both ansible 8 and 9 now or just 9?21:40
clarkbI'm trying to get facts straight for this announcement email21:40
clarkbI think it is just ansible 9 within oepndev's deployment because we are deploying master21:40
clarkbthat detail doesn't change things dramatically I'm going with the just 9 and 11 case (no 8) as I believe that to be correct21:45
clarkbhttps://lists.opendev.org/archives/list/service-announce@lists.opendev.org/thread/EUTEAOIUQZ6YJUQWD75QO34H5TDGBLKP/21:47
clarkbremote:   https://review.opendev.org/c/openstack/tempest/+/957186 DNM Test devstack and tempest with Ansible 11 in Zuul21:49
clarkband there is a canary for devstack and tempest21:49
fungicorvus: thanks, i just didn't know if we'd switched prefixes when we dropped nodepool21:50
opendevreviewClark Boylan proposed opendev/infra-specs master: Add spec to use Matrix for OpenDev comms  https://review.opendev.org/c/opendev/infra-specs/+/95482622:05
clarkbok I think we just found an ansible 11 problem: https://zuul.opendev.org/t/openstack/build/9c11103ca84646cca286931f824f4d2d/log/job-output.txt#1103-1112 due to https://github.com/ansible-collections/openvswitch.openvswitch?tab=readme-ov-file#open-vswitch-collection22:09
clarkbthe code is here: https://github.com/ansible-collections/openvswitch.openvswitch/blob/main/plugins/modules/openvswitch_bridge.py and it is gplv3 licensed. It is for testing only purposes in a zuul-jobs role. Should we maybe just vendor it?22:10
clarkbcorvus: ^ thoughts on doing that?22:10
clarkbThen for buildkit mirror configuration we set that via buildkitd.toml: https://docs.docker.com/build/buildkit/configure/#registry-mirror Looks like we're already configuring that via https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/use-buildset-registry/tasks/main.yaml#L77-L90 and22:16
clarkbhttps://opendev.org/zuul/zuul-jobs/src/branch/master/roles/use-buildset-registry/library/modify_buildkitd_toml.py so I think we're good. But I'm trying to understand what sort of toml that produces before being sure22:16
clarkbyes I believe that should produce valid config. And that role already sets things up for quay.io22:18
clarkbtl;dr I think our younger selves were way ahead of future us and configured buildkit appropriately22:19
clarkband buildkit is the default image builder as of docker 23.0. We use the latest version by default which is newer than that22:20
opendevreviewClark Boylan proposed zuul/zuul-jobs master: Vendor openvswitch_bridge  https://review.opendev.org/c/zuul/zuul-jobs/+/95718822:35
clarkbI'm going to go ahead and propose vendoring the code because I'm curious to see if it is compatible with newer ansible (I suspect so but am not 100% certain)22:36
corvusclarkb: back -- vendoring somewhere sgtm... aiui that's a general role to set up multi-node bridging which is why it's in zuul-jobs and why you'd vendor that to zuul-jobs.  but it's probably worth spending a couple of seconds thinking about whether that should go in openstack-zuul-jobs.22:37
clarkbcorvus: yes exactly. The idea is to have a batteries included role for zuul that sets up an overlay network so that you can control l2 and up for your multinode jobs22:38
clarkbI'm not sure it makes sense to move into openstack-zuul-jobs unless we remove that role from zuul-jobs entirely22:39
clarkb(because the role will break as soon as zuul drops support for ansible 9(22:39
corvusagree22:39
corvus(i was thinking about both)22:39
clarkbI don't think openstack would have any problems with hosting that role for themselves if removed from zuul-jobs22:40
corvussounds like there's 2 issues: 1) that role is not included in ansible anymore.  2) that role is being abandoned.  vendoring is a fix for 1... but are we setting ourselves up for indefinite maintenance of that because it's abandoned?  is that okay?  should we do something else?22:40
clarkbmy cynical take on 2) is that red hat is pushing hard to get everyone to use ovn intsead of ovs22:41
clarkbaiui ovn uses ovs under the hood. Ovn does not make sense for this setup as its a more complete network including dns and dhcp etc22:41
clarkbwe want something minimal that jobs can build on top of to potentially test dhcp clients or servers22:42
corvushttps://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/1522:43
clarkbwhich is to say I think ovs is going to stick around and likely continue to have stable interfaces but I guess there is no garuntee. Then on the other side of things we would potentially have to update the module if the internal ansible module interfaces change22:43
corvusclarkb: ^ that thread is worth a read22:43
corvushttps://github.com/ansible-collections/openvswitch.openvswitch/blob/main/meta/runtime.yml#L222:44
corvusthe collection specifies <2.18 (== ansible 11).  that's pointed out in some commits from that thread22:45
corvusi don't know if that means "really won't work with" or just means "we stopped caring 2 years ago and don't want to deal with it"22:45
clarkbya it isn't clear if that was their line in the sand or an actual compatibility issue22:45
clarkbI'm hoping that my proposed change helps shake some of that out22:45
corvus++ good chance it's just line-in-the-sand22:46
clarkbas far as other choices go we could look at uses linux bridge again. In the past we didn't use linux bridge because we needed to support protocols that run over tcp or udp eg vxlan not gre22:46
clarkbI want to say on our side this all originated before linux bridge could speak vxlan and thus we used ovs. I think linuxbridge can use vxlan now and the new thing too (geneve)22:47
clarkbwe may also consider wireguard though I think having extra security garuntees from wireguard is overkill22:47
opendevreviewClark Boylan proposed zuul/zuul-jobs master: Vendor openvswitch_bridge  https://review.opendev.org/c/zuul/zuul-jobs/+/95718822:48
clarkbthe upside to linuxbridge is that its very standard on linux and doesn't really rely on any tooling that what yuo'd alredy expect to have on your linux install for network configuration22:50
clarkband maybe we keep using vxlan for compatibility with older kernels?22:51
clarkbthinking out loud here: maybe the best thing to do would be to have openstack vendor the openvswitch stuff if it works. Then essentially mark the zuul-jobs role as non working and needing a rewrite to linuxbridge. if /when someone rewrites the zuul-jobs role we can drop the vendoring in openstack?22:51
clarkbthis assumes that vendoring works. If vendoring does not work then we'll need to do the rewrite anyway22:52
corvusnot a bad idea, but maybe still less effort to just vendor it in zuul-jobs and still declare it deprecated and in need of a rewrite22:56
clarkbya maybe we do that if this minimal vendoring just works22:56
clarkbthere is a linter error I'll need to address but that is minor22:58
opendevreviewGoutham Pacha Ravi proposed openstack/project-config master: Retire Monasca project  https://review.opendev.org/c/openstack/project-config/+/95706323:12
fungilooking at the ansible version announcement, are we skipping over 10 or can jobs be configured to use that as well?23:19
corvusskipping 1023:30
clarkbhttps://zuul.opendev.org/t/openstack/build/b9cc67956b504c07bc32c7f14dad6aea/console this build failed after my vendor of openvswitch_bridge. But I've just spent like 5 minutes reading through logs and I think ansible was fine. This seems to eb a legit failure23:31
corvushttps://zuul-ci.org/docs/zuul/latest/config/job.html#attr-job.ansible-version which clark included in the announcement also confirms the two available versions23:32
clarkbstill waiting on other multinode jobs to complete, but it is a good sign that they didn't retry failure loop23:33

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