Actions
Story #9468
closedAs a pulp-2to3-migration user, I can run the migration with SELinux enabled
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
Start date:
Due date:
% Done:
100%
Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
SELinux
Sprint:
Quarter:
Description
Updates are needed to both the Pulp 2 SELinux polices and the Pulp 3 SELinux policies
This story itself will refer to the Pulp 3 (pulpcore-selinux.git) changes.
Added by Mike DePaulo about 3 years ago
Updated by Anonymous about 3 years ago
- Status changed from NEW to MODIFIED
Applied in changeset pulpcore-selinux|5e64ab9657728e4f7f8fb12c5f249298c6dcd25b.
Updated by pulpbot about 3 years ago
Added by Mike DePaulo about 3 years ago
Added by Mike DePaulo about 3 years ago
Added by Mike DePaulo about 3 years ago
Added by Mike DePaulo about 3 years ago
Updated by pulpbot about 3 years ago
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Add support for pulp-2to3-migration plugin
I've tested this on an EL7 foreman machine with data, with and without the policy changes.
Every added policy line was tested. (A corresponding alert happened without the policy changes, but no alert hapepend with the policy changes.)
fixes: #9468 As a pulp-2to3-migration user, I can run the migration with SELinux enabled