Project

General

Profile

Actions

tickets #167359

closed

mailing lists interface down?

Added by meissner@suse.de 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Mailing lists
Target version:
-
Start date:
2024-09-25
Due date:
% Done:

0%

Estimated time:

Description

hi,

lists.opensuse.org interface seems down

https://lists.opensuse.org/manage/lists/security-announce.lists.opensuse.org/held_messages

"We are very sorry, but the requested service is currently not
available."

Ciao, Marcus


Related issues 1 (0 open1 closed)

Precedes openSUSE admin - tickets #167362: Avoid package removals on automatic update download failureResolvedcrameleon2024-09-26

Actions
Actions #1

Updated by crameleon 4 months ago

  • Category set to Mailing lists
  • Private changed from Yes to No
Actions #2

Updated by crameleon 4 months ago

  • Status changed from New to In Progress
  • Assignee set to crameleon
Actions #3

Updated by crameleon 4 months ago

  • Status changed from In Progress to Resolved

Interesting:

Sep 25 01:26:08 mailman3 systemd[1]: Starting Update of system...
Sep 25 01:26:17 mailman3 os-update[19993]: Retrieving repository 'openSUSE:infrastructure' metadata [.error]
Sep 25 01:26:17 mailman3 os-update[19993]: Repository 'openSUSE:infrastructure' is invalid.
Sep 25 01:26:17 mailman3 os-update[19993]: [openSUSE:infrastructure|http://download-prg.infra.opensuse.org/repositories/openSUSE:/infrastructure/openSUSE_Tumbleweed/] Valid metadata not found at specified URL
Sep 25 01:26:17 mailman3 os-update[19993]: History:
Sep 25 01:26:17 mailman3 os-update[19993]:  - [|] Error trying to read from 'http://download-prg.infra.opensuse.org/repositories/openSUSE:/infrastructure/openSUSE_Tumbleweed/'
Sep 25 01:26:17 mailman3 os-update[19993]: Please check if the URIs defined for this repository are pointing to a valid repository.
Sep 25 01:26:17 mailman3 os-update[19993]: Warning: Skipping repository 'openSUSE:infrastructure' because of the above error.
Sep 25 01:26:27 mailman3 os-update[19993]: Retrieving repository 'openSUSE_infrastructure_mailman3' metadata [.error]
Sep 25 01:26:27 mailman3 os-update[19993]: Repository 'openSUSE_infrastructure_mailman3' is invalid.
Sep 25 01:26:27 mailman3 os-update[19993]: [openSUSE_infrastructure_mailman3|http://download.infra.opensuse.org/repositories/openSUSE:/infrastructure:/mailman3/openSUSE_Tumbleweed/] Valid metadata not found at specified URL
Sep 25 01:26:27 mailman3 os-update[19993]: History:
Sep 25 01:26:27 mailman3 os-update[19993]:  - [|] Error trying to read from 'http://download.infra.opensuse.org/repositories/openSUSE:/infrastructure:/mailman3/openSUSE_Tumbleweed/'
Sep 25 01:26:27 mailman3 os-update[19993]: Please check if the URIs defined for this repository are pointing to a valid repository.
Sep 25 01:26:27 mailman3 os-update[19993]: Warning: Skipping repository 'openSUSE_infrastructure_mailman3' because of the above error.
Sep 25 01:26:36 mailman3 os-update[19993]: Retrieving repository 'repo-oss' metadata [.error]
Sep 25 01:26:36 mailman3 os-update[19993]: Repository 'repo-oss' is invalid.
Sep 25 01:26:36 mailman3 os-update[19993]: [repo-oss|http://download.infra.opensuse.org/tumbleweed/repo/oss/] Valid metadata not found at specified URL
Sep 25 01:26:36 mailman3 os-update[19993]: History:
Sep 25 01:26:36 mailman3 os-update[19993]:  - [|] Error trying to read from 'http://download.infra.opensuse.org/tumbleweed/repo/oss/'
Sep 25 01:26:36 mailman3 os-update[19993]: Please check if the URIs defined for this repository are pointing to a valid repository.
Sep 25 01:26:36 mailman3 os-update[19993]: Warning: Skipping repository 'repo-oss' because of the above error.
Sep 25 01:26:36 mailman3 os-update[19993]: Some of the repositories have not been refreshed because of an error.
Sep 25 01:26:36 mailman3 os-update[19993]: Loading repository data...
Sep 25 01:26:36 mailman3 os-update[19993]: Reading installed packages...
Sep 25 01:26:36 mailman3 os-update[19993]: Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this>
Sep 25 01:26:36 mailman3 os-update[19993]: Computing distribution upgrade...
Sep 25 01:26:37 mailman3 os-update[19993]: The following item is locked and will not be changed by any action:
Sep 25 01:26:37 mailman3 os-update[19993]:  Installed:
Sep 25 01:26:37 mailman3 os-update[19993]:   redis
Sep 25 01:26:37 mailman3 os-update[19993]: The following package is going to be REMOVED:
Sep 25 01:26:37 mailman3 os-update[19993]:   python3-mailman-web
Sep 25 01:26:37 mailman3 os-update[19993]: 1 package to remove.
Sep 25 01:26:37 mailman3 os-update[19993]: Package install size change:
Sep 25 01:26:37 mailman3 os-update[19993]:               |         0 B    required by packages that will be installed
Sep 25 01:26:37 mailman3 os-update[19993]:   -123.8 KiB  |  -  123.8 KiB  released by packages that will be removed
Sep 25 01:26:37 mailman3 os-update[19993]: Backend:  classic_rpmtrans
Sep 25 01:26:37 mailman3 os-update[19993]: Continue? [y/n/v/...? shows all options] (y): y
Sep 25 01:26:37 mailman3 [RPM][20065]: Transaction ID 66f366cd started
Sep 25 01:26:38 mailman3 [RPM][20065]: erase python3-mailman-web-0.0.9-81.2.noarch: success
Sep 25 01:26:38 mailman3 os-update[19993]: (1/1) Removing: python3-mailman-web-0.0.9-81.2.noarch [..
Sep 25 01:26:38 mailman3 os-update[19993]: warning: /etc/mailman3/settings.py saved as /etc/mailman3/settings.py.rpmsave
Sep 25 01:26:38 mailman3 [RPM][20065]: erase python3-mailman-web-0.0.9-81.2.noarch: success
Sep 25 01:26:38 mailman3 [RPM][20065]: Transaction ID 66f366cd finished: 0
Sep 25 01:26:38 mailman3 os-update[19993]: .done]
Sep 25 01:26:38 mailman3 os-update[19993]: Running post-transaction scripts [...done]
Sep 25 01:26:39 mailman3 os-update[19993]:
Sep 25 01:26:39 mailman3 os-update[19992]: ERROR: update failed, exit code was 106
Sep 25 01:26:39 mailman3 os-update[20227]: ERROR: update failed, exit code was 106

The download server failed (that's a separate issue I already noticed earlier but yet have to track), but instead of giving up with the dup zypper proceeded to remove a package? Can't quite explain that behavior.

I now applied the machine's highstate and it is back to the expected configuration.

Will check later and add a separate issue for investigating how we can avoid such update regressions upon download failure (ideas welcome).

Thanks for reporting,
Georg

Actions #4

Updated by crameleon 4 months ago

  • Precedes tickets #167362: Avoid package removals on automatic update download failure added
Actions

Also available in: Atom PDF