Note: This is a CentOS 5.3 boot image I have config files that I want to deploy when the machine is kickstarted. If the files have an SELinux context set, it crashes out with a traceback when I run "rhncfg-client get" as a kickstart post script. Having uploaded files from a machine they generally have an SELinux context set. == Version-Release number of selected component (if applicable): rhncfg-client-5.9.7.2-1.el5.noarch == How reproducible: Every time == Actual results: Traceback (most recent call last): File "/usr/bin/rhncfg-client", line 34, in ? sys.exit(Main().main() or 0) File "/usr/share/rhn/config_common/rhn_main.py", line 187, in main handler.run() File "/usr/share/rhn/config_client/rhncfgcli_get.py", line 62, in run dep_trans.add_preprocessed(path, processed_path, file_info, dirs_created) File "/usr/share/rhn/config_common/transactions.py", line 181, in add_preprocessed self._chown_chmod_chcon(processed_file_path, dest_path, file_info, strict_ownership=strict_ownership) File "/usr/share/rhn/config_common/transactions.py", line 151, in _chown_chmod_chcon raise Exception("failed to set selinux context on %s" % dest_path) Exception: failed to set selinux context on /bin/gone
Could be related to: https://bugzilla.redhat.com/show_bug.cgi?id=527142 Specifically see Comment 10.
I am having the same problem, but with spacewalk 0.7 this time.
Mass-moving to space13.
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Aligning under space16.
Since the bug 527142 is marked resolved, can we assume this bug can be closed as well?
Not sure, but I don't have easy access to test any more (Changed employer). If no-one else is yelling, I say close it off. Mark
(In reply to comment #8) > Not sure, but I don't have easy access to test any more (Changed employer). If > no-one else is yelling, I say close it off. OK. Thanks.