Bug 1828007 - Operator update is failing due to missing replace field in Operator CSV
Summary: Operator update is failing due to missing replace field in Operator CSV
Keywords:
Status: CLOSED DUPLICATE of bug 1827821
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.4.z
Assignee: Evan Cordell
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On: 1818788
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-26 09:28 UTC by Jian Zhang
Modified: 2020-04-26 15:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-26 15:51:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jian Zhang 2020-04-26 09:28:17 UTC 
====This bug is a clone of bug 1818788 for 4.4 ====


Description of problem:

Updating to OpenShift Container Platform 4.3.8 triggered also `elasticsearch-operator` from being updated. This update though failed and got stuck because the CSV was not correctly rolled and therefore the CSV for the older version was active as well as the CSV for the new version.

This caused a ownership conflict which could only be resolved by manually removing the CSV from the old `elasticsearch` operator version

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

 - OpenShift Container Platform 4.3.8


How reproducible:

 - N/A


Steps to Reproduce:
1. N/A

Actual results:

Update of `elasticsearch-operator` was stuck, impacting additional operators from being able to get installed

Expected results:

Update to work and to avoid one failing part to impact the entire operator installation and update capabilities

Additional info:
Comment 1 Alexander Greene 2020-04-26 15:51:43 UTC 

*** This bug has been marked as a duplicate of bug 1827821 ***
Note You need to log in before you can comment on or make changes to this bug.