Wednesday, 2026-10-07

*** haleyb|out is now known as haleyb00:31
frickler#status notice zuul processing is broken since about 03:00 UTC, investigation is in progress, please be patient08:01
opendevstatusfrickler: sending notice08:01
-opendevstatus- NOTICE: zuul processing is broken since about 03:00 UTC, investigation is in progress, please be patient08:02
opendevstatusfrickler: finished sending notice08:04
*** tobias-u1 is now known as tobias-urdin08:19
*** mikal0 is now known as mikal08:57
stephenfinfrickler: fungi: Just because we've already had a few issues here, would it be worth a status update about pbr 7.1.3 being released?11:54
stephenfinsomething like: pbr 7.1.3 has been released. If you see packaging-related issues in CI, particularly for stable branches, please report them on #openstack-oslo ?11:55
fungistephenfin: maybe, though i did mention during the tc meeting yesterday to be on the lookout for it too13:42
stephenfinWith any luck, we won't see any issues and things will be rosy, but the fact we're on attempt no. 4 suggests we should be on the lookout13:44
stephenfinThe TC notification is probably good enough though. I'm sure people will find us if things do break13:44
tkajinamcould anyone add me to https://launchpad.net/~zaqar-drivers/+members as an admin ?14:12
tkajinamfungi, I'd appreciate it if you have a few minutes ^^^14:12
tkajinamI think none of the current admins is around the community these days14:13
fungitkajinam: your kajinamit account, not the takashi-kajinami one?14:14
fungii can't remember which one you're using now14:14
tkajinamfungi, yes kajinamit is the right one14:14
tkajinamI don't remember with which email address I create the other one but I believe that's also mine :-P14:14
fungithe other one is associated with a gmail address rather than ntt14:15
fungianyway, done, please double-check14:15
tkajinamfungi, thanks. it works14:17
tkajinamI assume we don't need the release team as its member so I'll deactivate it too14:17
fungitkajinam: yeah, unnecessary these days. once upon a time the release managers ran scripts that updated bug target milestones but that hasn't been the case for many, many years now14:27
bauzasfolks, do we still have zuul processing issue ? I want to recheck some change 14:47
bauzaswhen looking at https://zuul.opendev.org/t/openstack/status I see new changes in the check pipeline14:48
fricklerbauzas: there are capacity issues that affect only some special kinds of large nodes, but for general changes it should be fine to recheck14:58
melwitta while back I added a patch to devstack to collect guru meditation report on failed job runs (https://review.opendev.org/c/openstack/devstack/+/997443) and I thought to check on it today and find it's erroring out but there is almost no information in a job log for example https://zuul.opendev.org/t/openstack/build/72d39e4f417b4a2881d1382d803e8266/log/job-output.txt#4015115:11
melwittdoes anyone have any suggestion how to debug something like this?15:12
bauzasfrickler: ty, I'll recheck then15:17
fungimelwitt: i'd look at what commands `TASK [Collect Guru Meditation Reports from OpenStack services]` and then see if manpages for anything in there document an exit code of `-12` (which seems unusual so probably oddly specific to one particular command?)16:33
melwittgood point16:42
melwittthanks :)16:42
fungithere's also some chance that the exit code belongs to ansible rather than a command it ran, i don't really know16:43
fungimelwitt: oh, there's also task-specific details zuul records which you can browse in the console view, more than simple stdout/stderr, which may help speed up the investigation: https://zuul.opendev.org/t/openstack/build/72d39e4f417b4a2881d1382d803e8266/console#8/0/38/compute116:45
fungino idea if any of the additional detail there helps16:45
melwitta-ha, cool thanks16:46
fungiit at least records what was passed to ansible, which for a shell action includes the shell commands it would try to run, so less digging around in playbook/role definitions in git16:48
clarkbmelwitt: fungi that script doesn't look like it emits anything and isn't set -e. Basically the lack of a set -e and the last command being sleep make me suspicious it is running at all with an rc of -12. But without having some indication of it running at all (set -x may be a good idea) its hard to say16:53
clarkbso maybe add set -x and see if that sheds light on where it is going wrong? My suspicion is that maybe it is /bin/sh or even just cmd not shell and we're not able to run the command at all /me looks for the task definition16:54
melwittyeah, ok that is my bad. I'll propose a change to add set -x16:55
melwittI'm sorry I didn't do it originally 😩 16:55
clarkbhttps://opendev.org/openstack/devstack/src/branch/master/playbooks/post.yaml#L30-L31 ok it is bash so it should be capable of processing hte array16:55
clarkbso ya I would start with making the task a little more debuggable to try and track down where the rc -12 is coming from16:55
fungimaybe also consider `-e` and `-o pipefail` to short-circuit the script asap if it hits a problem rather than possibly resulting in misleading cascade failures for subsequent commands16:55
melwittgood call16:56
melwittthanks for the good ideas :)16:56
fungithough if you do that, you need to safeguard commands you expect to exit nonzero normally within the script too16:56
melwitt++17:10
opendevreviewClark Boylan proposed openstack/project-config master: Undefine zuul_site_mirror_fqdn on non x86_64 hosts  https://review.opendev.org/c/openstack/project-config/+/100932517:33
*** priteau_ is now known as priteau21:38

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