The issue was actually with tcpircbot on alert1001, not with dbctl (which is merely a client of tcpircbot).
Followups noted in-thread; tasks to be opened for them.
Original report below.
I just realised that when depooling/repooling hosts, dbctl is no longer doing a !log action on irc.
The change does work and the depooling/repooling happens fine.
This is an example of an action that worked but never got looged on irc:
root@cumin1001:/home/marostegui# dbctl instance db1112 depool root@cumin1001:/home/marostegui# dbctl config commit -m "Depool db1112 for schema change" eqiad/groupLoadsBySection/DEFAULT live eqiad/groupLoadsBySection/DEFAULT generated { { "contributions": { "db1112": 100 }, "dump": { "dump": { "db1166": 100 "db1166": 100 }, }, "logpager": { "db1112": 100 }, "recentchanges": { "db1112": 100 }, "recentchangeslinked": { "db1112": 100 }, "vslow": { "vslow": { "db1166": 100 "db1166": 100 }, "watchlist": { "db1112": 100 } } } } eqiad/sectionLoads/DEFAULT live eqiad/sectionLoads/DEFAULT generated [ [ { { "db1123": 0 "db1123": 0 }, }, { { "db1112": 400, "db1157": 500, "db1157": 500, "db1166": 300, "db1166": 300, "db1175": 500 "db1175": 500 } } ] ] Enter y or yes to confirm: y Previous configuration saved. To restore it run: dbctl config restore /var/cache/conftool/dbconfig/20210303-063846-marostegui.json WARNING:conftool.announce:dbctl commit (dc=all): 'Depool db1112 for schema change', diff saved to https://phabricator.wikimedia.org/P14580 and previous config saved to /var/cache/conftool/dbconfig/20210303-063846-marostegui.json
I manually tested the !log action and it did work: https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&type=revision&diff=1901444&oldid=1901443
[07:41:20] <marostegui> !log Testing log [07:41:25] <+stashbot> Logged the message at https://wikitech.wikimedia.org/wiki/Server_Admin_Log
Looks like the last successful logging from dbctl was this: