Bug 456480 - condor_status -run -format vs condor_q -run -format
condor_status -run -format vs condor_q -run -format
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid (Show other bugs)
All Linux
low Severity low
: Next Version
: ---
Assigned To: Matthew Farrellee
MRG Quality Engineering
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2008-07-23 20:56 EDT by Matthew Farrellee
Modified: 2012-10-19 12:58 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-10-19 12:58:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Condor 11 None None None 2012-10-19 08:08:22 EDT

  None (edit)
Description Matthew Farrellee 2008-07-23 20:56:05 EDT
"condor_status -run -format ..." works as you might expect, it prints out your
special format for all machines with running jobs. Great.

"condor_q -run -format ..." prints out a mixture of "condor_q -run" output and
"condor_q -constraint 'JobStatus==2' -format ..." output. Not great.

Is this intended, or should it be fixed? There is a clear workaround, use
"condor_q -constraint 'JobStatus==2' -format ...", but that's onerous. This also
happens with -hold, -goodput, and -io.

Note You need to log in before you can comment on or make changes to this bug.