Bug 474813 - [RFE] customize EC2E routed CMD
Summary: [RFE] customize EC2E routed CMD
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid
Version: 1.0
Hardware: All
OS: Linux
low
low
Target Milestone: 1.1.1
: ---
Assignee: Robert Rati
QA Contact: Jeff Needle
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-05 13:55 UTC by Matthew Farrellee
Modified: 2009-04-21 16:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-21 16:19:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2009:0434 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging and Grid Version 1.1.1 2009-04-21 16:15:50 UTC

Description Matthew Farrellee 2008-12-05 13:55:20 UTC
When a job is routed for EC2E a second job is submitted that looks like a duplicate when viewed with condor_q, any likely other tools. This is primarily because the CMD, a.k.a the executable, is identical. However, the CMD is only a label for EC2 jobs, and could be changed to anything. I'd suggest: "EC2: <route name>: <original cmd>"

Comment 1 Robert Rati 2009-02-05 17:26:53 UTC
The routed job's Cmd is now:
"EC2: <route name>: <original cmd>"

However, condor_q will still just show <original cmd> in all likelihood.

Fixed in:
condor-ec2-enhanced-hooks-1.0-11

Comment 3 Jan Sarenik 2009-03-11 16:49:32 UTC
Works as expected. In condor_history it is for example:
Cmd = "EC2: Amazon Small: /mnt/sharedfs/testmonkey/jasan.sh"

While as Robert writes above, running jobs still show <original_cmd>.

Comment 5 errata-xmlrpc 2009-04-21 16:19:29 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-0434.html


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