Bug 811132 - Misleading error logs under production.log while creating new org
Summary: Misleading error logs under production.log while creating new org
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-10 08:49 UTC by Sachin Ghai
Modified: 2014-09-18 15:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-18 20:46:12 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Sachin Ghai 2012-04-10 08:49:41 UTC 
Description of problem:

Create an org from UI and you will see following logs in production.log

[ERROR: 2012-04-10 14:01:16 #5010] Received unrecognized notice: "Organization 'ami_org' was created."
[ERROR: 2012-04-10 14:01:16 #5010] Received unrecognized notice: "Organization 'ami_org' was created."
[ERROR: 2012-04-10 14:01:16 #5010] Received unrecognized notice: "Click on 'Add Environment' to create the first environment"

These logs are misleading as statement says 'received unrecognized notice' and with error. However org is being created in UI and UI raising proper notifications as well.
 
Version-Release number of selected component (if applicable):
katello-0.1.309-1.el6.noarch

How reproducible:
always

Steps to Reproduce:

1. Create org from UI

Actual results:


Expected results:
no error log should be in production.log while creating new org

Additional info:
Comment 2 Brad Buckingham 2012-12-18 20:46:12 UTC 
I ran a few create org tests using katello-1.1.12-22.el6cf.noarch and was unable to reproduce the issue; therefore, going to close this one.  Please re-open if the issue resurfaces.
Comment 3 Mike McCune 2013-08-16 18:12:14 UTC 
getting rid of 6.0.0 version since that doesn't exist
Note You need to log in before you can comment on or make changes to this bug.