Multiple operatorGroup error in subscription status

[awgreene]

Problem: When reconciling subscriptions in a namespace, OLM will error out if multiple operatorGroups exist in the namespace when deciding if the fail-forward feature is enabled. The failure is only loged and not surfaced in the status of the subscription.

Solution: By assuming that fail forward is disabled when more than one operatorGroups are found in a namespace, the syncResolvingNamespace function will attempt to find upgrades using the resolver which will fail due to multiple operatorGroups in the namespace anyways and portray this information in the subscription status.

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awgreene

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ~~OWNERS~~ [awgreene]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ankitathomas, awgreene

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ~~OWNERS~~ [awgreene]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[perdasilva]

@awgreene could you please rebase? I can't do it from this side =(

[openshift-ci[bot]]

New changes are detected. LGTM label has been removed.

[openshift-merge-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.