[08:00:28] <wm-bot2>	 Cteam: welcome to today 🦄! Don’t forget to post your update in thread.
[08:00:28] <wm-bot2>	 Feel free to include:
[08:00:28] <wm-bot2>	 1. 🕫 Anything you'd like to share about your work
[08:00:28] <wm-bot2>	 2. ☏ Anything you'd like to get help with
[08:00:28] <wm-bot2>	 3. ⚠ Anything you're currently blocked on
[08:00:28] <wm-bot2>	 (this message is from a toolforge job under the admin project)
[09:19:58] <dcaro>	 Done:
[09:19:58] <dcaro>	 * Still catching up
[09:19:58] <dcaro>	 Doing:
[09:19:58] <dcaro>	 * Moved another one of the repos to gitlab flows (registry-admission) (T341084)
[09:19:58] <dcaro>	 * Will start with reviews
[09:19:58] <stashbot>	 T341084: [toolforge] Move all the components to the gitlab ci/cd flow - https://phabricator.wikimedia.org/T341084
[09:19:59] <dcaro>	 Blockers:
[09:19:59] <dcaro>	 * None
[10:17:16] <dhinus>	 Working on: checking what is left before T319401 can be resolved. Opening some new phabs as a follow-up.
[10:17:17] <stashbot>	 T319401: Improve how we run WMCS cookbooks - https://phabricator.wikimedia.org/T319401
[13:23:49] <andrewbogott>	 yesterday: Very long, fruitless debug session trying to figure out what's happening with leaked cinder-backup snapshots. I see the rpc call to delete being sent but the volume service never seems to get them.
[13:26:12] <dcaro>	 http?
[13:44:50] <andrewbogott>	 A certain set of snaps are 'cursed' and the volume service never hears about them. If I create a /new/ snapshot the whole process works fine. So it's not a network connectivity issue.  Something in between my loglines (don't know if client or server) must be deciding that these particular snaps can't be deleted and is ignoring the call
[14:18:54] <dcaro>	 oh, that sounds like an unhandled exception being silently ignored or similar in the code