matrix bots currently broken #13347
Labels
No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#13347
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of request
I managed to break maubot. ;(
I noticed that the running pod was around 30days old, but I had deployed a bunch of changes for forge moves not long ago, so I had to deploy the latest version and it hits an odd traceback trying to run.
I then ran a undo on that, but the previous version (while not having errors) also doesn't want to run. ;(
I've asked @ryanlerch to look into it.
In the mean time, zodbot/nonbot/meetbot will be unresponsive. ;(
Still cannot figure it out -- it is having issues starting up the plugin instances (and has disabled them all)
When you try to start up any of the plugin instances you get the following traceback:
Cusriously, this is not happening on Staging, but only production
Some things i have checked:
github.com/fedora-infra/maubot-meetings@ff3ab78193but that wouldnt cause thisi now got it failing on both prod and stage, which is ... good?
ok, it turns out it was a bug when using newer versions of zope.interface in maubot plugins.
I have hotpatched maubot in the image that we build for our maubots on openshift, so they are working again now.
also, filed this issue upstream:
https://github.com/maubot/maubot/issues/282
HUm, seems the error is gone, but the meetbot plugin at least isn't working. ;(
[2026-05-18 15:02:34,635] [WARNING@maubot.instance.meetbot-meetings] Plugin disabled, not starting.
Ah, @abompard fixed it and showed me the interface to enable plugins. :)
All good now...