If a new InstallPlan is created without a valid OperatorGroup (e.g. zero or multiple groups, reference to nonexistent ServiceAccount), the InstallPlan’s phase indefinitely reads Installing. In fact, the only indication is a logged sync error (https://github.com/operator-framework/operator-lifecycle-manager/blob/e5a160aa2a69b4afe3a8da0add98b4083975096c/pkg/controller/operators/catalog/operator.go#L1337). The plan will be requeued several times, but typically reaches the requeue limit and stops because user intervention is required. Fixing the problem doesn't immediately trigger a resync.

The problem in this situation should be exposed to users. Minimally, this could be achieved by marking the InstallPlan "Failed" immediately if this condition is encountered and setting an appropriate message. Ideally, the user can be informed of the problem and given time to correct it before the plan is failed (and the plan should be resynced periodically to avoid the need to delete/re-create or wait).