Bug 672517
Summary: | condor_q -better prints error if classad expr should return false | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Lubos Trilety <ltrilety> |
Component: | condor | Assignee: | Will Benton <willb> |
Status: | CLOSED ERRATA | QA Contact: | Lubos Trilety <ltrilety> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | beta | CC: | iboverma, jneedle, matt |
Target Milestone: | 2.0 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | condor-7.6.0-0.2 | Doc Type: | Bug Fix |
Doc Text: |
C: The job run analysis feature of the 'condor_q' tool could not analyze jobs whose requirements expression included ClassAd function calls that evaluated to false.
C: Attempting to analyze such a job would result in an error message indicating that the requirements expression had a "bad form."
F: Internal changes to Condor's implementation of the ClassAd language now prevent this error from occurring.
R: Users can now analyze jobs with function calls that may return false in their requirements expressions.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2011-06-23 15:42:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 693778 |
Description
Lubos Trilety
2011-01-25 12:19:01 UTC
This appears to be fixed in 7.6 (specifically, in the 7.5.1 timeframe) as a side effect of the classad compatibility layer; I can't reproduce it with a pre-7.6 build. 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: C: The job run analysis feature of the 'condor_q' tool could not analyze jobs whose requirements expression included ClassAd function calls that evaluated to false. C: Attempting to analyze such a job would result in an error message indicating that the requirements expression had a "bad form." F: Internal changes to Condor's implementation of the ClassAd language now prevent this error from occurring. R: Users can now analyze jobs with function calls that may return false in their requirements expressions. Tested on:
$CondorVersion: 7.6.1 Apr 27 2011 BuildID: RH-7.6.1-0.4.el5 $
$CondorPlatform: I686-RedHat_5.6 $
$CondorVersion: 7.6.1 Apr 27 2011 BuildID: RH-7.6.1-0.4.el5 $
$CondorPlatform: X86_64-RedHat_5.6 $
$CondorVersion: 7.6.1 Apr 27 2011 BuildID: RH-7.6.1-0.4.el6 $
$CondorPlatform: I686-RedHat_6.0 $
$CondorVersion: 7.6.1 Apr 27 2011 BuildID: RH-7.6.1-0.4.el6 $
$CondorPlatform: X86_64-RedHat_6.0 $
# condor_q -better
-- Submitter: hostname : <IP:37149> : hostname
---
008.000: Run analysis summary. Of 1 machines,
1 are rejected by your job's requirements
0 reject your job because of their own requirements
0 match but are serving users with a better priority in the pool
0 match but reject the job for unknown reasons
0 match but will not currently preempt their existing job
0 match but are currently offline
0 are available to run your job
No successful match recorded.
Last failed match: Thu May 5 15:19:43 2011
Reason for last match failure: no match found
WARNING: Be advised:
No resources matched request's constraints
The Requirements expression for your job is:
( stringListMember("4","1,2,3") ) && ( TARGET.Arch == "X86_64" ) &&
( TARGET.OpSys == "LINUX" ) && ( TARGET.Disk >= DiskUsage ) &&
( ( TARGET.Memory * 1024 ) >= ImageSize ) &&
( ( RequestMemory * 1024 ) >= ImageSize ) &&
( TARGET.FileSystemDomain == MY.FileSystemDomain )
Job ClassAd Requirements expression evaluates to false
>>> VERIFIED
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-2011-0889.html |