Bug 893027 - aviary wrong owner in SubmissionID
Summary: aviary wrong owner in SubmissionID
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor-aviary
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: grid-maint-list
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On: 839305
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-08 13:34 UTC by Lubos Trilety
Modified: 2016-05-26 19:51 UTC (History)
6 users (show)

Fixed In Version: condor-7.8.8-0.10
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-26 19:51:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 838619 0 low CLOSED Jobs submitted by different users using the same submission name end up grouped in a single submission owned by the firs... 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 839305 0 medium CLOSED Add Owner as a field in JobID 2021-02-22 00:41:40 UTC

Internal Links: 838619 839305

Description Lubos Trilety 2013-01-08 13:34:20 UTC
Description of problem:
Jobs submitted using condor_submit have the same submissionID regardless on owner. Probably only submission name is counted.

Version-Release number of selected component (if applicable):
condor-aviary-7.8.8-0.1
condor-7.8.8-0.1

How reproducible:
100%

Steps to Reproduce:
1. prepare following file for submit:
# cat submit.file
cmd = /bin/sleep
args = 1d
+Submission = Testing
log = /tmp/userfile-$(Cluster).log
output = /tmp/outfile-$(Cluster).log
error = /tmp/errfile-$(Cluster).log
queue

2. submit a job as 'condor' user
cat submit.file | su - condor -s /bin/bash -c condor_submit

# condor_q
-- Submitter: host : <IP:43659> : host
 ID      OWNER            SUBMITTED     RUN_TIME ST PRI SIZE CMD               
   1.0   condor          1/8  07:38   0+00:00:13 R  0   0.0  sleep 1d          
1 jobs; 0 completed, 0 removed, 0 idle, 1 running, 0 held, 0 suspended

look at submissions
# cd /usr/share/condor/aviary/
# export PYTHONPATH=`pwd`/module:$PYTHONPATH
# python submissions.py
[(SubmissionSummary){
   id = 
      (SubmissionID){
         _scheduler = "host"
         _pool = "host"
         name = "Testing"
         owner = "condor"
         qdate = 1357626749
      }
   status = 
      (Status){
         code = "OK"
      }
   completed = 0
   held = 0
   idle = 0
   removed = 0
   running = 1
   suspended = 0
   transferring_output = 0
 }]

2. submit second job (with the same +Submission parameter) as different user
# getent passwd test || adduser test
# cat submit.file | su - test -s /bin/bash -c condor_submit

# condor_q
-- Submitter: host : <IP:58062> : host
 ID      OWNER            SUBMITTED     RUN_TIME ST PRI SIZE CMD               
   1.0   condor          1/8  07:32   0+00:01:17 R  0   0.0  sleep 1d          
   2.0   test            1/8  07:33   0+00:00:00 I  0   0.0  sleep 1d          
2 jobs; 0 completed, 0 removed, 1 idle, 1 running, 0 held, 0 suspended

see submission summary
# python submissions.py
[(SubmissionSummary){
   id = 
      (SubmissionID){
         _scheduler = "host"
         _pool = "host"
         name = "Testing"
         owner = "condor"
         qdate = 1357626749
      }
   status = 
      (Status){
         code = "OK"
      }
   completed = 0
   held = 0
   idle = 1
   removed = 0
   running = 1
   suspended = 0
   transferring_output = 0
 }]
  
Actual results:
Both jobs have the same SubmissionID

Expected results:
second job should have different SubmissionID because owner is not condor any more

Additional info:

Comment 1 Trevor McKay 2013-01-08 20:11:55 UTC
See also Bug 838619 (this is the same issue from a cumin perspective)

Comment 3 Pete MacKinnon 2013-03-04 23:34:47 UTC
Implementation now recognizes submissions as distinct by key of name+owner. No changes to schema or API so lookups are still *generally* done by the submission name alone. Duplicate names with different owners are presented to the client for human disambiguation.

Comment 6 Anne-Louise Tangring 2016-05-26 19:51:28 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.


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