[00:51:36] !log tools.wikibugs Updated channels.yaml to: 1600f1be3b0432a920fd7258b6cbad4d3c9b2e0f Add additional ai-governance phab tag for #wikimedia-ai [00:51:39] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wikibugs/SAL [09:12:03] !log admin restarted the wmcs-backup service on cloudvirt1024 to retry the backups (failed because a VM was removed in-between, T276892) [09:12:07] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [09:12:07] T276892: wmcs-backups: handle VMs that are deleted between backups start and that VM backup - https://phabricator.wikimedia.org/T276892 [09:59:58] !log admin draining cloudvirt1037 (T275753) [10:00:01] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [10:54:36] !log admin rebooting cloudvirt1037 (T275753) [10:54:39] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [10:58:46] !log admin draining cloudvirt1038 (T275753) [10:58:49] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [12:33:43] !log admin rebooting cloudvirt1038 (T275753) [12:33:46] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [12:34:19] !log deployment-prep briefly rebooting VM deployment-db05, we need to reboot its hypervisor cloudvirt1038 and failed to migrate to other [12:34:24] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/SAL [12:34:44] !log tools briefly rebooting VM tools-docker-registry-04, we need to reboot the hypervisor cloudvirt1038 and failed to migrate away [12:34:46] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [12:52:32] !log admin cloudvirt1038 hard powerdown / powerup for T276922 [12:52:36] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [12:52:36] T276922: cloudvirt1038: PCIe error - https://phabricator.wikimedia.org/T276922 [13:21:35] !log admin add cloudvirt1039 to the ceph host aggregate (no longer a spare, we have cloudvirt1038 with HW failures) [13:21:38] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [13:31:44] !log tools hard-reboot tools-docker-registry-04 because issues related to T276922 [13:31:48] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [13:31:48] T276922: cloudvirt1038: PCIe error - https://phabricator.wikimedia.org/T276922 [13:32:03] !log deployment-prep hard-reboot deployment-db05 because issues related to T276922 [13:32:08] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/SAL [13:33:19] oh that's the beta cluster database master, fun [13:35:02] !log admin icinga-downtime cloudvirt1038 for 30 days for T276922 [13:35:05] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [13:38:45] Majavah: :-/ [13:38:59] !log admin draining cloudvrit1027 for T275753 [13:39:02] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [15:49:08] hello! Could anyone help me out with a toolforge question? When trying to increase the memory limit of a node service, does this command look correct? [15:49:15] webservice --backend=kubernetes --mem=2Gi node10 restart [15:49:22] Trying to verfiy it works with: [15:49:22] kubectl get pod {podName} --output=yaml [15:49:22] And still seeing resource memory as 512Mi [15:52:10] I don't think restart will work, I think you have to stop and start it again [16:00:22] nikkinikk: I think AntiComposite is correct. `webservice restart` will accept cli arguments like adjustments to the container quota limits, but those changes are not actually applied. `webservice stop; webservice ... start` should do what you expect. [16:06:03] AH THANK YOU that did it. [16:27:48] !log admin rebooting cloudvirt1027 (T275753) [16:27:52] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [20:22:59] Does anyone have a favorite recipe for setting up docker-compose managed services on a Debian Buster box? I hacked together a unit file to work with a single Docker container, but now I need to add 2 more containers and I'm thinking that docker-compose might be a reasonable way to do that. [20:23:31] So I thought I'd ask for crowd wisdom here before falling into my own research and development rabbit hole. [20:56:33] bd808: Tbh i've not done much with docker period, but I read some things on docker-compose and it sounds interesting. Maybe its worth the R&D?