Actions
Issue #9338
closedPython import issue in some OpenShift environments
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
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