Bug 749280

Summary: Job id cluster value rollover impact on the QMF and Aviary Submission API
Product: Red Hat Enterprise MRG Reporter: Pete MacKinnon <pmackinn>
Component: Release_NotesAssignee: Tomas Capek <tcapek>
Status: CLOSED CURRENTRELEASE QA Contact: Lubos Trilety <ltrilety>
Severity: high Docs Contact:
Priority: high    
Version: 2.1CC: iboverma, ltrilety, matt
Target Milestone: 2.1Keywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-31 11:11:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 755648    

Description Pete MacKinnon 2011-10-26 15:49:09 UTC 
The QMF and Aviary (SOAP-based) Grid API provide users the ability to query for submission information. Since a submission is a shared attribute value of a related group of individual jobs, it is possible that jobs with duplicate cluster-proc identifiers can hide submissions depending on the order that the jobs are processed within the API implementation. These duplicate cluster-proc identifiers can occur if the maximum cluster value has been reached (i.e., SCHEDD_CLUSTER_MAXIMUM_VALUE has been set to an arbitrarily lower value than the default of INT_MAX) or if the schedd job queue files have been deleted while history job files remain.
Comment 1 Tomas Capek 2011-11-29 13:47:05 UTC 
Added to

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html-single/MRG_Release_Notes/index.html#Grid_2.1_Release
Comment 2 Lubos Trilety 2011-11-29 14:21:46 UTC 
Revision 1-1

Chapter 4.1.2. Known Issues

Grid API component, BZ#749280 present

>>> VERIFIED