Opened 15 years ago

Closed 8 years ago

#367 closed defect (fixed)

IZ2073: qstat -f -qs E broken

Reported by: ovid Owned by:
Priority: low Milestone:
Component: sge Version: 6.0u4
Severity: minor Keywords: Sun clients


[Imported from gridengine issuezilla]

        Issue #:      2073             Platform:     Sun      Reporter: ovid (ovid)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.0u4       CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    roland (roland)
      QA Contact:     roland
       * Summary:     qstat -f -qs E broken
   Status whiteboard:

     Issue 2073 blocks:
   Votes for issue 2073:

   Opened: Wed Jun 14 09:00:00 -0700 2006 

qstat -f -qs E is totally broken.

I get the following:

sgetest@dt218-123# qstat -f -qs E
sgetest@dt218-123# qstat -f -qs E -xml

But, without the -f flag, it seems OK

sgetest@dt218-123# qstat -qs E
job-ID  prior   name       user         state submit/start at     queue
                 slots ja-task-ID
  11589 0.50500 ERROR      sgetest      Eqw   06/14/2006 06:57:45
  11590 0.00000 HOLD       sgetest      hqw   06/14/2006 06:57:45
sgetest@dt218-123# qstat -qs E -xml
<?xml version='1.0'?>
<job_info  xmlns:xsd="">
    <job_list state="pending">
      <JB_submission_time>06/14/2006 06:57:45</JB_submission_time>
    <job_list state="pending">
      <JB_submission_time>06/14/2006 06:57:45</JB_submission_time>

   ------- Additional comments from roland Thu Nov 16 01:06:35 -0700 2006 -------
The comments section is incorrect because it mixes job error with queue error.
The "qstat -qs E" switch is a queue filter and shows all queues in error state
AND all pending jobs. The "qstat -f -qs E" should print the same output as
"qstat -qs E". This is not the case, it prints nothing.

My suspicion is qstat -f recognize no queues are selected and then print's no
output. This is wrong because it has to print the pending jobs.

Change History (1)

comment:1 Changed 8 years ago by dlove

  • Resolution set to fixed
  • Severity set to minor
  • Status changed from new to closed

Not clear what seems to have fixed this.

Note: See TracTickets for help on using tickets.