Description of problem: To provide equivalent functionality with the condor utilities, a command is needed to list a node's configuration. This command would optionally take an option providing the config version to display (ie node#getConfig). If no version is given, the current node's configuration in the store is displayed. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Added new shell command: show-node-config It takes a node name and displays the configuration of the node. It takes an option (-l, --latest) which is the most recent configuration not more recent then version # provided. If no option is given, it returns the node's current configuration in the store. Changes tracked upstream on branch: BZ820419-show-node-config
# wallaby show-node-config -h Usage: wallaby show-node-config NODE [OPTIONS] -h, --help displays this message --version VERSION shows this node's configuration at VERSION # wallaby help | grep show show-feature: Displays the properties of a feature. show-group: Displays the properties of a group. show-node: Displays the properties of a node. show-param: Displays metadata about a parameter in the store. show-subsystem: Displays the properties of a subsystem. # rpm -qa | grep wallaby python-wallaby-0.16.1-2.el6.noarch condor-wallaby-base-db-1.24-2.el6.noarch condor-wallaby-client-5.0.3-2.el6.noarch ruby-wallaby-0.16.1-2.el6.noarch wallaby-utils-0.16.1-2.el6.noarch python-wallabyclient-5.0.3-2.el6.noarch wallaby-0.16.1-2.el6.noarch Command is available and working, but there is no such command like show-node-config listed in output from "wallaby help". It will be hidden and used internally only?
Yes, this command is intended to be hidden for now.
Thanks for quick reply. # rpm -qa | grep -i wallaby python-wallaby-0.16.1-2.el6.noarch condor-wallaby-base-db-1.24-2.el6.noarch condor-wallaby-client-5.0.3-2.el6.noarch ruby-wallaby-0.16.1-2.el6.noarch wallaby-utils-0.16.1-2.el6.noarch python-wallabyclient-5.0.3-2.el6.noarch wallaby-0.16.1-2.el6.noarch >>> 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/RHSA-2013-0564.html