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:
there is some errors during installation in chroot via yum
it due to missing selinux-policy-targeted
Version-Release number of selected component (if applicable):
bind-9.9.4-72.el7.x86_64
selinux-policy-targeted-3.13.1-227.el7.noarch
RHEL-7.6-20180925.n.1/
How reproducible:
always
Steps to Reproduce:
1. yum --installroot=/tmp/XXXX install bind
Actual results:
Installing : 32:bind-license-9.9.4-72.el7.noarch 128/130
Installing : 32:bind-libs-9.9.4-72.el7.x86_64 129/130
Installing : 32:bind-9.9.4-72.el7.x86_64 130/130
ValueError: SELinux policy is not managed or store cannot be accessed.
/var/tmp/rpm-tmp.oRfq8p: line 12: /etc/selinux/targeted/rpmbooleans.custom: No such file or directory
ValueError: SELinux policy is not managed or store cannot be accessed.
/var/tmp/rpm-tmp.oRfq8p: line 30: /etc/selinux/targeted/rpmbooleans.custom: No such file or directory
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %posttrans(bind-32:9.9.4-72.el7.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package 32:bind-9.9.4-72.el7.x86_64
rhel/productid | 1.6 kB 00:00:00
rhel-HighAvailability/productid | 1.6 kB 00:00:00
rhel-ResilientStorage/productid | 1.6 kB 00:00:00
Verifying : python-2.7.5-76.el7.x86_64 1/130
Verifying : 1:pkgconfig-0.27.1-4.el7.x86
Expected results:
no failures
Additional info:
Such error is always emitted when selinux-policy-targeted is not installed at the time of postscript runs. But packages should not depend on targeted policy. Directory /etc/selinux/targeted does not exist in that case and such case is not handled well by %selinux_set_booleans macro. More about it is on bug #1631814.
It would behave the same way also in docker image without selinux policy. I think we want such case supported.
I would want to add Requires(post): selinux-policy-base to bind package. It would require any current policy to be present. We will rely it installs the smallest policy selinux-policy-minimum if no other is chosen in rpm transaction.
Depends how selinux-policy macro change is solved.
It is not exactly the same issue, but resolution is the same to both of them. This is because missing selinux-policy-X package.
*** This bug has been marked as a duplicate of bug 1647659 ***