Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
virt-rescue --selinux can not work well, when enable selinux in the command line the value of 'getenforce' is still Disabled in virt-rescue appliance
Version-Release number of selected component (if applicable):
libguestfs-1.27.62-1.1.el7
How reproducible:
100%
Steps to Reproduce:
1. Get a rhel guest image: rhel.img
2. #virt-rescue --selinux -a rhel.img
><rescue> getenforce
Disabled
><rescue> ls -Z /
lrwxrwxrwx root root ? bin -> usr/bin
dr-xr-xr-x root root ? boot
drwxr-xr-x root root ? dev
drwxr-xr-x root root ? etc
Actual results:
#virt-rescue --selinux -a rhel.img
><rescue> getenforce
Disabled
><rescue> ls -Z /
lrwxrwxrwx root root ? bin -> usr/bin
dr-xr-xr-x root root ? boot
drwxr-xr-x root root ? dev
drwxr-xr-x root root ? etc
Expected results:
selinux should be enabled in virt-rescue appliance and works well
Additional info:
SELinux is never enabled in enforcing mode within the appliance. Doing so would possibly result in conflicts between the kernel and enforced policy within the appliance (which is usually a copy of the host system) and the SELinux attributes possibly set in file systems of guests. Because of this, in recent versions we had to disable SELinux completely in virt-builder and virt-customize.
Thus I don't agree "enabling SELinux" should also make it enforcing, since it might lead to unusable tools.
(In reply to Pino Toscano from comment #1)
> SELinux is never enabled in enforcing mode within the appliance. Doing so
> would possibly result in conflicts between the kernel and enforced policy
> within the appliance (which is usually a copy of the host system) and the
> SELinux attributes possibly set in file systems of guests. Because of this,
> in recent versions we had to disable SELinux completely in virt-builder and
> virt-customize.
>
> Thus I don't agree "enabling SELinux" should also make it enforcing, since
> it might lead to unusable tools.
Thanks, i agree with you. If virt-rescue will never enable selinux then the --selinux option should removed from the man page or at least add some text to describe it.
Comment 6Richard W.M. Jones
2016-07-14 14:50:15 UTC