Project

Profile

Help

Issue #7035

API and Content systemd generated file have the wrong group

Added by spredzy 4 months ago. Updated 4 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Installer
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 76
Quarter:

Description

Both pulpcore-api and pulpcore-content do not specify Group= in the unit files. This results in the generated files/folders to default to group guid 100 (on CentOS) that is the usersgroup.

Associated revisions

Revision 22c9a83d View on GitHub
Added by spredzy 4 months ago

systemd: Ensure services are started with Group pulp_group

Currently the pulpcore-api and pulpcore-content have no group specified on their unit files. Leading them to create their file and folders to a defaulted group (guid: 100).

This commit ensures files and folders are created as {{ pulp_user }}:{{ pulp_group }}

fixes #7035

Revision 22c9a83d View on GitHub
Added by spredzy 4 months ago

systemd: Ensure services are started with Group pulp_group

Currently the pulpcore-api and pulpcore-content have no group specified on their unit files. Leading them to create their file and folders to a defaulted group (guid: 100).

This commit ensures files and folders are created as {{ pulp_user }}:{{ pulp_group }}

fixes #7035

History

#1 Updated by pulpbot 4 months ago

  • Status changed from NEW to POST

#2 Updated by dkliban@redhat.com 4 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 75

#3 Updated by rchan 4 months ago

  • Sprint changed from Sprint 75 to Sprint 76

#4 Updated by spredzy 4 months ago

  • Status changed from POST to MODIFIED

#6 Updated by fao89 4 months ago

  • Sprint/Milestone set to 3.5.0

#7 Updated by fao89 4 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF