• 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 installer does silently comment out sources

Hangover2

Regular Pleskian
Username:

TITLE


Plesk installer does silently comment out sources.

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.47, Debian 10.12, x86-64

PROBLEM DESCRIPTION

Since "Plesk Obsidian 18.0.47" the Plesk installer does silently comment out sources (that are not supported) without any prior notice or warning.

STEPS TO REPRODUCE

- add not supported sources to /etc/apt/sources.list
Code:
deb http://deb.debian.org/debian buster-backports main contrib non-free
- upgrade Plesk Obsidian 18.0.47 to Update #1 or Update #2
- check /etc/apt/sources.list

ACTUAL RESULT

Code:
# deb http://deb.debian.org/debian buster-backports main contrib non-free

EXPECTED RESULT

Code:
deb http://deb.debian.org/debian buster-backports main contrib non-free

ANY ADDITIONAL INFORMATION

Problem is maybe related to the following issue solved in 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)

Now no error message is shown anymore at all. Also the confirmation dialogue from the past does not show up.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
This is expected behavior for backports repositories.

Below is “Backports” definition from Debian.org: Debian Backports:
“Backports cannot be tested as extensively as Debian stable, and backports are provided on an as-is basis, with risk of incompatibilities with other components in Debian stable. Use with care!”

That’s why we do not support “backports” and do not recommend it: this repository doesn’t improve security but brings potentially untested changes to the production server.

Backports repository is disabled during Plesk installation. You could enable it back at your own risk.
 
If this is the new expected behavior it would be nice for the Plesk users to be informed about it in the changelog or by a new warning before the upgrade process. Also in the past before Plesk Obsidian 18.0.46 the admin could decide whether or not to take the risk.

Workaround to avoid the new behavior: create /tmp/plesk-installer-skip-repository-check.flag file to skip repository checks and automatic changes to your server sources.
 
Back
Top