Project

Profile

Help

Issue #9338

closed

Python import issue in some OpenShift environments

Added by awcrosby over 1 year ago. Updated about 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

When deploying pulpcore as part of galaxy_ng on OpenShift, in some environments the pulp-worker does not complete initializing. We have found this is fixed by moving a conditional import to the top of the file: https://github.com/pulp/pulpcore/blob/master/pulpcore/tasking/entrypoint.py#L43

Actions #1

Updated by bmbouter over 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to bmbouter
Actions #2

Updated by pulpbot over 1 year ago

  • Status changed from ASSIGNED to POST

Added by bmbouter over 1 year ago

Revision 022d2e39

Fixes worker not starting on openshift

For some strange reason some Openshift environments do not like the runtime import the worker entrypoint used. Moving it to the top where it belongs anyway resolves the problem.

closes #9338

Actions #3

Updated by bmbouter over 1 year ago

  • Status changed from POST to MODIFIED
Actions #4

Updated by pulpbot about 1 year ago

  • Sprint/Milestone set to 3.16.0
Actions #5

Updated by pulpbot about 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF