Project

Profile

Help

Issue #6764

closed

settings.py always created with ownership of group 'pulp'

Added by gerrod almost 4 years ago. Updated almost 4 years ago.

Status:
CLOSED - NOTABUG
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:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

I was performing a source install without pulplift and the /etc/pulp/settings.py is getting created with group 'pulp'. However, pulp_user and developer_user are both 'vagrant'. As a result the installer can't run migrations because CONTENT_ORIGIN is not set.

Actions #1

Updated by dkliban@redhat.com almost 4 years ago

  • Subject changed from settings.py always created with ownership of user 'pulp' to settings.py always created with ownership of group 'pulp'
  • Description updated (diff)
Actions #2

Updated by dkliban@redhat.com almost 4 years ago

This is expected. The default 'pulp_group' is 'pulp'.

Actions #3

Updated by mdepaulo@redhat.com almost 4 years ago

wrote:

This is expected. The default 'pulp_group' is 'pulp'.

Yup, and the user "vagrant" should be in the "pulp" group: https://github.com/pulp/pulp_installer/blob/master/roles/pulp/tasks/install.yml#L60

If CONTENT_ORIGIN is unset, make sure your variables look like this: https://github.com/pulp/pulp_installer/blob/master/playbooks/example-use/group_vars/all#L17

Actions #4

Updated by dkliban@redhat.com almost 4 years ago

  • Status changed from NEW to CLOSED - NOTABUG

This is not a bug with hte installer. Pulpcore is going to improve the error message when there is a permissions problem with the settings file.

https://github.com/pulp/pulpcore/pull/723/files

Also available in: Atom PDF