Description of problem:
Managed service cluster with ocs-provider-dev addon has been successfully installed. The addon moved back to installing state without any change in addon configuration. This happened within a day. After 1 day of running the cluster it was noticed.

Version-Release number of selected component (if applicable):
ocs-osd-deployer.v2.0.8

How reproducible:
1/1

Steps to Reproduce:
1.Install provider cluster:
rosa create service --type ocs-provider-dev --name <name> --machine-cidr 10.0.0.0/16 --size 4 --onboarding-validation-key <key> --subnet-ids <subnets> --region us-east-1
2. Check that addon got installed correctly:
rosa list addons -c <name>
3. Add consumer to the cluster.
4. Wait few hours/a day.
5. Check addon status again:
rosa list addons -c fbalak22-pr

Actual results:
At first the addon was installed but next day it moved to installing phase. The ocs-osd-deployer.v2.0.8 is also in installing phase.

Expected results:
Addon should stay in ready state.

Additional info:
There were included changes related to pricing epic in time of installation the dev addon.

In events of the csv is:
Events:
  Type     Reason              Age                    From                        Message
  ----     ------              ----                   ----                        -------
  Warning  InstallCheckFailed  4m53s (x525 over 27h)  operator-lifecycle-manager  install timeout

Logs from deployment showing that the addon got into ready state: https://ocs4-jenkins-csb-odf-qe.apps.ocp-c1.prod.psi.redhat.com/job/qe-deploy-ocs-cluster/18256/consoleFull