Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #4187

closed

Pulp3's systemd unit names should not conflict with Pulp2's systemd unit names

Added by bmbouter almost 6 years ago. Updated over 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
ipanova@redhat.com
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
3.0.0
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 49
Quarter:

Description

Problem

Pulp2 uses the following systemd unit names: 'pulp_resource_manager', 'pulp_workers' among others.
Pulp3 also needs those same components and uses 'pulp_resource_manager' and 'pulp_workers' also. per the docs

Solution: Have Pulp3 change

Pulp would switch to 'pulp3_resource_manager' and 'pulp3_worker@1', pulp3_worker@2.

Solution: Have Pulp2 change

Pulp would switch to 'pulp2_resource_manager' and 'pulp2_workers'.

Solution: Leave them conflicting and the user avoids through configuration

This option would have a documentation note that if these systemd names conflict with your system, perhaps due to a Pulp2 install already there, that you can rename the unit names and that is OK.

Also we would need to add a variable for this to the Ansible installer so automated installs could also do the same thing.

Actions
Send by e-mail Copy link

Also available in: Atom PDF