Issue #8210
closed
Story #7689: As a user I want my socket to be backed up by a systemd implementation
SELinux policy updates for systemd socket activation
Description
SELinux policies need to be updated for this parent task.
Filing this issue to keep track of it, especially if backports are needed: https://github.com/pulp/pulpcore-selinux/pull/33#issuecomment-773464494
Added by Mike DePaulo almost 4 years ago
Added by Mike DePaulo almost 4 years ago
Revision 1da711fe | View on GitHub
Update pulpcore-selinux to 1.2.4.
The fixes are required by foreman-installer, and will be required by pulp-installer when it implements #7689: (systemd socket activation):
- Allow systemd Type=notify
- Label /var/run/pulpcore-(api|content).sock as server
fixes: #8210 SELinux policy updates for systemd socket activation https://pulp.plan.io/issues/8210
related to #7689 As a user I want my socket to be backed up by a systemd implementation https://pulp.plan.io/issues/7689
Updated by pulpbot almost 4 years ago
- Status changed from NEW to POST
Updated by Anonymous almost 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset ansible-pulp|1da711fec7e474c36eeb2c0aac7a339a3f2e3aee.
Updated by ttereshc almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Update pulpcore-selinux to 1.2.4.
The fixes are required by foreman-installer, and will be required by pulp-installer when it implements #7689: (systemd socket activation):
fixes: #8210 SELinux policy updates for systemd socket activation https://pulp.plan.io/issues/8210
related to #7689 As a user I want my socket to be backed up by a systemd implementation https://pulp.plan.io/issues/7689