Bug migrated from Jira & Github Issue:
When an Operator has a manual approval strategy and is able to be installed or upgraded, this isn't particularly apparent to the user since the Installed Operator list view for that operator:
"Initial installation" case:
The "Installed Operators" list view shows "UpgradePending" status
"New Operator version available" case:
The "Installed Operators" list view shows "Upgrading" status
It needs to be more apparent in the list view that "user intervention is needed" to upgrade this Operator.
The console could be displaying "UpgradeAvailable" instead of "UpgradePending" (<-- the current Subscription object `status.state`) when the `spec.installPlanApproval` is set to `Manual`.
--> See related issue OLM-849
We can consider backporting this one.
Still looking into this. Will address in an upcoming sprint.
UX design for this bug seen here: https://docs.google.com/document/d/1SGS314oxVigBbx8V_sp6MvIO_s5KBOEFNEYjpjtIFTo/edit?usp=sharing
Can we make this clearer without needing redesign? Perhaps we can come back on the design elements in 4.6.
The "UX design" is really just changing two statuses (one on the list view and one in subscription details) from "UpgradePending"/"Upgrading" -> "Upgrade Available", with that status also being a link to the InstallPlan. Let me know if we need to rework that for 4.5.
PR is open, but this is not a new issue, I don't believe it should be a 4.5 blocker.
Checked on ocp 4.6 cluster with payload 4.6.0-0.ci-2020-06-04-011434
Install a operator in project, eg "Akka Cluster Operator", when install, choose "Manual" Approval Strategy, click "Install".
On installed operator page, could see status "Upgrade available", click on it, will go to intall plan detail page, click "Preview Install Plan", user could choose "Approve" or "Deny".
The bug is fixed.
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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.