Project

Profile

Help

Story #8265

As a user, I have checks that are run when starting Pulp and when I run "pulpcore-manager check"

Added by daviddavis 6 months ago. Updated 5 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Right now we have checks in two different places in our application:

The first set of checks aren't being run except by Katello. This is because "checks are not run as part of the WSGI stack that is used in deployment".

We should standardize on one approach to checks that will be run:

  • When the pulpcore-manager check command is run
  • When pulpcore is run as part of a WSGI stack

History

#1 Updated by daviddavis 6 months ago

  • Tracker changed from Issue to Task
  • % Done set to 0
  • Severity deleted (2. Medium)
  • Triaged deleted (No)

#2 Updated by daviddavis 6 months ago

  • Tracker changed from Task to Story
  • Subject changed from Standardize checks to As a user, I have checks that are run when starting Pulp and when I run "pulpcore-manager check"

#3 Updated by daviddavis 5 months ago

We should also try to move to models instead of using a db cursor. One thing that might help is using django's get_model() function. We could probably call this in the check if it's done after/at AppConfig's ready().

Please register to edit this issue

Also available in: Atom PDF