Bug 586042 - Parameters requested by condor_configure_pool are not ordered
Summary: Parameters requested by condor_configure_pool are not ordered
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor-wallaby-tools   
(Show other bugs)
Version: Development
Hardware: All
OS: Linux
low
medium
Target Milestone: 1.3
: ---
Assignee: Robert Rati
QA Contact: Luigi Toscano
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-26 17:11 UTC by Luigi Toscano
Modified: 2010-10-21 18:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-21 18:44:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Luigi Toscano 2010-04-26 17:11:11 UTC
Description of problem:
When new features are added through condor_configure_pool, it asks for the value of the requested parameters. The parameters are not ordered.
For example, with
condor_configure_pool -n $HOSTNAME -a -f CentralManager,NodeAccess
the following parameter are requestes:
ALLOW_READ
QMF_BROKER_HOST
CONDOR_HOST
ALLOW_WRITE


Please sort the parameters, either by group of parameters (and alphabetical inside each group) or using a global alphabetical order.

Comment 1 Robert Rati 2010-05-12 14:02:41 UTC
The parameters are now sorted in global alphabetical order.

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

Comment 2 Luigi Toscano 2010-07-27 16:21:59 UTC
The parameters are now sorted in alphabetical order.

Verified on RHEL5.5 (noarch package):
condor-wallaby-tools-3.0-1.el5


Note You need to log in before you can comment on or make changes to this bug.