This topic describes the cause of the "A YUM/DNF repository defined multiple times" error message that is reported when you use Server Migration Center (SMC) to migrate an operating system. This topic also describes how to resolve the error.
Problem description
During the migration of an operating system, the "A YUM/DNF repository defined multiple times" error message is reported.
Cause
The configuration files of Yellowdog Updater, Modified (YUM) repositories contain duplicate repository identifiers. This may cause operating system migration jobs to fail.
Solution
Connect to the Elastic Compute Service (ECS) instance whose operating system you want to migrate. For more information, see Connect to a Linux instance by using a password or key.
Run the following commands to view the repository identifiers in the configuration files of YUM repositories:
grep "\[base\]" /etc/yum.repos.d/*.repo grep "\[extras\]" /etc/yum.repos.d/*.repo grep "\[updates\]" /etc/yum.repos.d/*.repo
The following information provides an example of the response. In this example, the repositories defined in the
/etc/yum.repos.d/CentOS-7.repo
and/etc/yum.repos.d/CentOS-Base.repo
files have the same identifier [base].[root@test ~]# grep "\[base\]" /etc/yum.repos.d/*.repo /etc/yum.repos.d/CentOS-7.repo:[base] /etc/yum.repos.d/CentOS-Base.repo:[base] [root@test ~]# grep "\[extras\]" /etc/yum.repos.d/*.repo /etc/yum.repos.d/CentOS-Base.repo:[extras] [root@test ~]# grep "\[updates\]" /etc/yum.repos.d/*.repo /etc/yum.repos.d/CentOS-Base.repo:[updates]
Modify the duplicate identifiers in the .repo configuration files in the
/etc/yum.repo.d/
directory. Make sure that each repository has a unique identifier.In this example, you can change the identifier [base] in the
/etc/yum.repos.d/CentOS-7.repo
or/etc/yum.repos.d/CentOS-Base.repo
file to another name. In actual situations, if other identifiers such as [extras] and [updates] are also configured for more than one repository, you must modify the duplicate identifiers to ensure that each repository has a unique identifier.After the error is resolved, run the SMC client and retry the migration job. For more information, see Run the SMC client.