BMER - operator upgrade from 4.12 to 4.13 does not work - subs stays at AtLatestKnown and no installplan is created

When catalog source is updated from 4.12 to 4.13, where bmer 4.13 bundle is included, the bmer subscription does not recognize there is a upgradable version. 

BMER subscription says AtLatestKnown and no 4.13 installplan is created. 

4.12 to 4.13 bmer upgrade

100%

1. install 4.12 bmer on 4.13 ocp 
2. update catalogsource to 4.13 which includes 4.13 bmer
3. wait for bmer 4.13 installplan to be created and subs to become UpgradePending

No upgradable bmer version is regonized. Thus nothing happens in subs and no installplan was generated.

bmer ugpraded successfully

Similar issue happened in 4.11-4.12 upgrade for same operator. 

This issue is not seen in TALM, or any other operators on spoke (e.g., ptp, sriov).