Project

Profile

Help

Issue #6263

User installation makes non-pulp user hard to use

Added by bmbouter 7 months ago. Updated 5 months ago.

Status:
NEW
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:
Quarter:

Description

To reproduce

  1. Make a user not named pulp, this is the administrator's normal account. For demo purposes I'll use bmbouter.
  2. Install a generic user install with pulp as the pulp username and bmbouter as the user to install with. Do this with:
ansible-playbook example-use/playbook.yml -u bmbouter -i ~/devel/pulp3/inventory
  1. Then ssh as bmbouter because you can't ssh as pulp because it has /usr/nologin.

  2. You try to use pulpcore-manager but you have two problems.

a) Your environment doesn't have PULP_SETTINGS="/etc/pulp/settings.py" like the systemd files have b) You lack the POSIX permissions to read the /etc/pulp/settings.py file also.

This is also made more confusing for users due to this dynaconf bug but that's a separate matter.

History

#1 Updated by fao89 7 months ago

  • Triaged changed from No to Yes

#2 Updated by bmbouter 5 months ago

  • Category set to Installer
  • Tags deleted (Pulp 3 installer)

Please register to edit this issue

Also available in: Atom PDF