Project

Profile

Help

Issue #4794

closed

Pulp handles incompatible plugins poorly

Added by mdepaulo@redhat.com over 5 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:

Description

As I was discussing with dkilban on IRC, Pulp does not handle plugins being incompatible with its current version very well.

Here is a partial snippet of logs from my container for pulp-api (which calls makemigrations and migrate before starting pulp-api), and a complete snippet:
https://pastebin.com/nmhNdHAd
https://pastebin.com/My1ZSBwj

When this error occurs, I can access /pulp/api/v3/, but not /pulp/api/v3/status/ . It yields HTTP 500 error.


Related issues

Related to Pulp - Issue #4562: Source installs should fail if a plugin requires a newer version of pulpcore-plugin or pulpcore than is checked outCLOSED - CURRENTRELEASEActions
Has duplicate Pulp - Issue #4829: Can't access API docsCLOSED - DUPLICATEActions

Also available in: Atom PDF