Created attachment 355510 [details] traceback after package install when systemid file was removed Description of problem: I'm getting a traceback after the package installation on the system where I have removed /etc/sysconfig/rhn/systemid file (so RHN is disabled on the system and package is taken from a local file:// yum repo). Traceback is simillar to the one in bug 444581. Version-Release number of selected component (if applicable): yum-3.2.22-20.el5.noarch yum-rhn-plugin-0.5.4-10.el5.noarch rhnlib-2.2.7-2.el5.noarch How reproducible: always Steps to Reproduce: 1. # rm -rf /var/cache/yum/* 2. # vim /etc/yum.repos.d/local.repo # configure some local repo with required package (you can use yumdownloader to get the packages there) 3. # mv /etc/sysconfig/rhn/systemid{,.BAK} 4. # rpm -e vsftpd 5. # yum -y install vsftpd Actual results: traceback Expected results: no traceback Additional info: Found during testing bug 444581.
In this case we print out message that RHN is disabled, but forgot to set up the variable and really disable. Commited to spacewalk git as 16d247b4ca80fd07eb6d5139adcef44ef90d8542 and to svn as rev. 188952
# VERIFIED Checked on RHEL 5.5 server/client versions: RHEL5.5-[Server,Client]-20091227.0/ The package fixing the issue is: yum-rhn-plugin-0.5.4-15.el5.noarch.rpm (both for client & server) Scenario done: 1. install yum-utils; createrepo 2. yumdownloader --destdir /tmp/yum.local/ --resolve vsftpd 3. createrepo /tmp/yum.local/ 4. make a /etc/yum.repos.d/local.repo with: [local] name=local baseurl=file:///tmp/yum.local gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release enabled=1 gpgcheck=1 refer to the scenario in the Reproducer for the rest (comment#1) Result: No more tracebacks, the package installation goes ok from local repo.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0269.html