Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1817353

Summary: local-storage operator does upgrade when installplanstrategy is Automatic
Product: OpenShift Container Platform Reporter: Jatan Malde <jmalde>
Component: StorageAssignee: aos-storage-staff <aos-storage-staff>
Status: CLOSED DUPLICATE QA Contact: Liang Xia <lxia>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.zCC: aos-bugs, ecordell, nhale
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-26 15:55:59 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:

Description Jatan Malde 2020-03-26 08:34:40 UTC 
Description of problem:

IHAC where installing local-storage operator from the OperatorHub initially with 4.2.15 does not move ahead to higher version when 4.2.23 csv version is available in channel 4.2.

Checking the 4.2.23 csv, I could see the 'replaces' value is not available in the csv and as per [1], that value is responsible for upgrading the csv to new version. 

[1] https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/how-to-update-operators.md#upgrade-path

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

OCP 4.2.15 and above

How reproducible:

Steps to Reproduce:
1. Install OCP with 4.2.15 version and then install local-storage operator from operatorhub
2. Once that is done, upgrade the cluster to 4.2.23, verify if the new csv is visible in packagemanifests
3. If it is there and the subscription is set to channel 4.2 and automatic installplanstrategy then it should get upgraded to 4.2.23.

Actual results:
 This is seen specifically with local-storage and it does not moves ahead. If it  is not expected behavior, can we get the replaces value-added.

Expected results:


Additional info:

Attaching attachments from the case,
Comment 4 Red Hat Bugzilla 2024-01-06 04:28:43 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days