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.:
- update to Plesk Obsidian Version 18.0.46
- then try to update to Plesk Obsidian 18.0.46 #Update 1 or execute as root:
ACTUAL RESULT
Plesk update fails
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
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
- 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