Issue #6130
closedUsers have a tendency to run /usr/local/bin/pulp-content in production
Description
Ticket moved to GitHub: "pulp/pulpcore/1866":https://github.com/pulp/pulpcore/issues/1866
The ansible galaxy team was running pulp-content in production by running the /usr/local/bin/pulp-content script: https://github.com/pulp/pulpcore/blob/master/bin/pulp-content
However, this script is not meant to be run in production, only for quickly launching pulp-content like django-admin runserver
allows for pulp-api. Users should use gunicorn like the systemd unit and the containers specify in production.
https://github.com/pulp/pulpcore/commit/9c36548f4b1f264ea1b835f49c077b67cf6d0d43
https://pulp.plan.io/issues/4218
The agreed upon solution is to turn it into a subcommand of pulpcore-manager
Docs updates will be required for this change too.
Related issues
Updated by mdepaulo@redhat.com about 4 years ago
- Sprint Candidate changed from No to Yes
Updated by fao89 about 4 years ago
- Tracker changed from Issue to Task
- % Done set to 0
Updated by mdepaulo@redhat.com about 4 years ago
- Has duplicate Story #6403: As a user, the `pulp-content` helper script is named correctly as `pulpcore-content` added
Updated by mdepaulo@redhat.com about 4 years ago
As agreed on #pulp-dev, we will turn this into a subcommand of pulpcore-manager.
This also implicitly addresses #6403's issue of it still having the "pulp-" prefix rather than the current "pulpcore-" prefix.
Note: Originally proposed alternate solutions in the description were to rename it to something like "pulp-content-testrun", remove the executable bit or remove it from the PATH, etc.
Updated by mdepaulo@redhat.com about 4 years ago
- Tracker changed from Task to Issue
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
- Severity set to 2. Medium
- Triaged set to No
- Sprint set to Sprint 70
Updated by fao89 about 4 years ago
- Triaged changed from No to Yes
- Sprint Candidate changed from Yes to No
Updated by rchan over 3 years ago
- Sprint deleted (
Sprint 80)
Removing from current Sprint 80. Target for Sprint 82. Can be added back to Sprint 81 if staffing allows.
Updated by bmbouter over 3 years ago
- Status changed from ASSIGNED to NEW
- Assignee deleted (
bmbouter)
Moving back to NEW, I am not actively working on this.
Updated by pulpbot over 2 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE