Improve wording and always block if Katello was configured

This commit is contained in:
lumarel 2021-06-21 22:50:40 +02:00
parent ad5f8b2e27
commit 9a6ad7a5f2
2 changed files with 6 additions and 7 deletions

View File

@ -24,15 +24,14 @@ as enabled** (i.e. for CentOS the `baseos` repo configuration in the
Also make sure that there are **no other repositories** which could interfere with the
original configuration.
As long as the original repository configuration is disabled and a new alternative
repository gets added in a different file, or not the only repo that provides the
base packages, the migration result will end in a corrupted system.
Any distribution that has had its core repositories altered, removed, duplicated
or overridden may cause migrate2rocky to break or corrupt the system when run.
Any attempt to migrate such systems, even after reversing the changes made by such
software, is not supported in any way. In all cases you should backup your system
before using migrate2rocky and USE AT YOUR OWN RISK.
This especially happens on systems configured with a centralized package management
like Katello (RedHat Satellite 6) or Uyuni (RedHat Satellite 5, SUSE Manager).
If one of these systems is configured it is possible to remove all projects/channels
so the designated /etc/yum.repos.d/redhat.repo or
/etc/yum.repos.d/susemanager:channels.repo file is empty or missing.
#### RHEL migrations show error messages during conversion

View File

@ -188,7 +188,7 @@ exit_clean () {
}
pre_check () {
if [[ -e /etc/rhsm/ca/katello-server-ca.pem ]] || [[ -s /etc/yum.repos.d/redhat.repo ]]; then
if [[ -e /etc/rhsm/ca/katello-server-ca.pem ]]; then
exit_message "Migration from Katello-modified systems is not supported by migrate2rocky. See the README file for details."
fi
if [[ -e /etc/salt/minion.d/susemanager.conf ]] || [[ -s /etc/yum.repos.d/susemanager\:channels.repo ]]; then