Bug 1777144

Summary: operator-lifecycle-manager-packageserver fails to update with OwnerConflict and RequirementsUnknown events
Product: OpenShift Container Platform Reporter: rvanderp
Component: OLMAssignee: Daniel Sover <dsover>
OLM sub component: OLM QA Contact: Salvatore Colangelo <scolange>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: dsover, jiazha
Version: 4.2.z   
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1796913 (view as bug list) Environment:
Last Closed: 2020-05-04 11:17:42 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: 1796913    

Description rvanderp 2019-11-27 02:26:31 UTC
Description of problem:
When updating from 4.1.24 to 4.2.7, update of the operator-lifecycle-manager-packageserver fails with events `unable to adopt APIService` and `requirements not yet checked`.  

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

How reproducible:
Have only seen on this specific cluster, but the upgrade is blocked

Steps to Reproduce:
1. Update cluster from 4.1.24 to 4.2.7
2. Check the state of the `operator-lifecycle-manager-packageserver`
3.

Actual results:
operator-lifecycle-manager-packageserver is failing to update

Expected results:
operator-lifecycle-manager-packageserver should update

Additional info:
This issue may be related to bug https://bugzilla.redhat.com/show_bug.cgi?id=1723818

Comment 16 errata-xmlrpc 2020-05-04 11:17:42 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:0581