Actions
Issue #9338
closed
Python 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
Updated by bmbouter about 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
Updated by pulpbot about 3 years ago
- Status changed from ASSIGNED to POST
Added by bmbouter about 3 years ago
Updated by bmbouter about 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|022d2e390729401e157201edea84da14c77b49db.
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
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