Bug 1958791 - Pruner degrades image registry operator when it is removed
Summary: Pruner degrades image registry operator when it is removed
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.6.z
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Oleg Bulatov
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-10 07:25 UTC by Christian González Vázquez
Modified: 2024-12-20 20:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-11 15:45:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1867792 1 unspecified CLOSED Pruner degrades image registry operator if the latter is removed 2023-12-15 18:47:35 UTC

Description Christian González Vázquez 2021-05-10 07:25:50 UTC
Description of problem:

If image registry is removed the pruner degrades the operator with reason ImagePrunerJobFailed::Removed


Version-Release number of selected component (if applicable):

4.6.19

How reproducible:

Allways

Steps to Reproduce:
1. Sets image registry management state as Removed
2. Wait for pruner to run

Actual results:

Image registry operator becomes Degraded

Expected results:

No degradation, as the image registry is removed we should not degrade it.
Additional info:

It´s the same problem that BZ1867792

Comment 1 Oleg Bulatov 2021-05-10 12:02:33 UTC
Please attach the pruner logs.

Comment 4 Red Hat Bugzilla 2023-09-15 01:06:18 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


Note You need to log in before you can comment on or make changes to this bug.