Description of problem:

When a OCP 4.8 cluster is upgrade to the latest 4.9.z ( 4.9.47 at the time this report was written), the packageserver stays stuck in v0.17.0, even though the v0.18.3 packgeserver is supposed to roll out. Instead the packgeserver stays stuck in v0.17.0. However, the OLM clusteroperator does not report any failure, inaccurately stating that all of OLM's components were upgraded successfully, and therefore the upgrade was successful.

Version-Release number of selected component (if applicable):

How reproducible:

Always 

Steps to Reproduce:

1. Launch 4.8
2. Upgrade to 4.9.47

Actual results:

Upgrade happens successfully, despite https://issues.redhat.com/browse/OCPBUGS-858 preventing the packageserver from moving to v0.17.0 to v0.18.3

Expected results:

Upgrade is blocked if packageserver CSV (a core component of OLM) is not upgraded to the expected version. 

Additional info: