Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 876248

Summary: /var/log/katello/client.log reports success and error
Product: Red Hat Satellite Reporter: James Laska <jlaska>
Component: katello-agentAssignee: Bryan Kearney <bkearney>
Status: CLOSED UPSTREAM QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.0.1CC: bkearney, ehelms, jturner, lzap
Target Milestone: UnspecifiedKeywords: EasyFix, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-19 18:13:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/katello/client.log none

Description James Laska 2012-11-13 16:23:11 UTC 
Created attachment 644205 [details]
/var/log/katello/client.log

Description of problem:

All katello CLI operations are reported as errors in /var/log/katello/client.log.

Version-Release number of selected component (if applicable):
 * candlepin-0.7.8.1-1.el6cf.src.rpm
 * katello-1.1.12-22.el6cf.src.rpm
 * katello-candlepin-cert-key-pair-1.0-1.src.rpm
 * katello-certs-tools-1.1.8-1.el6cf.src.rpm
 * katello-cli-1.1.8-12.el6cf.src.rpm
 * katello-configure-1.1.9-12.el6cf.src.rpm
 * katello-qpid-broker-key-pair-1.0-1.src.rpm
 * katello-qpid-client-key-pair-1.0-1.src.rpm
 * katello-selinux-1.1.1-2.el6cf.src.rpm
 * pulp-1.1.14-1.el6cf.src.rpm


How reproducible:
 * pretty darn easy

Steps to Reproduce:
1. Install katello
2. Perform content operations using the katello cli (create users/orgs, import manifest, enable repos, sync content etc..)
3. Inspect /var/log/katello/client.log
  
Actual results:

 * client.log reports errors even for successful operations

Expected results:

 * A successful operation should not be reported as an error

Additional info:

> # head /var/log/katello/client.log
> 2012-11-12 11:30:09,513 [ERROR][MainThread] main() @ base.py:437 - error: Successfully created org [ redhat ]
> 2012-11-12 11:30:12,584 [ERROR][MainThread] main() @ base.py:437 - error: Successfully created environment [ Dev ]
> 2012-11-12 11:30:13,811 [ERROR][MainThread] main() @ base.py:437 - error: Successfully created environment [ Test ]
> 2012-11-12 11:30:15,121 [ERROR][MainThread] main() @ base.py:437 - error: Successfully created environment [ Prod ]
Comment 2 Lukas Zapletal 2012-12-10 15:34:25 UTC 
EasyFix
Comment 3 Bryan Kearney 2012-12-18 16:06:37 UTC 
https://github.com/Katello/katello/pull/1286
Comment 4 Bryan Kearney 2012-12-18 16:30:10 UTC 
commit 3a12524cec1d9db57a9d0c12b1e29ee665c54e82
Author: Bryan Kearney <bkearney>
Date:   Tue Dec 18 11:03:41 2012 -0500

    876248: Successful actions should be logged as info, not as errors
Comment 5 Mike McCune 2013-08-16 18:07:16 UTC 
getting rid of 6.0.0 version since that doesn't exist
Comment 8 Mike McCune 2013-09-19 18:13:36 UTC 
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.