Bug 746053 - yum-rhn-plugin busted: Repository rhel-x86_64-server-5 is listed more than once in the configuration
Summary: yum-rhn-plugin busted: Repository rhel-x86_64-server-5 is listed more than on...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum-rhn-plugin
Version: 5.7
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Miroslav Suchý
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-13 18:38 UTC by Dan
Modified: 2011-12-18 18:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-18 18:46:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dan 2011-10-13 18:38:30 UTC
Red Hat Enterprise 5.7 x86_64 kernel 2.6.18-274.3.1.el5

yum-rhn-plugin.noarch-0.5.4-22.el5_7.2

Running a cobbler-built local repository mirror for cobbler/PXE/Kickstarting systems.  There are third party repos and a custom repo of locally required packages.

After an update that changed me from yum-rhn-plugin-0.5.4-22.el5 to yum-rhn-plugin-0.5.4-22.el5_7.2, I started getting failure on any yum command with the message "Repository rhel-x86_64-server-5 is listed more than once in the configuration".

I found the following workarounds: 

* disable yum-rhn-plugin by using "--disableplugin=rhnplugin" on the command line

* downgrade to yum-rhn-plugin-0.5.4-22.el5 (yum-rhn-plugin-0.5.4-22.el5_7.1 has the same issue) and put "exclude=yum-rhn-plugin" in /etc/yum.conf

Comment 1 Dan 2011-10-13 18:41:14 UTC
It looks like an old bug crawled back into yum-rhn-plugin
Ref: <https://access.redhat.com/kb/docs/DOC-15495>

Comment 2 Šimon Lukašík 2011-10-14 13:12:50 UTC
Could You please provide more verbose reproducer? What exactly have you
done before the error started to pop-up. On which yum command do you
see the error?

On my machine yum repolist with yum-rhn-plugin-0.5.4-22.el5_7.2 works
like a charm.

Comment 3 Dan 2011-10-14 15:17:52 UTC
A more verbose reproducer ?
I set up a cobbler server with local repo mirrors
reference: <https://fedorahosted.org/cobbler/wiki/ManageYumRepos>

I have all Red Hat 5.7 channels for both i386 and x86_64 defined as well as EPEL5, a repo for HP ProLiant hardware management software and one repo of in-house custom built RPM's.

I am building machines with cobbler PXE kickstart - references: https://fedorahosted.org/cobbler/wiki/KickstartTemplating
https://fedorahosted.org/cobbler/wiki/KickstartSnippets

After the new machine is built, any yum command fails to run with the message "Repository rhel-x86_64-server-5 is listed more than once in the configuration".

On the client, I ripped out the entire /etc/yum.repo.d/ directory and rebuilt it one piece at a time.  None of these actions made the problem go away.  Disabling the plugin lets the yum commands work as does downgrading the installed package.  However, this breaks my hands-free system build environment as I have to manually log into each client box, downgrade the package, lock it with yum-versionlock, and then complete the setup process.


On which yum command do I see the error? Any/every command without disabling the plugin

You say that on your machine yum repolist with yum-rhn-plugin-0.5.4-22.el5_7.2 works
like a charm.  Was this test machine built the same way that mine was ?  From a cobbler/pxe-boot/kickstart on a server with local mirrors ?

Comment 4 Dan 2011-10-14 15:22:39 UTC
FYI: I have a RHN Case on this as well
https://access.redhat.com/support/cases/00546517

Comment 6 Šimon Lukašík 2011-12-18 18:46:21 UTC
This is not a bug.

Multiple repositories with the same name are not allowed by Yum. The label
is actually the identifier of repository. If a machine has configured
a repository with the label equal to rhn channel, some of Yum operations
will fail.

The failure is actually good thing in this case. Because it will draw
an attention of the administrator. Additionally, the error message describes
the situation well. Not much to fix.


Note You need to log in before you can comment on or make changes to this bug.