[08:00:02] <wm-bot2>	 Cteam: welcome to today 🦄! Don’t forget to post your update in thread.
[08:00:02] <wm-bot2>	 Feel free to include:
[08:00:02] <wm-bot2>	 1. 🕫 Anything you'd like to share about your work
[08:00:02] <wm-bot2>	 2. ☏ Anything you'd like to get help with
[08:00:02] <wm-bot2>	 3. ⚠ Anything you're currently blocked on
[08:00:02] <wm-bot2>	 (this message is from a toolforge job under the admin project)
[09:20:55] <dcaro>	 Hmpf... forgot to hit enter...
[09:20:56] <dcaro>	 Done:
[09:20:56] <dcaro>	 * [api-gateway] fix the api version generation (now it's stable, interesting lru_cache issue https://gitlab.wikimedia.org/repos/cloud/toolforge/api-gateway/-/merge_requests/49)
[09:20:56] <dcaro>	 * [api-gateway] fixed the url in the openapi yaml
[09:20:56] <dcaro>	 * [toolforge,api] added api.svc.toolforge.org and api.svc.beta.toolforge.org DNS records
[09:20:56] <dcaro>	 * [lima-kilo] toolforge_deploy_mr will not handle the chart repository too if needed (for MRs it should always be toolsbeta)
[09:20:56] <dcaro>	 * [toolforge,o11y] fixed the grafana dashboard for users (k8s namespaces), kube-system-metrics had deprecated some of the metrics we were using to list namespaces
[09:20:57] <dcaro>	 * [toolforge,jobs] fixed an issue with a worker stuck on NFS that was also not reporting to prometheus, it was in 'migrating' state in openstack and that makes it not get picked up by prometheus
[09:20:57] <dcaro>	 Doing:
[09:20:58] <dcaro>	 * [components-api] working on getting an async client, did a try with generation, but it puts a pin on pydanticv1 (when v2 is needed for things like pydantic-settings and others), so might instead give a try to adding an async client to toolforge-weld (using httpx)
[09:20:58] <dcaro>	 * [toolforge,jobs-api] did some tests on how to unblock people that get jobs stuck by NFS, the only method that seems to work is using `activeDeadlineSeconds` or `concurrencyStrategy: Replace`, will do another round to `livenessProbe` though I suspect that will only restart the container and not move the pod to another node
[09:20:59] <dcaro>	 * [toolforge] trying to get some hints on how many tools were 'given up on' by users https://phabricator.wikimedia.org/T379144
[09:20:59] <dcaro>	 Blockers:
[09:21:00] <dcaro>	 * [api-gateway] Enable pass-through of deployment urls with token auth to the components api (https://gitlab.wikimedia.org/repos/cloud/toolforge/api-gateway/-/merge_requests/51)
[09:21:46] <dcaro>	 * [components-api] Add created_at field to deploy tokens (for expiration, https://gitlab.wikimedia.org/repos/cloud/toolforge/components-api/-/merge_requests/31)
[09:21:46] <dcaro>	 * [components-api] Add token validation (https://gitlab.wikimedia.org/repos/cloud/toolforge/components-api/-/merge_requests/32)
[09:21:46] <dcaro>	 * [components-api] Rename deployment token to deploy token (small refactor, https://gitlab.wikimedia.org/repos/cloud/toolforge/components-api/-/merge_requests/35)
[13:44:03] <dhinus>	 Done:
[13:44:05] <dhinus>	 * T379076 delete tf-infra-test and tf-infra-dev projects
[13:44:07] <dhinus>	 * created T379159 add komla to wmcs-roots
[13:44:09] <dhinus>	 Working on:
[13:44:11] <dhinus>	 * T375479 NodeDown alerts, merging and testing the last patches
[13:44:13] <dhinus>	 * T375223 putting cloudvirt1063 back in service