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

Bug 583993

Summary:	GlobalJobId doesn't have to be unique when SCHEDD_CLUSTER_MAXIMUM_VALUE is set
Product:	Red Hat Enterprise MRG	Reporter:	Martin Kudlej <mkudlej>
Component:	condor	Assignee:	grid-maint-list <grid-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	1.3	CC:	iboverma, matt
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-26 19:57:14 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:
Bug Depends On:
Bug Blocks:	575150, 834691

Description Martin Kudlej 2010-04-20 13:06:59 UTC

Steps to Reproduce:
1. Set up to SCHEDD_CLUSTER_MAXIMUM_VALUE = 10 .
2. restart condor and wait for stards are up and running
3. Submit 11 jobs in one file, for example:
cmd = /bin/true
queue
cmd = /bin/true
queue
cmd = /bin/true
queue
cmd = /bin/true
queue
cmd = /bin/true
queue
cmd = /bin/true
queue
cmd = /bin/true
queue
cmd = /bin/true
queue
cmd = /bin/true
queue
cmd = /bin/true
queue
cmd = /bin/true
queue

condor_q -l:
GlobalJobId = "hostname#1.0#1271766740"
LastJobStatus = 0
JobStatus = 1
ProcId = 0
AutoClusterId = 1
AutoClusterAttrs = "JobUniverse,LastCheckpointPlatform,NumCkpts,Requirements,NiceUser,ConcurrencyLimits"
ServerTime = 1271768623

and GlobalJobId is the same as of first job:
condor_history -format "%s\n" "GlobalJobId" 1.0:
hostname#1.0#1271766740

Version-Release number of selected component (if applicable):
condor-7.4.3-0.8.el5

How reproducible:
100%

Actual results:
GlobalJobId isn't unique.

Expected results:
GlobalJobId has to be unique.

Comment 2 Matthew Farrellee 2010-04-21 15:06:14 UTC

This is a good observation. It demonstrates the need to carefully manage job counts when using SCHEDD_CLUSTER_MAXIMUM_VALUE.

Comment 3 Martin Kudlej 2010-04-22 12:40:44 UTC

I reopened this bug, because I thought that GlobalJobId is unique identification of job in pool. If not what's the real purpose of GlobalJobId? Is there any other classadd which uniquely identify the job in pool?

Comment 4 Matthew Farrellee 2010-04-22 13:28:31 UTC

It is, except for this case, and use of MAX_VAL requires particular care. It is not a tool for common use.

Comment 7 Anne-Louise Tangring 2016-05-26 19:57:14 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.