Bug 533003 - rhncfg-client get fails during kickstart if there's an SELinux context set
Summary: rhncfg-client get fails during kickstart if there's an SELinux context set
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Clients
Version: 0.6
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space16
TreeView+ depends on / blocked
 
Reported: 2009-11-04 16:41 UTC by Mark Chappell
Modified: 2011-08-30 10:34 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-07-25 18:33:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Mark Chappell 2009-11-04 16:41:04 UTC
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

Comment 1 Mark Chappell 2009-11-18 16:47:39 UTC
Could be related to:

https://bugzilla.redhat.com/show_bug.cgi?id=527142

Specifically see Comment 10.

Comment 2 hai wu 2010-01-19 22:35:17 UTC
I am having the same problem, but with spacewalk 0.7 this time.

Comment 3 Jan Pazdziora (Red Hat) 2010-11-19 16:04:35 UTC
Mass-moving to space13.

Comment 4 Miroslav Suchý 2011-04-11 07:33:10 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 5 Miroslav Suchý 2011-04-11 07:37:03 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 6 Jan Pazdziora (Red Hat) 2011-07-20 11:51:21 UTC
Aligning under space16.

Comment 7 Jan Pazdziora (Red Hat) 2011-07-25 17:01:50 UTC
Since the bug 527142 is marked resolved, can we assume this bug can be closed as well?

Comment 8 Mark Chappell 2011-07-25 17:17:38 UTC
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

Comment 9 Jan Pazdziora (Red Hat) 2011-07-25 18:33:02 UTC
(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.


Note You need to log in before you can comment on or make changes to this bug.