Project

Profile

Help

Actions
Send by e-mail Copy link

Story #8265

closed

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

Added by daviddavis about 3 years ago. Updated over 2 years ago.

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

Ticket moved to GitHub: "pulp/pulpcore/1972":https://github.com/pulp/pulpcore/issues/1972

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
Actions
Copy link
 #1

Updated by daviddavis about 3 years ago

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

Updated by daviddavis about 3 years 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"
Actions
Copy link
 #3

Updated by daviddavis about 3 years 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().

Actions
Copy link
 #4

Updated by pulpbot over 2 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE
Actions
Send by e-mail Copy link

Also available in: Atom PDF