Red Hat Bugzilla – Bug 495787
rhnpush --force option disabled in Satellite when it should only be disabled in Spacewalk
Last modified: 2009-09-10 14:54:45 EDT
Description of problem:
If a user attempts to push a package via rhnpush with the --force option to a 530 Satellite, the user will receive an error stating that --force has been disabled.
Upon consulting with Pradeep, it appears that this feature should only be disabled for Spacewalk, where the following line in /etc/rhn/rhn.conf appears as follows:
This line should be changed with the Satellite branding package and should read:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Attempt to push a package to a Satellite using rhnpush and adding the --force command-line option
Error received on console stating that --force is disabled, package not pushed
Looks like this was disabled in spacewalk.git commit f8572eda5ea4e55660759fecd23414f3349e17ff, commit message doesn't clearly state one way or the other but it looks like it was done in a way that it could be re-enabled for Satellite easily. (setting force_package_upload = 1) I'll ping Prad to make sure.
I should read original bug report more clearly as I see now you already discussed with prad. :) Will re-enable for Satellite.
Fixed in satellite.git 4044bd334def6ba00261911fd49f939057f80b41, fix will arrive in satellite-branding-188.8.131.52-1 but will require a re-run of spacewalk-setup if you're not doing a fresh install.
VERIFIED in 5/7 build.
VERIFIED again in Satellite-5.3.0-RHEL4-re20090730.0-i386-embedded-oracle.iso
/etc/rhn/rhn.conf , force is by default set to 1:
testing procedure : rhnpush run repeatedly with or without directive '--force' :
rhnpush -d /mnt/redhat/brewroot/packages/rpm/184.108.40.206/15.el5/x86_64/ --channel=main-channel --username=admin --password=*** --nosig --server=http://`hostname`/APP --force
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.