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.

Issue

• The rhncfg-client fails to deploy "all" configuration files if any of the configuration file have destination path as a NFS mount and the NFS share do not have root permission (no_root_squash) to write to the directory .

Example:

Consider /mnt is NFS mounted partition (without root access). We have two files on configuration channel,

file1- /mnt/file1
file2- /etc/file2

• While using rhncfg-client get command to deploy files, it fails to deploy both files because NFS share exported with read-only permission or client do not have permission to write. The rhncfg-client deploy all files successfully if partition is not NFS mounted or have permission to write to all required directories. Here rhncfg-client should deploy all other files (Here file2) which can be deployed successfully and it should give a warning message for files which can not be deployed (Here file1).