TALM may miss MCP reconcile after change to PerformanceProfile or operator upgrade

When upgrading the PAO operator from 4.9 to 4.10 version the CGU showed “complete” ~10 minutes before the master MCP finished reconciling due to change in performance profile MachineConfig.

4.11.3

Always

This procedure emulates the upgrade of a SNO OCP followed by operators.
1. Install cluster with OCP 4.10 and operators taken from the 4.9 catalog.
2. Create a new validator policy which contains (at least) the MCP content from the group-du-validator policy used during installation. Ensure the bindingRules apply this to your cluster.
3. Update common-config: set catalogsource index to 4.10.
4. Update common-subscriptions: Set PAO channel to 4.10
5. Commit and push changes to git
6. Create a CGU to remediate common-config, common-subscriptions, and update-validator (in that order).

The CGU shows "completed" ~10 minutes before the master MCP finishes updating with new rendered master.

CGU shows "completed" after the MCP completes its reconciliation. The update-validator policy should stay non-compliant until that reconciliation completes, however it is seen as compliant 

 the MCP starts updaing.