• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs Plesk update fails because of repository check

Hangover2

Regular Pleskian
Username:

TITLE


Plesk update fails because of repository check

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.46, Debian 10.12, x86-64

PROBLEM DESCRIPTION

Since "Plesk Obsidian 18.0.46" we cannot update our Plesk servers anymore. It fails because the repository check script throws an error concerning our buster-backports source, that is only used to have the latest kernel available on our systems.

STEPS TO REPRODUCE

- add buster-backports to your sources.list, e.g.:
Code:
deb http://deb.debian.org/debian buster-backports main contrib non-free
- update to Plesk Obsidian Version 18.0.46
- then try to update to Plesk Obsidian 18.0.46 #Update 1 or execute as root:
Code:
/root/parallels/pool/PSA_18.0.46_9656/examiners/repository_check.sh

ACTUAL RESULT

Plesk update fails
Code:
/root/parallels/pool/PSA_18.0.46_9656/examiners/repository_check.sh: 289: local: buster-backports/main: bad variable name

EXPECTED RESULT

Plesk update should be possible. We did use the backports source also in the past without having any update issues. We know it is not officially supported by Plesk but we would love to see the same update behavior like before.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Backport repositories are not supported by Plesk to avoid potential stability risks.
To keep Plesk updated, disable backports.
 
Hello @IgorG ,

nevertheless the script is broken now. Before Plesk Obsidian 18.0.46 a proper warning was shown, e.g.:

Code:
/root/parallels/pool/PSA_18.0.45_9299/examiners/repository_check.sh

Plesk installation doesn't support 'Debian Backports/buster-backports/non-free' OS repository.
Make sure it is disabled, then try again.

As a consequence the nightly auto-installer fails generating an error log. Also the one-click update via Plesk dashboards fails the same way.

A workaround for now is the "Custom Installation", that still works by confirming the output of the repository check can be ignored.
 
As a possible workaround, you can create /tmp/plesk-installer-skip-repository-check.flag file to skip repository checks.
 
Since Plesk Obsidian 18.0.47 no error or warning is shown anymore. But the installer does silently just comment out our not supported sources without any hint or confirmation needed from our side.

Changelog Plesk Obsidian 18.0.47:

A comprehensible error message is now shown when updating Plesk fails because there are one or more unsupported repositories configured on the server. (PPPM-13716)

This does definitely not happen. We will file a new bug report soon.
 
Back
Top