Bug 635979 - condor_configure_pool: cannot delete parameters
Summary: condor_configure_pool: cannot delete parameters
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor-wallaby-tools
Version: beta
Hardware: All
OS: Linux
high
high
Target Milestone: 1.3
: ---
Assignee: grid-maint-list
QA Contact: Martin Kudlej
URL:
Whiteboard:
Depends On: 636262
Blocks: 493710 627960
TreeView+ depends on / blocked
 
Reported: 2010-09-21 08:36 UTC by Martin Kudlej
Modified: 2010-10-21 18:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-21 18:44:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin Kudlej 2010-09-21 08:36:23 UTC
Description of problem:
After installing and deleting 2 basic features I cannot delete parameters
First example uses parameters included in features:

$ yum install wallaby wallaby-utils condor-wallaby-base-db co
ndor-wallaby-tools condor-wallaby-client

$ wallaby load /var/lib/condor-wallaby-base-db/condor-base-db.snapshot

$ vim /etc/condor/config.d/test

QMF_BROKER_HOST = 127.0.0.1

$ service condor restart
Starting Condor daemons: [  OK  ]

$ wallaby inventory
Console Connection Established...
node name is provisioned?                             last checkin
--------- ---------------                             ------------
_hostname_   unprovisioned           Tue Sep 21 03:58:49 -0400 2010

$ condor_configure_store -a -n `hostname`
Adding node "_hostname_"

--- !Node
name: _hostname_
memberships: []

$ condor_configure_pool --default-group -a -f Master,NodeAccess

Apply these changes [Y/n] ?
The following parameters need to be set for this configuration to be valid.
ALLOW_READ
ALLOW_WRITE
CONDOR_HOST
Set these parameters now ? [y/N] y
ALLOW_READ: *
ALLOW_WRITE: *
CONDOR_HOST: 127.0.0.1
Configuration applied

Create a named snapshot of this configuration [y/N] ?

Activate the changes [y/N] ? Y
Activating configuration.  This may take a while, please be patient
Configuration activated
Configuration saved

$ condor_config_val -dump | grep -i allow
ALLOW_ADMINISTRATOR = $(CONDOR_HOST), $(FULL_HOSTNAME), $(FULL_HOSTNAME)
ALLOW_NEGOTIATOR = $(CONDOR_HOST)
ALLOW_NEGOTIATOR_SCHEDD = $(CONDOR_HOST), $(FLOCK_NEGOTIATOR_HOSTS)
ALLOW_OWNER = $(FULL_HOSTNAME), $(ALLOW_ADMINISTRATOR)
ALLOW_READ = *
ALLOW_READ_COLLECTOR = $(ALLOW_READ), $(FLOCK_FROM)
ALLOW_READ_STARTD = $(ALLOW_READ), $(FLOCK_FROM)
ALLOW_WRITE = *
ALLOW_WRITE_COLLECTOR = $(ALLOW_WRITE), $(FLOCK_FROM)
ALLOW_WRITE_STARTD = $(ALLOW_WRITE), $(FLOCK_FROM)

$ condor_configure_pool --default-group -l                   Group "Internal Default Group":
Group ID: 1
Name: Internal Default Group
Features (priority: name):
  0: Master
  1: NodeAccess
Parameters:
  ALLOW_WRITE = *  
  CONDOR_HOST = 127.0.0.1
  ALLOW_READ = *   
[root@nec-em19 ~]# condor_configure_pool --default-group -d -f Master,NodeAccess

Apply these changes [Y/n] ?
Configuration applied

Create a named snapshot of this configuration [y/N] ?

Activate the changes [y/N] ? y
Activating configuration.  This may take a while, please be patient
Configuration activated
Configuration saved

$ condor_configure_pool --default-group -l                   Group "Internal Default Group":
Group ID: 1
Name: Internal Default Group
Features (priority: name):
Parameters:
  ALLOW_WRITE = *  
  CONDOR_HOST = 127.0.0.1
  ALLOW_READ = *   

$ condor_configure_pool --default-group -d -p ALLOW_WRITE

Apply these changes [Y/n] ?
Configuration applied

Create a named snapshot of this configuration [y/N] ?

Activate the changes [y/N] ? Y
Activating configuration.  This may take a while, please be patient
Configuration activated
Configuration saved

$ echo $?
0

$ condor_configure_pool --default-group -l
Group "Internal Default Group":
Group ID: 1
Name: Internal Default Group
Features (priority: name):
Parameters:
  ALLOW_WRITE = *  
  CONDOR_HOST = 127.0.0.1
  ALLOW_READ = *

Second one uses simple parameter from store which is not included in installed feature:
$ condor_configure_pool --default-group -a -p START
Value for "START": true

Apply these changes [Y/n] ? 
Configuration applied

Create a named snapshot of this configuration [y/N] ? 

Activate the changes [y/N] ? y
Activating configuration.  This may take a while, please be patient
Configuration activated
Configuration saved

$ condor_config_val -dump | grep -i start
...
START = true
...

$ condor_configure_pool --default-group -l
Group "Internal Default Group":
Group ID: 1
Name: Internal Default Group
Features (priority: name):
Parameters:
  ALLOW_WRITE = *
  CONDOR_HOST = 127.0.0.1
  ALLOW_READ = *
  START = true

$ condor_configure_pool --default-group -d -p START

Apply these changes [Y/n] ? 
Configuration applied

Create a named snapshot of this configuration [y/N] ? 

Activate the changes [y/N] ? Y
Activating configuration.  This may take a while, please be patient
Configuration activated
Configuration saved

$ condor_configure_pool --default-group -l
Group "Internal Default Group":
Group ID: 1
Name: Internal Default Group
Features (priority: name):
Parameters:
  ALLOW_WRITE = *
  CONDOR_HOST = 127.0.0.1
  ALLOW_READ = *
  START = true


Version-Release number of selected component (if applicable):
condor-7.4.4-0.14.el5
wallaby-0.9.18-2.el5
wallaby-utils-0.9.18-2.el5
condor-wallaby-tools-3.6-5.el5
condor-wallaby-client-3.6-5.el5

How reproducible:
100%

Steps to Reproduce:
1. install configuration store, qpidd and configd
2. get machines to be provisioned
3. add parameters/features to default group
4. remove features if they have been added
5. remove parameter
6. check parameter in condor configuration and in configuration of
default group in pool
  
Actual results:
Admin cannot deleter parameters.

Expected results:
Admin can delete all parameters from configuration of pool.

Comment 1 Ted Ross 2010-09-22 19:48:02 UTC
The blocking Bug 636262 has been resolved.  This problem should be resolved as well.

Comment 2 Martin Kudlej 2010-10-01 10:23:28 UTC
Tested with shared parameters 
ALLOW_ADMINISTRATOR: HACentralManager, Master
CONDOR_HOST: HACentralManager, Master
COLLECTOR_NAME: Collector, Master
ALLOW_NEGOTIATOR: HACentralManager, Negotiator
ALLOW_NEGOTIATOR_SCHEDD: BaseScheduler, HACentralManager
COLLECTOR_HOST: Collector, HACentralManager
JOB_HOOKS_PORT: JobHooks, LowLatency
SPOOL: JobQueueLocation, Scheduler
STARTD_JOB_EXPRS: ExecuteNode, ExecuteNodeDedicatedPreemption
KILL: DedicatedResource, ExecuteNode
PREEMPT: DedicatedResource, ExecuteNode
START: DedicatedResource, ExecuteNode
SUSPEND: DedicatedResource, ExecuteNode
STARTD_ATTRS: DedicatedResource, ExecuteNode
WANT_SUSPEND: DedicatedResource, ExecuteNode
WANT_VACATE: DedicatedResource, ExecuteNode
CONTINUE: DedicatedResource, ExecuteNode

on RHEL 5.5 x86_64/i386 with 
python-condorutils-1.4-5.el5
condor-wallaby-tools-3.6-5.el5
condor-wallaby-base-db-1.4-5.el5
condor-debuginfo-7.4.4-0.16.el5
condor-7.4.4-0.16.el5
condor-wallaby-client-3.6-5.el5
wallaby-0.9.18-2.el5

and it works. -->VERIFIED


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