Bug 786815

Summary:	Time borders have no effect for list of resources, groups, users
Product:	Red Hat Enterprise MRG	Reporter:	Martin Kudlej <mkudlej>
Component:	condor-plumage	Assignee:	Pete MacKinnon <pmackinn>
Status:	CLOSED ERRATA	QA Contact:	Daniel Horák <dahorak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	Development	CC:	dahorak, matt, pmackinn, tstclair
Target Milestone:	2.3	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	condor-7.8.2-0.1	Doc Type:	Bug Fix
Doc Text:	Cause: From and To date ranges were not supported for the userlist, usergrouplist, and resourcelist options on plumage_stats. Consequence: A plumage_stats user was unable to limit their queries based on a date range. Fix: Code changes to pass the From and To date range parameters to the appropriate functions within plumage_stats. Result: Users can query user, usergroup, and resource statistics within a specified time span.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-06 18:41:32 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:

Description Martin Kudlej 2012-02-02 13:30:08 UTC

Description of problem:
If someone use parameters: --userlist, --usergrouplist, --resourcelist AND at least one of --f or --t there should be warning in documentation, help message or after use of these arguments together that --f and --t have no effect for --userlist, --usergrouplist, --resourcelist.

I think somewhere should be written about possible parameter combinations.

Version-Release number of selected component (if applicable):
condor-plumage-7.6.5-0.12

How reproducible:
100%

Steps to Reproduce:
1. install and setup condor and ODS
2. run jobs and wait till they show up in ODS
3. plumage_stats --f="date in far far future" --t="date in far far future" --(ugl/rl/ul)
  
Actual results:
User can use parameters in very different combinations. There is no warning about that and no documentation about that.

Expected results:
User can use parameters just in defined combinations. There will be at least warning about unsupported parameter usage and there will be documentation about supported parameters combinations.

Comment 2 Pete MacKinnon 2012-05-02 19:54:58 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: From and To date ranges were not supported for the userlist, usergrouplist, and resourcelist options on plumage_stats.
Consequence: A plumage_stats user was unable to limit their queries based on a date range.
Fix: Code changes to pass the From and To date range parameters to the appropriate functions within plumage_stats.
Result: Users can query user, usergroup, and resource statistics within a specified time span.

Comment 9 Daniel Horák 2013-01-17 13:05:42 UTC

Tested on:
# rpm -q condor-plumage
  condor-plumage-7.8.8-0.3.el6

# plumage_stats --ul
  SUBMITTER
  test1@*
  test2@*
  test3@*
  test4@*
  test5@*
# plumage_stats --ugl
  SUBMITTER / MACHINE
  test1@* / HOSTNAME
  test2@* / HOSTNAME
  test3@* / HOSTNAME
  test4@* / HOSTNAME
  test5@* / HOSTNAME
# plumage_stats --rl
  MACHINE
  slot1@HOSTNAME
  slot1@HOSTNAME
  slot2@HOSTNAME
  slot2@HOSTNAME

# plumage_stats --from "2014-01-01" --to "2015-01-01" -v --ul
  from:	2014-01-01
  to:	2015-01-01
  SUBMITTER
# plumage_stats --from "2014-01-01" --to "2015-01-01" -v --ugl
  from:	2014-01-01
  to:	2015-01-01
  SUBMITTER / MACHINE
# plumage_stats --from "2014-01-01" --to "2015-01-01" -v --rl
  from:	2014-01-01
  to:	2015-01-01
  MACHINE

Time borders works correctly with --ul --ugl --rl parameters.

>>> VERIFIED

Comment 11 errata-xmlrpc 2013-03-06 18:41:32 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