Project

Profile

Help

Issue #4726

closed

Starting Pulp shows errors while all processes start up

Added by bmbouter almost 5 years ago. Updated over 2 years ago.

Status:
CLOSED - WONTFIX
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

Problem

Pulp_workers and pulp_resource_manager processes "check" on each other and if at least 1 worker or 1 resource_manager has not checked in recently it outputs an error saying Pulp is in an unhealthy state. When starting the pulp processes, there is no way to start it without having these errors output. While technically correct (since the other process hasn't started) these errors should not start as part of normal startup. For example here is a normal startup:

Apr 23 18:49:42 pulp3-source-fedora29.localhost.example.com rq[31237]: pulp: pulpcore.tasking.services.worker_watcher:ERROR: There are 0 worker processes running. Pulp will not operate correctly without at least one worker process running.
Apr 23 18:49:42 pulp3-source-fedora29.localhost.example.com rq[31237]: pulp: pulpcore.tasking.services.worker_watcher:ERROR: There are 0 worker processes running. Pulp will not operate correctly without at least one worker process running.

Solution

This logging should be adjusted to only log after 1 heartbeat instead of logging on the very first heartbeat.

Actions #1

Updated by amacdona@redhat.com almost 5 years ago

  • Triaged changed from No to Yes
Actions #2

Updated by dalley over 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

No longer relevant

Also available in: Atom PDF