Red Hat Bugzilla – Bug 244298
rhnreg_ks ends up with a conflict if config mgmt option is enabled in activation key
Last modified: 2010-10-22 11:41:47 EDT
Description of problem:
ok I found the problem...In your key if you goto configuration option there is a
check box at the bottom thats checked
" Schedule a deploy action for all of the configuration files in the channels
listed above upon system registration."
What this means is that automatically add rhncfg to the transaction set if you
are deploying..that why its running rhncfg as a separate transaction at the
bottom...If you disable that check box everything should be working fine..and in
this instance up2date is set to error if rhncfg is already installed.
So thats how it is as of now.. we can open an issue for 4.6 to hanle this so
up2date in config option enable case will try to recheck the package existance.
For now we should be good as its not going to break any other package installs.
Its gonna raise the conflict error as a separate transaction for rhncfg package
alone..but still install the rest of the packages successfully in the akey list.
to add little more info:
[root@gss6-245 up2date_client]# rhnreg_ks --serverUrl=http://10.65.6.86/XMLRPC
####################### ['curl', 'rhncfg', 'rhncfg-actions', 'rhncfg-client',
Name Version Rel
The following packages you requested are already updated:
%%%%%%%%%%%%%%%%%%%%%%%%% [['rhncfg', '5.0.1', '1.el4', ''], ['rhncfg-actions',
'5.0.1', '1.el4', ''], ['rhncfg-client', '5.0.1', '1.el4', '']]
Name Version Rel
rhncfg 5.0.1 1.el4 noarch
rhncfg-actions 5.0.1 1.el4 noarch
rhncfg-client 5.0.1 1.el4 noarch
rhncfg is added in as a seperate transaction and in/var/logup2date
Fri Jun 15 02:50:20 2007] up2date successfully retrieved authentication token
from up2date server
[Fri Jun 15 02:50:22 2007] up2date RPM package conflict error. The message was:
Test install failed because of package conflicts:
package rhncfg-5.0.1-1.el4 is already installed
package rhncfg-client-5.0.1-1.el4 is already installed
package rhncfg-actions-5.0.1-1.el4 is already installed
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
I guess something like this should fix the rhncfg issue:
--- up2dateBatch.py (revision 117585)
+++ up2dateBatch.py (working copy)
@@ -11,6 +11,7 @@
from rhpl.translate import _, N_
+from up2date_client import rpmUtils
@@ -174,6 +175,8 @@
selPackages = 
actionPkgNVREA = map(lambda x:x[:4],self.actionPkgListInfo)
+ installedPkgs = rpmUtils.getInstalledPackageList(getArch=1)
+ installedPkgsNVREA = map(lambda x:x[:4], installedPkgs)
# If action pkgs for update/install
# this loop could be faster leaving it in for now
@@ -183,6 +186,9 @@
for pkg in self.allAvailablePackages:
if pkg in skippedPkgs:
+ if pkg[:4] in installedPkgsNVREA:
+ #skip if package already installed
if pkg[:4] in actionPkgNVREA:
This effects RHEL3 nodes also. Could this fix be applied to RHEL also?
That should have read: Could this fix be applied to RHEL3 also?
If I uncheck the checkbox: " Schedule a deploy action for all of the
configuration files in the channels listed above upon system registration."
the config files are not deployed!!!!
This bugzilla has Keywords: Regression.
Since no regressions are allowed between releases,
it is also being marked as a blocker for this release.
Please resolve ASAP.
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 the 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.