Opened 11 years ago

Last modified 9 years ago

#564 new defect

IZ2702: qsub incorrectly reports that job could not be submitted

Reported by: templedf Owned by:
Priority: normal Milestone:
Component: sge Version: 6.2
Severity: Keywords: clients
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2702]

        Issue #:      2702             Platform:     All      Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.2         CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    roland (roland)
      QA Contact:     roland
          URL:
       * Summary:     qsub incorrectly reports that job could not be submitted
   Status whiteboard:
      Attachments:

     Issue 2702 blocks:
   Votes for issue 2702:


   Opened: Wed Aug 27 10:30:00 -0700 2008 
------------------------


I configured a cluster with no execution hosts and submitted jobs to it:

# qsub $SGE_ROOT/examples/jobs/sleeper.sh
Unable to run job: warning: root your job is not allowed to run in any queue
Your job 1 ("Sleeper") has been submitted.
Exiting.
# qsub -w n $SGE_ROOT/examples/jobs/sleeper.sh
Unable to run job: warning: root your job is not allowed to run in any queue
Your job 2 ("Sleeper") has been submitted.
Exiting.
# qstat -f

############################################################################
 - PENDING JOBS - PENDING JOBS - PENDING JOBS - PENDING JOBS - PENDING JOBS
############################################################################
      1 0.55500 Sleeper    root         qw    08/27/2008 10:01:13     1
      2 0.55500 Sleeper    root         qw    08/27/2008 10:01:30     1

qsub reports that the jobs could not be submitted, even though they were.  The
problem is that JAPI is treating the warning from the qmaster like an error.

In additon, the error message is broken.  "root your job is not allowed to run
in any queue" should be "job submitted by user root is not allowed to run in any
queue" or "your job is not allowed to run in any queue".

Change History (0)

Note: See TracTickets for help on using tickets.