Bug 1770183

Description of problem:
After deploying OCP 4.2 and OCS 4.2 on top of it I see that version of CSV didn't get upgraded after there the new version appeared in catalog source.

$ oc get csv -n openshift-storage
NAME                                        DISPLAY                                VERSION              REPLACES                PHASE
local-storage-operator.4.2.0-201910101614   Local Storage                          4.2.0-201910101614                           Succeeded
ocs-operator.v0.0.213                       Openshift Container Storage Operator   0.0.213              ocs-operator.v0.0.196   Succeeded
$ oc get packagemanifest -n openshift-marketplace |grep local-storag
local-storage-operator                       Red Hat Operators             2d13h
$ oc get packagemanifest -n openshift-marketplace local-storage-operator -o yaml |grep currentCSV
  - currentCSV: local-storage-operator.4.2.1-201910221723


So you can see: Installed version:  4.2.0-201910101614  , from packageManifest: 4.2.1-201910221723

$ oc get subscription -n openshift-storage local-storage-operator-4.2-redhat-operators-openshift-marketplace -o yaml | Grep Automatic
  installPlanApproval: Automatic

I think that this install plan should automatically roll to new build.

This is problematic for me cause I want to in upgrade test and checks on long running cluster if the CSVs are in right version and in success shape.

Is there other way how to get CSV name than from PackageManifest? For example if installPlanApproval will be set to Manual and new build will appear how I can get the current installed name of the CSV? Currently it contain the version in the name: local-storage-operator.4.2.0-201910101614, so if I would like to do oc get local-storage-operator-version I will need to have way how to know which one is installed and suppose to be latest. Thanks

Version-Release number of selected component (if applicable):
CSV:    containerImage: quay.io/openshift/origin-local-storage-operator:4.2.0
Server Version: 4.2.0-0.nightly-2019-11-05-111920
Kubernetes Version: v1.14.6+488792c

How reproducible:
Deployed cluster, kept it running for 2 days, probably new build was pushed to the registry but didn't get rolled.

Steps to Reproduce:
1. Deploy OCP and OCS
2. Wait till new build of local-storage pushed to the registry
3. No upgrade is rolled for that CSV

Actual results:
No upgrade is happening

Expected results:
Roll to the new version of CSV local-storage-operator.4.2.1-201910221723

Not sure how the CSV is defined but is there replaces or skipRange defined? We had similar issue in OCS CSV described here:
https://bugzilla.redhat.com/show_bug.cgi?id=1767400


Additional info:
I have must-gather logs if needed tell me and I will provide them. Also I have the cluster still running.