Bug 692140

Summary:	confusing output in condor_q -bet
Product:	Red Hat Enterprise MRG	Reporter:	Will Benton <willb>
Component:	condor	Assignee:	Will Benton <willb>
Status:	CLOSED ERRATA	QA Contact:	Lubos Trilety <ltrilety>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	Development	CC:	iboverma, jneedle, ltoscano, ltrilety, matt
Target Milestone:	2.0
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	condor-7.6.0-0.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-27 14:30:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Will Benton 2011-03-30 14:18:23 UTC

Description of problem:

The job analysis feature of the condor_q tool short-circuits when jobs have not yet been considered for matchmaking.  This can be confusing, since users would generally like to know why the job would have been matched (if it has already been through a negotiation cycle).

Version-Release number of selected component (if applicable):

condor-7.5.6 (upstream)

How reproducible:

Submit more jobs than you have available slots.  Wait a few minutes.  Run "condor_q -bet"

Steps to Reproduce:
1.  echo 'cmd=/bin/sleep\nargs=1d\nqueue 10' | condor_submit
2.  sleep 300
3.  condor_q -bet
  
Actual results:

All of the jobs that are not running will be analyzed with output of this form:

260.001:  Request has not yet been considered by the matchmaker.

Expected results:

The above output is intended to indicate jobs that would have been spuriously analyzed as "not running for unknown reasons" in the old (condor 7.4) job analysis.  Generally, this should only apply in cases in which a machine is available but the job has not yet been considered for matchmaking.  The actual behavior described above occurs even when machines are not available, thus masking potentially-useful analysis results about the activities of those machines.

Additional info:

Comment 1 Will Benton 2011-03-30 14:19:49 UTC

This is fixed in 7.6.x-BZ692140.

Comment 2 Will Benton 2011-03-30 14:20:31 UTC

I've set mrg-skip-errata because this bug never appeared in a MRG release.

Comment 3 Lubos Trilety 2011-05-26 12:44:03 UTC

Successfully reproduced on:
$CondorVersion: 7.6.0 Mar 24 2011 BuildID: RH-7.6.0-0.3.el5 PRE-RELEASE-GRID $
$CondorPlatform: I686-Redhat_5.6 $

001.002:  Request has not yet been considered by the matchmaker.

Comment 4 Lubos Trilety 2011-05-26 15:47:12 UTC

Tested on:
$CondorVersion: 7.6.1 May 23 2011 BuildID: RH-7.6.1-0.6.el5 $
$CondorPlatform: I686-RedHat_5.6 $

$CondorVersion: 7.6.1 May 23 2011 BuildID: RH-7.6.1-0.6.el5 $
$CondorPlatform: X86_64-RedHat_5.6 $

$CondorVersion: 7.6.1 May 23 2011 BuildID: RH-7.6.1-0.6.el6 $
$CondorPlatform: I686-RedHat_6.1 $

$CondorVersion: 7.6.1 May 23 2011 BuildID: RH-7.6.1-0.6.el6 $
$CondorPlatform: X86_64-RedHat_6.1 $

all idle jobs has similar summary:
001.009:  Run analysis summary.  Of 1 machines,
      0 are rejected by your job's requirements 
      0 reject your job because of their own requirements 
      1 match but are serving users with a better priority in the pool 
      0 match but reject the job for unknown reasons 
      0 match but will not currently preempt their existing job 
      0 match but are currently offline 
      0 are available to run your job

>>> VERIFIED