When an Operator subscription is configured with a manual approval strategy (approval: Manual), the Operator Lifecycle Manager (OLM) appears to be creating two distinct InstallPlan objects for the same version during installation.
This forces the administrator to manually approve the installation twice, once for each InstallPlan. This creates confusion and adds unnecessary steps to the operator installation process.

    Not always

    1. Create subscription
    2. Approve the install plan 
    3. Check the install plan again
    

    2 Install plans for same operator version gets created.

    1 Install plan should install the operator.

2025-10-16T20:37:02.636897561Z time="2025-10-16T20:37:02Z" level=info msg=syncing id=0p3vn ip=install-9fsq8 namespace=rhacs-operator phase=

2025-10-16T20:37:02.636941760Z time="2025-10-16T20:37:02Z" level=info msg="skip processing installplan without status - subscription sync responsible for initial status" id=0p3vn ip=install-9fsq8 namespace=rhacs-operator phase=

2025-10-16T20:37:02.636963795Z time="2025-10-16T20:37:02Z" level=info msg=syncing id=OyPy0 ip=install-uk4i9 namespace=rhacs-operator phase=RequiresApproval