Bug 856646
Summary: | getSubmissionID() by qdate returning duplicates | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Trevor McKay <tmckay> |
Component: | condor-aviary | Assignee: | Pete MacKinnon <pmackinn> |
Status: | CLOSED ERRATA | QA Contact: | Martin Kudlej <mkudlej> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | Development | CC: | matt, mkudlej, tstclair |
Target Milestone: | 2.3 | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | condor-7.8.5-0.1 | Doc Type: | Bug Fix |
Doc Text: |
Cause: Retrieving submission IDs with a BEFORE mode.
Consequence: Duplicate submission IDs are returned.
Fix: Fixed problems in the getSubmissionID implementation that could not process the specified time range query parameters.
Result: Unique submission IDs are returned to the client.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-06 18:45:45 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Trevor McKay
2012-09-12 14:09:48 UTC
Is it possible this is related to Bug 855449? Tested on RHEL 5.9/6.4 x x86_64/i386 with condor-7.8.7-0.6.el6_3.x86_64 condor-aviary-7.8.7-0.6.el6_3.x86_64 condor-classads-7.8.7-0.6.el6_3.x86_64 condor-wallaby-base-db-1.25-1.el6_3.noarch condor-wallaby-client-5.0.4-1.el6_3.noarch condor-wallaby-tools-5.0.4-1.el6_3.noarch python-condorutils-1.5-6.el6.noarch python-qpid-0.18-4.el6.noarch python-qpid-qmf-0.18-12.el6_3.x86_64 python-wallabyclient-5.0.4-1.el6_3.noarch qpid-cpp-client-0.18-12.el6_3.x86_64 qpid-cpp-server-0.18-12.el6_3.x86_64 qpid-qmf-0.18-12.el6_3.x86_64 qpid-tools-0.18-7.el6_3.noarch ruby-condor-wallaby-5.0.4-1.el6_3.noarch ruby-qpid-qmf-0.18-12.el6_3.x86_64 ruby-wallaby-0.16.1-2.el6.noarch wallaby-0.16.1-2.el6.noarch wallaby-utils-0.16.1-2.el6.noarch and it works. --> VERIFIED 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 |