Bug 813807 - Jobs submitted from cumin through aviary show 'unknown' for enqueued column
Summary: Jobs submitted from cumin through aviary show 'unknown' for enqueued column
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor-aviary
Version: Development
Hardware: All
OS: Linux
medium
medium
Target Milestone: 2.3
: ---
Assignee: Pete MacKinnon
QA Contact: Martin Kudlej
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-18 13:17 UTC by Trevor McKay
Modified: 2013-03-06 18:43 UTC (History)
7 users (show)

Fixed In Version: condor-7.8.2-0.3
Doc Type: Bug Fix
Doc Text:
Cause: Submit a job through Aviary or QMF interface. Consequence: Qdate field shows value of zero (0). Fix: Submission and job implementation code in Aviary and QMF adjusted to ensure that a ATTR_Q_DATE variable set that arrives late is properly recorded. Result: Qdate field shows correct time value.
Clone Of:
Environment:
Last Closed: 2013-03-06 18:43:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0564 0 normal SHIPPED_LIVE Low: Red Hat Enterprise MRG Grid 2.3 security update 2013-03-06 23:37:09 UTC

Description Trevor McKay 2012-04-18 13:17:06 UTC 
Description of problem:

For some reason dates in the enqueued column are showing up as 'unknown'.  Find out why.
Comment 2 Stanislav Graf 2012-04-20 11:28:33 UTC 
Steps to Reproduce:

(1) Submit job from cumin through aviary
abc | /bin/sleep 360 | True | /tmp

(2) Look into Pool / Submissions
Enqueued - unknown

(3) Drill into Submission - Details
Enqueued - None

(4) Wait 360s -> job is completed

(5) Drill into Submission - Details
Enqueued - 2012-04-20 13:17:16

(6) Look into Pool / Submissions
Enqueued - 2012-04-20 13:17:16
Comment 3 Trevor McKay 2012-05-18 16:55:44 UTC 
This *seems* to be an issue in the plugins.  Submitting through condor_submit gives us Submission objects with a non-zero QDate.  Submitting through the plugins gives us 0 values.

Retargeting.
Comment 5 Pete MacKinnon 2012-05-22 15:03:43 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: Submit a job through Aviary or QMF interface.
Consequence: Qdate field shows value of zero (0).
Fix: Submission and job implementation code in Aviary and QMF adjusted to ensure that a ATTR_Q_DATE variable set that arrives late is properly recorded.
Result: Qdate field shows correct time value.
Comment 8 Martin Kudlej 2013-01-14 14:04:01 UTC 
Tested on RHEL 5.9/6.4 x i386/x86_64 with 
condor-7.8.8-0.3.el6.x86_64
condor-aviary-7.8.8-0.3.el6.x86_64
condor-classads-7.8.8-0.3.el6.x86_64
condor-qmf-7.8.8-0.3.el6.x86_64
condor-wallaby-base-db-1.25-1.el6_3.noarch
condor-wallaby-client-5.0.5-1.el6.noarch
condor-wallaby-tools-5.0.5-1.el6.noarch
cumin-0.1.5648-1.el6.noarch
python-condorutils-1.5-6.el6.noarch
python-qpid-0.18-4.el6.noarch
python-qpid-qmf-0.18-13.el6.x86_64
python-wallaby-0.16.3-1.el6.noarch
python-wallabyclient-5.0.5-1.el6.noarch
qpid-cpp-client-0.18-13.el6.x86_64
qpid-cpp-server-0.18-13.el6.x86_64
qpid-qmf-0.18-13.el6.x86_64
qpid-tools-0.18-7.el6_3.noarch
ruby-condor-wallaby-5.0.5-1.el6.noarch
ruby-qpid-qmf-0.18-13.el6.x86_64
ruby-wallaby-0.16.3-1.el6.noarch
wallaby-0.16.3-1.el6.noarch
wallaby-utils-0.16.3-1.el6.noarch

and it works. -->VERIFIED
Comment 10 errata-xmlrpc 2013-03-06 18:43:47 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0564.html
Note You need to log in before you can comment on or make changes to this bug.