Thursday, 2024-09-26

frickleractually I'm only out after tomorrow, but cleaning up those holds is fine anyway03:59
opendevreviewTony Breeds proposed opendev/system-config master: Also include tzdata when installing ARA  https://review.opendev.org/c/opendev/system-config/+/92368407:21
opendevreviewTony Breeds proposed opendev/system-config master: Update ansible-devel job to run on a newer bridge  https://review.opendev.org/c/opendev/system-config/+/93053807:21
opendevreviewMerged opendev/irc-meetings master: Change to odd weeks for irc meetings for publiccloud-sig.  https://review.opendev.org/c/opendev/irc-meetings/+/93033409:24
Clark[m]A jitsi docker release just happened if anyone wants to try manually doing the update steps performed by our daily job maybe we can sort out the issue with updating those containers?14:15
fungitrying to recall what problem we've observed... container not starting correctly/at all?14:27
clarkbya its like it does an incomplete restart and something fails to come up14:50
clarkbso probably need to manually step through theansible actions to see where it goes sideways then hopefully determine a resolution14:51
fungiclarkb: this right? https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles/jitsi-meet/tasks/main.yaml#L83-L9015:05
fungiseems like there's an obvious step missing, or else docker-compose is smarter than i realize15:05
clarkbfungi: yup. And ya the down shouldn't technically be necessary with docker compose figuring out what needs to be stopped and then started but maybe that is what the problem is for some reason15:06
fungidoes up imply down first if the image has changed?15:06
clarkbyes15:06
clarkbonly for the updated images15:06
clarkband maybe if there are depenednecies of updated images? But maybe that is the issue some subtle bheavior where we really need to restart everythingand we are not?15:06
fungiokay. so yeah maybe that's it... basically i just need to log into the servers and do a pull followed by up and see if it breaks again?15:06
fungior should i try an explicit down before the up?15:07
clarkbfungi: maybe we do a pull, down, then up and if that works we just update the ansible to match?15:08
fungican do15:08
clarkbwe know the current ansible behavior is likely to leave things not working so if a different process gives us a working end result we can switch to that and see if it improves15:08
frickleralways doing the down would reset running calls, wouldn't it?15:08
clarkboh yes we need to check if the images updated15:09
clarkbthere are examples of that in other role15:09
fungihave we been seeing the same problem occur on both the primary and jvb servers?15:14
fricklerI only remember the meetpad server, but not too confident about it15:18
opendevreviewStephen Finucane proposed openstack/project-config master: Retire x/nova-lxd  https://review.opendev.org/c/openstack/project-config/+/93060015:24
opendevreviewStephen Finucane proposed openstack/project-config master: Retire x/nova-lxd  https://review.opendev.org/c/openstack/project-config/+/93060016:23
opendevreviewStephen Finucane proposed openstack/project-config master: Remove x/nova-lxd from zuul  https://review.opendev.org/c/openstack/project-config/+/93060016:24
opendevreviewMerged openstack/project-config master: Remove x/nova-lxd from zuul  https://review.opendev.org/c/openstack/project-config/+/93060016:51
fricklercorvus: not sure if you had seen this already, but https://review.opendev.org/c/opendev/sandbox/+/915197 broke .gitreview by reverting to an old repo name. it has since been fixed, but there still is an old link in the readme17:00
corvusack; maybe we should fix that and then make a safe tag that we can revert to17:01
fungiclarkb: i did a docker-compose pull on meetpad02 but it didn't say "downloaded newer image"17:37
fungii suppose it may have already pulled them down earlier?17:37
clarkbmaybe https://github.com/jitsi/docker-jitsi-meet/releases/tag/stable-9753 is what I got a notification for in email17:38
clarkbprosody has matchign images for that in docker hub17:38
fungidocker image list mentions images created 4 hours ago so that seems to correspond17:39
corvusdocker image ls says that there is a newer copy of all 4 images locally, from 4 hours ago17:39
clarkbfungi: if you do a `docker image list` the images did uget pulled17:39
corvusdocker inspect jitsi-meet-docker_web_1 says it's running the older image17:39
fungiyep, so it pulled the new images but didn't restart any containers17:40
corvusi would conclude the state is equivalent to docker-compose pull has been run but nothing else17:40
clarkbso either docker-compose isn't logging that anymore (but our experience with gitea upgrades yesterday indicates it must?) or something else pulled them?17:40
fungiyeah, i'm hesitant to make the restart conditional on output from the pull command if we have something else also pulling images17:40
clarkbI think more likely your pull did pull them17:41
fungii'll compare on jvb0217:41
fungiyeah, you're probably right, i only see the old image on jvb0217:42
clarkblet me dig up an exampel from gitea jobs for the command output17:43
clarkbbut docker-compose usually makes it pretty obvious if it is pulling something17:43
fungiis is what my terminal history looks like: https://paste.opendev.org/show/bPKTZBiMvftcGIrgl3pF/17:43
corvusif the goal is "update if there is a newer image" maybe instead of relying on the pull, we should do some api comparisons.  like "if the sha for the desired image tag does not match what the container is running, run down and up"17:43
fungimaybe i need to make it think it's not on a tty?17:43
corvusyou can get docker to spit out json and run that through jq to do things like that17:44
fungii wonder if docker-compose has magic "keep output pretty" functionality that hides download info17:44
clarkbhttps://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_5f3/930217/1/gate/system-config-run-gitea/5f3f224/bridge99.opendev.org/ara-report/results/259.html17:44
clarkbthe difference is having a term or not I Think17:44
clarkbif you watch it interactively it does say all that stuff but rather tahn scrolling output it is doing it in place17:44
fungii'll do a 2>&1|cat on jvb02 for confirmation17:45
clarkbyou're seeing just the last line for each image17:45
clarkbin your paste I mean17:45
fungiyeah, when i dump it through cat i do get all the lines rather than just the final one17:46
fungiPulling jvb ... status: downloaded newer image fo...17:46
opendevreviewJeremy Stanley proposed opendev/system-config master: Explicitly down Jitsi-Meet containers on upgrade  https://review.opendev.org/c/opendev/system-config/+/93063717:52
clarkbfungi: cool so doing a down and up after a pull caused everything to come up cleanly?17:53
fungiseems that way17:53
clarkbya docker ps shows things updated and I was able to join a room then quit without issue17:53
fungii didn't get any errors from the up -d on either server17:54
fricklerwhy is https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/930599/3 still failing? the depends-on is merged, the parent shows no errors18:01
clarkbhave we reloaded the zuul tenant to remove the project?18:03
clarkbit says last reconfigured 39 minutes ago /me does some math18:04
fungiits depends-on deployed to the server at 17:04, if that helps18:04
clarkb30 minutes ago was 17:34, 39 is 17:25. The recheck happened at 10:1918:04
fungi(probably slightly before, but that's when the deploy buildset reported)18:04
clarkbfungi: ya I think it takes about 20 minutes to full reload the tenant though which aligns with deploying at 17:04 and reloading the tenant at 17:2518:05
fungii agree18:05
clarkbanyway it may be worth rechecking one more time since the previous recheck was before the tenant reloaded. Then if it still fails we dig into logs18:05
corvusclarkb: mouseover the reconfigure time and you'll get the real time18:05
clarkboh cool 17:24 UTC ya18:05
corvus(every timestamp in zuul-web should have an absolute value)18:05
clarkboh its the parent change!18:06
clarkbhttps://review.opendev.org/c/openstack/openstack-zuul-jobs/+/930615 has  configuration error not the depends on18:06
fungiaha!18:06
fungithat explains it18:06
clarkbalso the fix is to put the one we're rechecking first18:06
fungithe parent was passing in check earlier, but something merged to break it18:06
clarkbyes nova-lxd was removed so we can't refer to it anymore which the change we were originally looking at should fix18:07
fungiright, didn't see that until i approved it moments ago18:08
fricklerthe parent didn't have the error when I looked at it, but that explains it, thx18:09
fungiyeah, the error wasn't reported on the parent until i hit approve on it18:11
fricklerbut I think this needs another cleanup patch, then, the error location isn't touched by 93059918:11
clarkbah yup looks like another job?18:13
clarkbactually no I think thats it18:14
clarkbI would rebase and flip the order of those two changes and see if zuul complains any further18:14
fricklerah, yes, I misread the zuul note. let me just shuffle things, needs some local editing due to conflicts18:17
NeilHanloninfra-root: though I'm sure it's not, one may want to uninstall cups from your servers if it's there.18:21
* NeilHanlon disappears into the night18:21
fungiaha, so that was the answer to the recent riddle18:24
fricklerreordering the stack seems to have severly confused gerrit's "Relation Chain" view :-/ I think I'll need to rebase the whole stack manually18:25
NeilHanlonfungi: at least partially, it seems. the disclosure has been moved up to... an hour from now18:57
NeilHanlonsomething something cat something something bag18:57
fungiindeed18:58
* fungi sighs18:58
fungiluckily i can't find anywhere we need to be concerned19:00
fricklersoomething like https://github.com/OpenPrinting/cups-browsed/issues/36 likely?19:00
Clark[m]Oh cool I get lunch early so I can go on a bike ride and the fun starts19:08
fungiin our case it seems to have been much ado about nothing19:12
mordredthe discussion in that PR is very respectful and productive19:15
mordreds/PR/issue/19:16
fungiisn't it tho19:17
clarkbdesktop flavors of various distro probably do have cups running though so check your laptops/desktops19:20
clarkbthe writeup is public now20:01
fungiwhee!20:03
NeilHanlonhttps://www.evilsocket.net/2024/09/26/Attacking-UNIX-systems-via-CUPS-Part-I/20:14
NeilHanlonweeee indeed20:14

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