Bug 618742 - Changes to the default group are not saved when there are no nodes in the store
Changes to the default group are not saved when there are no nodes in the store
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: wallaby (Show other bugs)
All Linux
medium Severity medium
: 1.3
: ---
Assigned To: Will Benton
Martin Kudlej
Depends On:
  Show dependency treegraph
Reported: 2010-07-27 11:55 EDT by Robert Rati
Modified: 2010-10-20 07:28 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-10-20 07:28:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Rati 2010-07-27 11:55:33 EDT
Description of problem:
Wallaby throws an exception when an unprovisioned node checks in with the store.  The store had no nodes in it, but had features configured on the default-group and the configuration had been successfully activated.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Remove all wallaby db files
2. Start wallaby
3. load default db
4. condor_confgure_pool --default-group -a -f Master,NodeAccess
5. Set requested params and activate
6. condor_configd -d
7. Check the ConfigLog for the error message from the store
Actual results:

Expected results:

Additional info:
Comment 1 Will Benton 2010-07-27 12:07:21 EDT
Changed bug title.
Comment 2 Will Benton 2010-07-27 13:12:16 EDT
Fixed on master.
Comment 3 Martin Kudlej 2010-08-25 10:29:45 EDT
I've tested this with wallaby-utils-0.6.3-1 on RHEL 5.5 x i386/x86_64 and there was exception.
I've tested this with wallaby-0.9.4-1 on RHEL 5.5 x i386/x86_64 and there is no exception. --> VERIFIED

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