Bug 241369 - --force and --nullorg are incompatible options
--force and --nullorg are incompatible options
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Other (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Sayli Karmarkar
wes hayutin
Depends On:
Blocks: 456985
  Show dependency treegraph
Reported: 2007-05-25 10:50 EDT by James Bowes
Modified: 2015-03-22 21:08 EDT (History)
5 users (show)

See Also:
Fixed In Version: sat530
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-10 16:21:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description James Bowes 2007-05-25 10:50:18 EDT
You can't force a package to a nullorg channel. the client should recognize
this, and inform the user.
Comment 2 Jeff Browning 2009-02-18 16:16:23 EST
I'm not sure what to test here. Could someone please elaborate on the issue?
Comment 3 Sayli Karmarkar 2009-02-18 16:30:22 EST
Jeff, Just try to use rhnpush using both --force and --nullorg together and it should inform user that it is not allowed. 

Comment 4 wes hayutin 2009-03-10 11:48:02 EDT
[root@grandprix tmp]# rhnpush -c testasf -u admin -p dog8code -d /tmp --force --nullorg
ERROR: You cannot force a package to a nullorg channel.
Comment 5 Milan Zázrivec 2009-08-14 08:50:49 EDT
5.3.0 stage testing: same results as in comment #4 -> RELEASE_PENDING.
Comment 6 Brandon Perkins 2009-09-10 16:21:10 EDT
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.


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