Project

General

Profile

tickets #95884

Mailman REST API not available

Added by AdaLovelace 11 months ago. Updated about 1 month ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Mailing lists
Target version:
-
Start date:
2021-07-22
Due date:
% Done:

0%

Estimated time:

Description

Collegues wanted to subscribe the zsystems mailing list via the web
interface:
https://lists.opensuse.org/archives/list/zsystems@lists.opensuse.org/

The first issue happens after clicking on "Manage subscriptions". You
are receiving the message "Something went wrong: Mailman REST API not
available. Please start Mailman core."

Then I recommended to test ist with an registered account. There is the
possibility to send an email via the web interface to the mailing list.
He is receiving a: "Can't connect to Mailman's REST server, your message
has not been sent."
The HTTP status code is 500.

History

#1 Updated by cboltz 11 months ago

  • Status changed from New to In Progress
  • Assignee set to hellcp

Looks like one of the updates installed today (python3-SQLAlchemy 1.3.22-lp152.4.3 -> 1.4.20-lp152.2.1 from devel_languages_python_backports) no longer liked our config file and broke startup of mailman :-(

After changing the database url from postgres: to postgresql: it works again :-)

The remaining question is why the mailman VM has the devel_languages_python_backports repo. In theory the VM is fully salted, but I can't see any mention of that repo in salt. Sasi, do you know why it was added?

#2 Updated by pjessen about 1 month ago

  • Status changed from In Progress to Feedback

Maybe it is time for some feedback?

#3 Updated by pjessen about 1 month ago

  • Private changed from Yes to No

#4 Updated by hellcp about 1 month ago

Yeah, it probably needs to be salted, but the much larger issue is how difficult operating with Leap's version of python has become now, to the point rebuilding mailman is starting to become real hard. We should consider Tumbleweed for both mailman machine and matrix machine to be able to update those services to the latest versions

#5 Updated by pjessen about 1 month ago

  • Status changed from Feedback to In Progress

hellcp wrote:

Yeah, it probably needs to be salted, but the much larger issue is how difficult operating with Leap's version of python has become now, to the point rebuilding mailman is starting to become real hard. We should consider Tumbleweed for both mailman machine and matrix machine to be able to update those services to the latest versions

Speaking for myself, I have no issue with that, provided we have people who can work with that. (I'm not one).

#6 Updated by cboltz about 1 month ago

No objections against Tumbleweed (but note that we'll need to adjust/version-switch some things in salt to match Tumbleweed, for example "usrfiles" in nsswitch.conf).

That said: Leap 15.4 comes with a python310 package, so it has at least the newer python interpreter and base modules. However, it looks like all the python modules are not packaged for python 3.10.

Also available in: Atom PDF