Bug 586376 - changes by remote configuration client don't apply in condor
changes by remote configuration client don't apply in condor
Status: CLOSED NOTABUG
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: wallaby-utils (Show other bugs)
Development
All Linux
medium Severity medium
: 1.3
: ---
Assigned To: Robert Rati
Martin Kudlej
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-27 08:47 EDT by Martin Kudlej
Modified: 2010-04-28 08:47 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-04-27 14:27:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Martin Kudlej 2010-04-27 08:47:48 EDT
Version-Release number of selected component (if applicable):
RHEL 5.5 
condor-wallaby-tools-2.6-0.5
condor-7.4.3-0.11.el5

How reproducible:
100%

Steps to Reproduce:
1. install condor and condor_wallaby*
2. start wallaby-agent
3. load default configuration of store /var/lib/wallaby/snapshots/condor-base-db.snapshot
4. condor_configure_store -a -n `hostname`
5.  condor_configure_pool -n `hostname` -a -f Master,CentralManager,NodeAccess

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

Save this configuration [y/N] ? y
  Configuration Name: init
Configuration saved

Activate the changes [y/N] ? y
Configuration activated

6. condor_config_val -dump | grep -i allow_write
ALLOW_WRITE = $(FULL_HOSTNAME), $(FULL_HOSTNAME)

so remote configuration values don't apply in condor.
Comment 1 Robert Rati 2010-04-27 14:27:32 EDT
Misconfiguration on the client nodes.  QMF_BROKER_HOST was not set, so the configd was unable to find the store to retrieve configuration.

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