#12781 HTTP 500 when viewing held messages for private list rocm-packagers-sig
Closed: Fixed by zlopez. Opened by tflink.

Describe what you would like us to do:


I've been trying to view the held messages for the private list rocm-packagers-sig for several weeks but every time I try to access the held messages through the admin interface, I get a http 500 error.

I'm able to access the held messages for other private lists so I assume that the problem isn't just with me but if that's not the case, please let me know what I'm doing wrong.

When do you need this to be done by? (YYYY/MM/DD)


It's not horribly urgent but 2025/09/23 would be great


Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, medium-trouble, ops

Here's the traceback:

2025-09-09 19:04:49 [FALCON] [ERROR] GET /3.1/lists/rocm-packagers-sig@lists.fedoraproject.org/held?count=10&page=1 => Traceback (most recent call last):
  File "falcon/app.py", line 365, in falcon.app.App.__call__
  File "/usr/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 189, in on_get
    resource = self._make_collection(request)
  File "/usr/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in _make_collection
    entries = [as_dict(resource) for resource in collection]
  File "/usr/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in <listcomp>
    entries = [as_dict(resource) for resource in collection]
  File "/usr/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 180, in _resource_as_dict
    assert resource is not None, resource
AssertionError: None

This looks like some metadata are missing in database for one or more of the held messages.

Issue tagged with: sprint-0

Metadata Update from @zlopez:
- Issue assigned to zlopez

I'm trying to understand what is happening here. From what I can see in mailman code it should return all the messages marked as held from db, which contains 17 messages. But for some reason instead of list of messages it returns None.

I will try to debug it a little more or there is an option to just clear the held queue.

Dug into it more and it seems that some of the held messages didn't really had resource in database (not sure how that happened, but after removing 7 messages causing the error the held messages queue was opened without issue.

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

Issue status updated to: Closed (was: Open)
Issue close_status updated to: Fixed

Issue status updated to: Open (was: Closed)

I can get into that interface and manage held messages now, thanks. There are a bunch of older messages (1 year old or so) which have been lost but I think that is to be expected and I need to be better about looking at those held messages :)

Thanks again for getting this fixed.

Metadata Update from @zlopez:
- Issue untagged with: sprint-0

Metadata