If you try to deploy a config file with a non-existing/wrong SELinux context the event history will simply say 'invalid argument' leaving the administrator with a big question mark. It should instead say something like "file /path/to/foobar could not be deployed because of invalid SELinux context".
By the way, let me post the error messages. Client is a Fedora 13 Beta. Spacewalk WebUI: Failed deployment, rolled back: [Errno 22] Invalid argument (code 49) Client's /var/log/rhncfg-actions (with debug=10): 2010-04-29 16:21:10 transactions.deploy: deploying transaction 2010-04-29 16:21:10 transactions.deploy: directory not found, creating: /nas 2010-04-29 16:21:10 utils.mkdir_p: testing /nas 2010-04-29 16:21:10 utils.mkdir_p: created /nas 2010-04-29 16:21:10 utils.mkdir_p: dirs_created: ['/nas'] 2010-04-29 16:21:10 transactions.deploy: changed_dir_info: {} 2010-04-29 16:21:10 transactions.deploy: new_dirs: ['/nas'] 2010-04-29 16:21:10 transactions.deploy: done with directory creation, moving on to files 2010-04-29 16:21:10 transactions.deploy: writing new version of /etc/modprobe.d/no-ipv6 to tmp file ... 2010-04-29 16:21:10 transactions._chown_chmod_chcon: selinux context: user_u:object_r:user_home_t 2010-04-29 16:21:10 transactions.rollback: rolling back 2010-04-29 16:21:10 transactions.rollback: removing tmp file /etc/modprobe.d/.rhn-cfg-tmp-3129-sm9wp3 ... 2010-04-29 16:21:10 transactions.rollback: tmp file removed 2010-04-29 16:21:10 transactions.rollback: removing directory /nas that was created during transaction ... 2010-04-29 16:21:10 transactions.rollback: directory removed 2010-04-29 16:21:10 transactions.rollback: rollback successful 2010-04-29 16:21:10 configfiles.deploy: Failed deployment, rolled back: [Errno 22] Invalid argument --- All our files seem to have had the SELinux context user_u:object_r:user_home_t and I wouldn't know why one of us would set them to that because it's all system files (like for pam/ldap/access/nsswitch/...) so I wonder if that's a default (which IMHO should be empty). Maybe it came from uploading the fiels with rhncfg-manager from a backup which was in a users home tho...that'd explain the contexts I guess.
Okay, after applying the patch from Joshua Roys I now get the following message instead which is really helpful: "Failed deployment, rolled back: ('failed to set selinux context on /etc/nsswitch.conf', OSError(22, 'Invalid argument'))" (code 49) Thanks a lot for the fast and very good patch Joshua! cae64f15933666eca92edaa3dad2d00f22954113
Let's call this bugzilla MODIFIED, as the fix is in Spacewalk git master but was not tagged and built yet.
Mass-aligning under space12, so that we don't lose track of this bugzilla. This however does not mean that we plan (will be able to) address this bug in Spacewalk 1.2.
Moving ON_QA. Please use the Spacewalk 1.2 release candidate yum repo at http://koji.spacewalkproject.org/spacewalk/split/spacewalk-5E/server/spacewalk-5E-1.2/$basearch/os http://koji.spacewalkproject.org/spacewalk/split/spacewalk-f12/server/spacewalk-f12-1.2/$basearch/os http://koji.spacewalkproject.org/spacewalk/split/spacewalk-f13/server/spacewalk-f13-1.2/$basearch/os http://koji.spacewalkproject.org/spacewalk/split/spacewalk-f14/server/spacewalk-f14-1.2/$basearch/os (depending on your OS) to verify the bugzilla.
With Spacewalk 1.2 released, marking as CLOSED CURRENTRELEASE. https://www.redhat.com/archives/spacewalk-list/2010-November/msg00111.html