Bug 436332 - rhnpush returns 0 even if a package checksum mismatches
rhnpush returns 0 even if a package checksum mismatches
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Other (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Pradeep Kilambi
John Matthews
: Triaged
Depends On:
Blocks: 456985
  Show dependency treegraph
Reported: 2008-03-06 10:47 EST by Daniel Mach
Modified: 2009-09-10 16:24 EDT (History)
3 users (show)

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

Attachments (Terms of Use)
add --strict option (2.52 KB, patch)
2008-03-06 10:47 EST, Daniel Mach
no flags Details | Diff

  None (edit)
Description Daniel Mach 2008-03-06 10:47:10 EST
Description of problem:
When trying to push already existing package which was signed with differeny key
(quite common when pushing to testing rhn servers), rhnpush returns 0 which
indicates that everything is correct.

Version-Release number of selected component (if applicable):

Steps to Reproduce:
1. push rpm to rhn
2. push the same rpm signed with different key to rhn
Actual results:
push finishes with checksum mismatch warning
return code is 0

Expected results:
return code different than 0

Additional info:
I made a patch which adds --strict option.
When rhnpush is executed, it behaves exactly the same as before until the
--strict option is used.

It will be necessary to add strict option to rhn config file as well.

strict causes that rhnpush dies on following errors:
- ERROR: Package %s on disk but not in db
- ERROR: Package checksum %s mismatch (use --force to force upload)

Unfortunately, it dies on first error. It would be great to get list of all
errors (to be able to fix them at once), but I think it's impossible without
major code change.
Comment 1 Daniel Mach 2008-03-06 10:47:10 EST
Created attachment 297061 [details]
add --strict option
Comment 5 Brandon Perkins 2009-09-10 16:24:24 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.