Bug 2013811

Summary: Community operator subscription has upgrade available, but will not upgrade
Product: OpenShift Container Platform Reporter: Jordan Bell <jorbell>
Component: OLMAssignee: Kevin Rizza <krizza>
OLM sub component: OperatorHub QA Contact: Jian Zhang <jiazha>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified CC: tflannag
Version: 4.7   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-14 16:22:07 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:
Attachments:
Description Flags
Template used in ansible script for subscription installation none

Description Jordan Bell 2021-10-13 19:58:26 UTC
Created attachment 1832706 [details]
Template used in ansible script for subscription installation

Description of problem:

Community operator (universal-crossplane) subscription is in `state: UpgradeAvailable` with Automatic approval plan, but does not upgrade the operator; currentCSV and installedCSV match, but neither show the latest version of the operator known to be available.

How reproducible:

Some clusters have successfully upgraded to newer version of the operator, but others have not

Steps to Reproduce:
1. Install subscription (see attached)
2. Wait for operator to upgrade

Actual results:

Subscription reaches `state: UpgradeAvailable` and console shows that the operator has an upgrade available, but no upgrade takes place (no new installplans, no changes in currentCSV)

Expected results:

Operator upgrades successfully

Additional info:
Subscription is installed via ansible using template attached

Comment 1 tflannag 2021-10-14 16:22:07 UTC
This reads like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2002276, which has an upstream fix that's already landed in the master branch, but we're running into issues with getting our 4.10 downstream repository back up-and-running due to unrelated issues. Can you attach that support case to the 2002276 BZ?

*** This bug has been marked as a duplicate of bug 2002276 ***