OLM sometimes creates two install plans for a subscription about kubectl-operator HOT 1 OPEN

Update: I just attempted to reproduce this issue, and I noticed that kubectl operator approved the "wrong" install plan. Looking at the kubectl operator code, it appears as if it:

1. Creates the subscription
2. Waits for the subscription's status.installPlanRef to be set.
3. Fetches the install plan found in 2)
4. Updates the install plan found in 2) by setting spec.approved to true.

Therefore, OLM is setting an install plan reference on the subscription and then (sometimes) immediately re-reconciling the subscription, creating another install plan, and then updating the install plan reference, rendering the first approved install plan inert. When kubectl operator is fast enough (or OLM is slow enough), kubectl operator is able to pick up the first install plan just before it becomes inert, eventually causing the install to timeout and fail.

from kubectl-operator.