Bug 1831555

Summary: Package server stays in state "catalog source was removed" and cannot be updated
Product: OpenShift Container Platform Reporter: przem123 <ppod>
Component: Management ConsoleAssignee: Robb Hamilton <rhamilto>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: high    
Version: 4.4CC: aos-bugs, bpeterse, dsover, gparente, hasha, jokerman, nhale, susuresh
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1840647 (view as bug list) Environment:
Last Closed: 2020-07-13 17:35:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1840647    
Attachments:
Description Flags
package server error none

Description przem123 2020-05-05 09:20:12 UTC
Created attachment 1685153 [details]
package server error

I updated my openshift cluster from 4.3.18 to 4.4.3. The package server cannot be updated and stays in state "catalog source was removed" all the time. See the screenshot attached.

How to solve this problem ?

My system contains 3 master nodes (coreos) and 2 worker nodes (rhel76). It is a bare metal installation.

Must gather:
https://ibm.box.com/s/tez9s8g8ysbew62im5hyypfuiwbhwdqo

Comment 3 bpeterse 2020-05-26 14:55:32 UTC
Investigating to see if this is essential to 4.5.

Comment 6 shahan 2020-05-28 09:06:14 UTC
After 4.4.5->4.5.0-0.nightly-2020-05-27-040756, the packagesever did not show the message "catalog source was removed"
4.5.0-0.nightly-2020-05-27-040756

Comment 7 errata-xmlrpc 2020-07-13 17:35:00 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409