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.

Bug 1609904

Summary: RHEL 7 selinux module building takes much longer than rhel 6
Product: Red Hat Enterprise Linux 7 Reporter: Devon <dshumake>
Component: libsemanageAssignee: Vit Mojzis <vmojzis>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: dwalsh, lvrabec, mgrepl, mmalik, plautrba, ssekidde
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-06 08:20:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Devon 2018-07-30 19:00:02 UTC
1. Proposed title of this feature request

RHEL 7 selinux module building takes much longer than rhel 6.

2. Who is the customer behind the request?

Account: name and acct # <- please include both
TAM customer: no
CSM customer: no
Strategic: no

3. What is the nature and description of the request?

Customer is seeing much longer build times when installing multiple selinux modules at the same time.

4. Why does the customer need this? (List the business requirements here)

"The current slowness in installing multiple selinux modules at the same time is impacting our build/test cycle. We have resorted to a hack to speed this process that we can not field with."

5. How would the customer like to achieve this? (List the functional requirements here)

"Modify/fix the semodule command in RHEL7 to be on par with RHEL6/FC27 wrt to installing multiple selinux policy modules at the same time (semodule -i  *.pp)"

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

"Confirm build time for selinux-policy rpm is in on par with RHEL6 and/or FC27."

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

Could not find one if there is one.

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

"Would like in the November timeframe. Don't know what release the corresponds to. March is when we must have the fix or live with the slow build/install times."

9. Is the sales team involved in this request and do they have any additional input?

No

10. List any affected packages or components.

selinux-policy

11. Would the customer be able to assist in testing this functionality if implemented?

Yes