Bug 221899

Summary: Node log displayed in partially random order
Product: Red Hat Enterprise Linux 5 Reporter: Len DiMaggio <ldimaggi>
Component: congaAssignee: Ryan McCabe <rmccabe>
Status: CLOSED ERRATA QA Contact: Corey Marthaler <cmarthal>
Severity: medium Docs Contact:
Priority: low    
Version: 5.0CC: cluster-maint, djansa, jlaska, kanderso, kupcevic, rmccabe
Target Milestone: ---Keywords: FutureFeature, Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2007-0640 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-07 15:36:37 UTC Type: ---
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
Log file - what is the sequence of the whole file? none

Description Len DiMaggio 2007-01-08 20:05:24 UTC 
Description of problem:
Node log displayed in partially random order - groups of messages are in
ascending/descending order, but the overall log is not displayed in any one
sequence.

Version-Release number of selected component (if applicable):
ricci-0.8-26.el5
luci-0.8-26.el5

How reproducible:
100%

Steps to Reproduce:
1. View the log of a cluster node via luci
  
Actual results:
See the attached file.

Expected results:
Either ascending or descending order.

Additional info:
See the attachment.
Comment 1 Len DiMaggio 2007-01-08 20:05:24 UTC 
Created attachment 145097 [details]
Log file - what is the sequence of the whole file?
Comment 2 Ryan McCabe 2007-01-09 20:00:21 UTC 
Easy fix, but it'll have to wait until after 5.0. The log entries are grouped by
what logged them (e.g., all cluster-related log messages are grouped together).
Comment 3 Kiersten (Kerri) Anderson 2007-04-23 17:09:36 UTC 
Fixing Product Name.  Cluster Suite was merged into Enterprise Linux for version
5.0.
Comment 6 errata-xmlrpc 2007-11-07 15:36:37 UTC 
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 the 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.

http://rhn.redhat.com/errata/RHSA-2007-0640.html