Issue #9338: Python import issue in some OpenShift environments - Pulp

Actions

Send by e-mail Copy link

Issue #9338

closed

Python import issue in some OpenShift environments

Added by awcrosby about 3 years ago. Updated about 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

bmbouter

Category:

Sprint/Milestone:

3.16.0

Start date:

Due date:

Estimated time:

Severity:

3. High

Version:

Platform Release:

OS:

Triaged:

Groomed:

Sprint Candidate:

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

Copy link

Updated by bmbouter about 3 years ago

Status changed from NEW to ASSIGNED
Assignee set to bmbouter

Actions

Copy link

Updated by pulpbot about 3 years ago

Status changed from ASSIGNED to POST

PR: https://github.com/pulp/pulpcore/pull/1606

Added by bmbouter about 3 years ago

Revision 022d2e39 | View on GitHub

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

Copy link