Config Channel push failing if user unknown (rhncfg-client get)
I'm surprised it has taken us this long to get in this predicament..
We have files that are owned by users in our configuration channel. Recently we have migrated to using Netgroups and limiting account access to hosts.
Now - if we decide to deploy all config files to a host, it will fail. For example:
/home/jboss - owned by jboss:jboss
If the jboss user is not valid on that host, it will not deploy the file and then the whole deploy fails.
Is there a setting to have the deploy fail more gracefully? Or better yet, ignore files that have an invalid user defined?
Responses
Hello James,
There is an existing feature request for this exact topic:
Bug 748378 - [RFE] rhncfg-client should give a warning messages if any of the configuration file(s) can not be deployed and all other configuration files should be deployed on client system successfully.
This request is currently aligned to Red Hat Satellite 6, in which Puppet runs will allow partial success - the reports tab in the Provisioning section will allow users to view what was successful and what was not. (The above Bugzilla is private but if you have a support case we can attach it to the BZ for you for tracking.)
Red Hat Satellite 6 is currently targeted for general availability in 2014, but if you would like to take a preview (with the opportunity to provide feedback), please refer to our Managed Design Program - http://red.ht/mdp,
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
