Description of problem: Configuration doesn't allow for symbolic link creation from a file on a remote system to the local system ln -s /remote/nfs/mount/script.sh /etc/cron.hourly/script.sh Version-Release number of selected component (if applicable): 1.5 How reproducible: Every time Steps to Reproduce: 1. Filename/path: /etc/cron.hourly/script.sh 2. symbolic link/target /remote/nfs/mount/script.sh 3. Actual results: Client execution returned "Failed deployment and rollback, information on user '' could not be found" (code 50) Expected results: a symplink created Additional info:
Taking..
Hello, In order to investigate this issue we tried to reproduce the using the scenario explained below: # rhncfg-client elist Mode Owner Group Size Rev Config Channel File lrwxrwxrwx root root 15 1 global_mmello_cfgs /etc/cron.hourly/test.sh -> /export/test.sh -rw-r--r-- root root 214 2 global_mmello_cfgs /etc/motd lrwxrwxrwx root root 22 1 global_mmello_cfgs /etc/test-remot-symlink -> ../boot/grub/grub.conf lrwxrwxrwx root root 11 1 global_mmello_cfgs /export/nfs-symb-link -> /etc/passwd drwx------ root root *0 2 global_mmello_cfgs /root/.ssh -rw------- root root 412 2 global_mmello_cfgs /root/.ssh/authorized_keys # mount | grep nfs 10.12.56.126:/export on /export type nfs (rw,vers=4,addr=10.12.56.126,clientaddr=10.12.56.89) # ls -la /export/nfs-symb-link /etc/cron.hourly/test.sh /export/test.sh ; rhncfg-client verify ; rhncfg-client get ; ls -la /export/nfs-symb-link /etc/cron.hourly/test.sh /export/test.sh ls: cannot access /export/nfs-symb-link: No such file or directory ls: cannot access /etc/cron.hourly/test.sh: No such file or directory -rwxr-xr-x. 1 nfsnobody nfsnobody 26 Nov 10 01:18 /export/test.sh missing /etc/cron.hourly/test.sh <-- file missing as expected /etc/motd /etc/test-remot-symlink missing /export/nfs-symb-link <-- file missing as expected /root/.ssh /root/.ssh/authorized_keys Deploying /root/.ssh Deploying /root/.ssh/authorized_keys Deploying /export/nfs-symb-link Deploying /etc/cron.hourly/test.sh Deploying /etc/test-remot-symlink Deploying /etc/motd lrwxrwxrwx. 1 root root 15 Nov 10 01:19 /etc/cron.hourly/test.sh -> /export/test.sh <-- file deployed as expected lrwxrwxrwx. 1 nfsnobody nfsnobody 11 Nov 10 01:19 /export/nfs-symb-link -> /etc/passwd <-- file deployed as expected (created at NFS) -rwxr-xr-x. 1 nfsnobody nfsnobody 26 Nov 10 01:18 /export/test.sh Going further, per the message attached into the BZ the operation was aborted due the UserNotFound exception: Error: 'Client execution returned "Failed deployment and rollback, information on user '' could not be found" (code 50)' Looking the code we have: spacewalk/client/tools/rhncfg/actions/configfiles.py ----------------------------------------------------------------- 220 except cfg_exceptions.UserNotFound, e: 221 try: 222 dep_trans.rollback().... 223 except FailedRollback: 224 log_to_file(0, "Failed deployment and rollback, information on user '%s' could not be found" % (e[0], )) 225 return (44, "Failed deployment and rollback, information on user '%s' could not be found" % (e[0], ), {}) 226 #5/3/05 wregglej - 136415 Adding some more exceptions to handle 227 except cfg_exceptions.UserNotFound, f: 228 log_to_file(0, "Failed deployment and rollback, information on user '%s' could not be found" % (f[0], )) 229 return (50, "Failed deployment and rollback, information on user '%s' could not be found" % (f[0], ), {}) 230 #5/5/05 wregglej - 136415 Adding exception handling for unknown group, 231 except cfg_exceptions.GroupNotFound, f: 232 log_to_file(0, "Failed deployment and rollback, group '%s' could not be found" % (f[0],)) 233 return (51, "Failed deployment and rollback, group '%s' could not be found" % (f[0],), {}) 234 else: 235 log_to_file(0, "Failed deployment and rollback, information on user '%s' could not be found" % (e[0], )) 236 return (50, "Failed deployment and rollback, information on user '%s' could not be found" % (e[0], ), {}) Have you check if the file's owner is valid and exists? Can you provide further information around this issue (rpm -q rhncfg* , detailed steps, logs, rhncfg-client verify|elist|get output)? Since we were not able to reproduce the same issue, we are setting this BZ to NEEDINFO flag. Best Regards, Marcelo Moreira de Mello
Close this. The spacewalk client software on the node I was working on is outdated (cira 0.5) and not at the same rev at the server. The symbolic creation works just fine on newer installation with the current client. Sorry about the waste of time, I forgot that this server was an older one.