Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 896740

Summary: getSubmissionID returns some chronologically sorted entries out-of-order
Product: Red Hat Enterprise MRG Reporter: Pete MacKinnon <pmackinn>
Component: condor-aviaryAssignee: grid-maint-list <grid-maint-list>
Status: CLOSED WONTFIX QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: high Docs Contact:
Priority: high    
Version: DevelopmentCC: esammons, ltoscano, matt, tstclair
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: condor-7.8.8-0.5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-26 19:44:03 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
spool files containing JQL and history file none

Description Pete MacKinnon 2013-01-17 21:49:24 UTC 
Using a combination of submissions recorded in the history file and the job queue log (JQL), getSubmissionID sometimes returns submissions from the JQL out-of-order when using the AFTER mode for qdate paging.

For example,

% submission_ids.py --size=40 --mode=AFTER --qdate=1355172185                
1355436244 2012-12-13 17:04:04 new
1355344112 2012-12-12 15:28:32 angelfish                                          

instead of:

% submission_ids.py --size=40 --mode=AFTER --qdate=1355172185                
1355344112 2012-12-12 15:28:32 angelfish                                          
1355436244 2012-12-13 17:04:04 new
Comment 1 Pete MacKinnon 2013-01-18 15:16:56 UTC 
Created attachment 682470 [details]
spool files containing JQL and history file

Reproducer is to have an empty SPOOL directory, then place the contents of the attachment in there and start condor with aviary_query_server. Use the submission_id.py tool with AFTER mode and note that sometimes the last few entries are out-of-order.
Comment 6 Anne-Louise Tangring 2016-05-26 19:44:03 UTC 
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.