Bug 2013811 - Community operator subscription has upgrade available, but will not upgrade
Summary: Community operator subscription has upgrade available, but will not upgrade
Keywords:
Status: CLOSED DUPLICATE of bug 2002276
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.7
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Kevin Rizza
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-13 19:58 UTC by Jordan Bell
Modified: 2021-10-14 16:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-14 16:22:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Template used in ansible script for subscription installation (542 bytes, text/plain)
2021-10-13 19:58 UTC, Jordan Bell
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.