Red Hat Bugzilla – Bug 508141
system.config.deplyAll is giving wrong error message when client doesn't have configfiles.deploy capability
Last modified: 2009-09-10 15:56:02 EDT
Created attachment 349448 [details]
traceback from catalina.out
Description of problem:
Steps to Reproduce:
1. Register a client
2. Give provisioning capability
3. Create a configuration channel
4. Create a file "/tmp/foo" in the config channel
5. execute api:
system.config.addChannels(key, systemIds, channelLabels, true);
where systemIds list contains id of the system registered and channelLabels list contains label of the config channel created.
This will succeed.
6. Now try executing:
system.config.deployAll(key, systemIds, earliestDate);
Warning null value received for obj.. Expected class type = java.lang.String
redstone.xmlrpc.XmlRpcFault: unhandled internal exception: null
tomcat traceback is attached.
Error indicating: Client doesn't have configfiles.deploy capability. Please install rhncfg* packages from thn-tools channel.
Note that when client has rhncfg packages installed, deployAll works fine.
master git commit: 3bc4c571c889c85bd038a06f08bed865f3aeff0f
vader git commit: d4ca5991386fbdfa060d95758fdece11f1a6909a
Updated the logic to use text consistent with the UI. Ex.
"The server <hostname> does not have the configfiles.deploy client capability. Please enable the capability before proceeding with the operation."
I did not specifically mention to install the rhncfg* packages, since the user can find out what steps are needed to become config capable by either the reference documentation or the UI at Configuration->ConfigurationChannels->channel->Systems(TargetSystems). I didn't want to repeat this information in case the requirements later change for what is needed for a system to become config capable.
Error message seen as : "The server abc does not have the configfiles.deploy client capability. Please enable the capability before proceeding with the operation."
Moving to verified.
Verified in stage with the same results as stated in previous comment.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.