Issue #6263: User installation makes non-pulp user hard to use - Pulp

Actions

Send by e-mail Copy link

Issue #6263

closed

User installation makes non-pulp user hard to use

Added by bmbouter almost 5 years ago. Updated about 4 years ago.

Status:

CLOSED - DUPLICATE

Priority:

Normal

Assignee:

Category:

Installer - Moved to GitHub issues

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Sprint:

Quarter:

Description

To reproduce¶

Make a user not named pulp, this is the administrator's normal account. For demo purposes I'll use bmbouter.
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

Then ssh as bmbouter because you can't ssh as pulp because it has /usr/nologin.
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.

Related issues