Default group only applies to a node if there is no other configuration. Skeleton group always applies. Or, vice versa, for backward compatible semantics of default.
How we can test this bug? Is there any repro scenario?
To test this feature, run wallaby-agent with the --enable-skeleton-group option or with WALLABY_ENABLE_SKELETON_GROUP=true in your environment. When it is enabled, this feature adds newly-created nodes to a group called +++SKEL. Features and parameter settings applied to +++SKEL will thus be applied to all nodes in +++SKEL, but --- unlike the default group --- nodes can be removed from +++SKEL.
Tested on: wallaby-0.12.1-1 condor-wallaby-tools-4.1.1-1 ccs/p doesn't list skeleton group # ccp --list-all-groups Groups: group1 group2 Internal Default Group # wallaby list-groups Console Connection Established... the default group +++DEFAULT the skeleton group +++SKEL group1 group2 Another question is if there shouldn't be a new option for the skeleton group in ccp similar to the one for default group. >>> ASSIGNED
Tested with: wallaby-0.12.1-1 Tested on: RHEL6 i386, x86_64 RHEL5 i386, x86_64 As it is a tech preview support of the skeleton group in wallaby tools ccs/p will be added later for that a new Bug 749569 was created. In wallaby skeleton group works fine, when enabled any new node was automatically added to skeleton group (+++SKEL). It is possible to remove a node from such group later. >>> VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0045.html