Operators resolved together in a namespace are approved and installed together. This is not a bug in OLM.

If anything, I think this may warrant a console bug or RFE to associate installplans with approval, rather than specific operators.

Hi Nick,

> Operators resolved together in a namespace are approved and installed together. This is not a bug in OLM.

Yes, I understand the design. But, as you can see, only the 3scal operaor installed after approve the akka operator, the etcd operator still in pending, is it as expected? Shouldn't approve all of them together?

Besides, the installPlan of the operator still display "false" even if it had been installed: the InstallPlan of the "3scale-community-operator.v0.5.1" still display APPROVED: false. It should display true since it had been installed successfully.
mac:~ jianzhang$ oc get ip
NAME            CSV                                      APPROVAL   APPROVED
install-cmbtw   akka-cluster-operator-certified.v1.0.0   Manual     false
install-gtm6n   3scale-community-operator.v0.5.1         Manual     true
install-gxkvp   3scale-community-operator.v0.5.1         Manual     false

I reopen it, thanks!

Hey Jian,

What operators were included in the install plan that was approved? It seems likely that this was an ordering problem and the actual problem is a UX issue -- the UX where the console is approving or not approving does not properly understand the scope of install plans that resolve multiple operators. To that end, I think this issue should actually be reassigned to the console team for further review (although most likely this should be considered an RFE rather than a bug).

I also think there is a separate problem here, which is that the printer columns for install plans should not have the CSV field at all -- install plans should be resolving multiple CSVs, so the UX is confusing to include that field at all.

I'm reassigning this ticket to the console team for further review, because the underlying implementation is working as expected.

Adding Tony and Peter to the CC list for UX input.

To level-set, what tripped the users up is about "how InstallPlan(s) associated with Operator Subscription(s)" within a namespace.


In this BZ, the user installed 3 Operators in the same namespace, by:
---
Step 1. install 3scale Operator, with “Manual Approval”
    InstallPlan A <--> 3scale Subscription
    
    --> InstallPlan pending: haven’t approved it


Step 2. install akka Operator, with “Manual Approval”
    InstallPlan B <--> akka Subscription
                  <--> 3scale Subscription

   -->  InstallPlan pending: haven’t approved it


Step 3. install etcd Operator, with “Auto Approval”
    InstallPlan C <--> etcd Subscription
                  <--> akka Subscription
                  <--> 3scale Subscription     

    --> InstallPlan pending: haven’t approved it


Step 4. Go to akka Subscription, 
     Find associated InstallPlan B,
     Approve InstallPlan B


Step 5. Since InstallPlan B associates with both akka and 3scale Subscriptions, both Operator got installed 
---


Alternatively, in step 4 of the above scenario, if the user instead:

case A). approved 3scale Operator, 
    --> since InstallPlan A is only associated with 3scale Subscription, only 3scale Operator would be installed.

case B). approved etcd Operator, 
    --> since InstallPlan C is associated with etcd, akka, and 3scale Subscriptions, all three Operators would be installed.
    
    *Side Note: Noticed that the etcd Operator was in fact installed with “Auto Approval”. There is another UI work to help convey this separately.

Currently, Console UI actually has already shown that "InstallPlan B" (in the above scenario) includes components from both "Akka" and "3scale" Operators.

I guess what UI could potentially do more to help here is to call out more explicitly saying in those hint blocks of the InstallPlan details page:
For example (quick idea):

1). Review Manual Install Plan
"Inspect the requirements for the components ___from `Akka` and `3scale` Operators___ specified in this install plan before approving."

2). Review Manual Install Plan
"Once approved, the following resources ___from `Akka` and `3scale` Operators___ will be created in order to satisfy the requirements for the components specified in the plan. Click the resource name to view the resource in detail."

Or something even simpler that highlights the fact that "InstallPlan could be associated with more than one Subscription(s)" and approve this InstallPlan will install all the associated components for those Subscriptions.

UX design: https://docs.google.com/document/d/1YhHJFyDlkKhbvR-BlBmu-1z2TJOVei5JSuv9hArE0zo/edit?usp=sharing

Test with payload 4.7.0-0.nightly-2020-11-22-123106

Console UI is enhanced, when install multiple operators in a same project, can know exactly which components are in every install plan, approve an install plan, only corresponding components are intalled

Can inspect install plan detail from an installed operator also

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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:5633