Project

Profile

Help

Issue #6130

Users have a tendency to run /usr/local/bin/pulp-content in production

Added by mdepaulo@redhat.com 8 months ago. Updated about 1 month ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
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

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

Has duplicate Pulp - Story #6403: As a user, the `pulp-content` helper script is named correctly as `pulpcore-content`CLOSED - DUPLICATE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by mdepaulo@redhat.com 8 months ago

  • Sprint Candidate changed from No to Yes

#2 Updated by fao89 8 months ago

  • Tracker changed from Issue to Task
  • % Done set to 0

#3 Updated by mdepaulo@redhat.com 7 months ago

  • Has duplicate Story #6403: As a user, the `pulp-content` helper script is named correctly as `pulpcore-content` added

#4 Updated by mdepaulo@redhat.com 7 months 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.

#5 Updated by mdepaulo@redhat.com 7 months 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

#6 Updated by fao89 7 months ago

  • Triaged changed from No to Yes
  • Sprint Candidate changed from Yes to No

#7 Updated by mdepaulo@redhat.com 7 months ago

  • Description updated (diff)

#8 Updated by rchan 6 months ago

  • Sprint changed from Sprint 70 to Sprint 71

#9 Updated by rchan 6 months ago

  • Sprint changed from Sprint 71 to Sprint 72

#10 Updated by rchan 5 months ago

  • Sprint changed from Sprint 72 to Sprint 73

#11 Updated by rchan 5 months ago

  • Sprint changed from Sprint 73 to Sprint 74

#12 Updated by rchan 4 months ago

  • Sprint changed from Sprint 74 to Sprint 75

#13 Updated by rchan 4 months ago

  • Sprint changed from Sprint 75 to Sprint 76

#14 Updated by rchan 3 months ago

  • Sprint changed from Sprint 76 to Sprint 77

#15 Updated by rchan 3 months ago

  • Sprint changed from Sprint 77 to Sprint 78

#16 Updated by rchan 2 months ago

  • Sprint changed from Sprint 78 to Sprint 79

#17 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 79 to Sprint 80

#18 Updated by rchan about 2 months ago

  • Sprint deleted (Sprint 80)

Removing from current Sprint 80. Target for Sprint 82. Can be added back to Sprint 81 if staffing allows.

#19 Updated by bmbouter about 1 month ago

  • Status changed from ASSIGNED to NEW
  • Assignee deleted (bmbouter)

Moving back to NEW, I am not actively working on this.

Please register to edit this issue

Also available in: Atom PDF