Bug 625522

Summary:	RFE: Output list of parameters set on a node for 'ccp -l -n <node>'
Product:	Red Hat Enterprise MRG	Reporter:	Erik Erlandson <eerlands>
Component:	wallaby-utils	Assignee:	Robert Rati <rrati>
Status:	CLOSED ERRATA	QA Contact:	Lubos Trilety <ltrilety>
Severity:	low	Docs Contact:
Priority:	low
Version:	1.3	CC:	ltrilety, matt
Target Milestone:	1.3.2	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	condor-wallaby-tools-3.7-1	Doc Type:	Enhancement
Doc Text:	When listing a node information with condor_configure_pool, the output did not show, which parameters and values are explicitly set on the node. Since parameters set on a node have higher priority than parameter values determined by other means, it could have been difficult to determine why a parameter had a specific value. With this update, listing a node information with condor_configure_pool clearly displays which parameters are explicitly set on the node.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-15 12:16:48 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 Erik Erlandson 2010-08-19 17:39:08 UTC

When user does this:

% condor_configure_pool -l -g <group>

They get a list of parameters explicitly set on that group.   It would be nice to get a similar list of any parameters explicitly set for

% condor_configure_pool -l -n <node>


Example, if somebody explicitly adds a parameter to a node:

% condor_configure_pool -n <node> -p START
value for START: TRUE

% condor_configure_pool -l -n <node>
Group Memberships:
 ...
Features Applied:
 ...
Configuration:
 ...
Parameters:
 START = TRUE     <--- START called out as explicitly added

Comment 1 Robert Rati 2010-10-18 21:05:11 UTC

This is now on master.

Comment 2 Robert Rati 2010-10-19 20:04:32 UTC

Fixed in:
condor-wallaby-tools-3.7-1

Comment 3 Robert Rati 2010-11-29 19:06:17 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:
C: Listing a node's information does not include which parameters and values are explicitly set on the node.
C: It can be confusing to figure out why a parameter has a specific value, since parameters set on a node have higher priority than parameter values determined by other means.
C: The parameters set on a node are now clearly displayed
R: Listing a node's information will now clearly display which parameters and their values are explicitly set on the node.

Comment 4 Robert Rati 2010-11-29 19:20:28 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1,4 @@
-C: Listing a node's information does not include which parameters and values are explicitly set on the node.
+C: Listing a node's information with condor_configure_poll does not include which parameters and values are explicitly set on the node.
 C: It can be confusing to figure out why a parameter has a specific value, since parameters set on a node have higher priority than parameter values determined by other means.
 C: The parameters set on a node are now clearly displayed
-R: Listing a node's information will now clearly display which parameters and their values are explicitly set on the node.+R: Listing a node's information with condor_configure_pool will now clearly display which parameters and their values are explicitly set on the node.

Comment 6 Robert Rati 2010-12-23 17:18:31 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1,4 @@
-C: Listing a node's information with condor_configure_poll does not include which parameters and values are explicitly set on the node.
+C: Listing a node's information with condor_configure_pool does not include which parameters and values are explicitly set on the node.
 C: It can be confusing to figure out why a parameter has a specific value, since parameters set on a node have higher priority than parameter values determined by other means.
 C: The parameters set on a node are now clearly displayed
 R: Listing a node's information with condor_configure_pool will now clearly display which parameters and their values are explicitly set on the node.

Comment 8 Lubos Trilety 2011-01-18 14:59:49 UTC

Tested on version:
condor-wallaby-tools-3.8-8

Tested on:
RHEL5 i386,x86_64  - passed

>>> VERIFIED

Comment 9 Eva Kopalova 2011-02-09 16:30:26 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1 @@
-C: Listing a node's information with condor_configure_pool does not include which parameters and values are explicitly set on the node.
+When listing a node information with condor_configure_pool, the output did not show, which parameters and values are explicitly set on the node. Since parameters set on a node have higher priority than parameter values determined by other means, it could have been difficult to determine why a parameter had a specific value. With this update, listing a node information with condor_configure_pool clearly displays which parameters are explicitly set on the node.-C: It can be confusing to figure out why a parameter has a specific value, since parameters set on a node have higher priority than parameter values determined by other means.
-C: The parameters set on a node are now clearly displayed
-R: Listing a node's information with condor_configure_pool will now clearly display which parameters and their values are explicitly set on the node.

Comment 10 errata-xmlrpc 2011-02-15 12:16:48 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/RHBA-2011-0217.html