ODF operator install fails when CatalogSources are not talking to their endpoints (Disconnected)    

4.15.z    

Always    

1.  Install OpenShift 4.14 with ODF 4.14 while in disconnected mode

Use oc-mirror to copy and populate the local registry with the following:

4.14 OCP release images
4.14 redhat-operators
4.14 certified-operators
4.14 community-operators 
4.14 redhat-marketplace

Use oc-mirror to copy down the following for v4.15:

4.15 OCP release images
4.15 redhat-operators (for ODF)

Use oc-mirror to copy down the following for v4.16:

4.16 OCP release images 
4.16 redhat-operators 
4.16 certified-operators 
4.16 community-operators 
4.16 redhat-marketplace

2.  Upgrade the OpenShift to 4.15
3.  Update the CatalogSource to v4.15 for `redhat-operators`

UI -> Administration -> Cluster Settings -> Configuration -> OperatorHub -> Sources tab

The other 3 CatalogSources will fail if their Endpoints were switched `v4.15` since they were not mirrored via oc-mirror

certified-operators
community-operators 
redhat-marketplace  

Attempt an installation of the ODF operator (if there were unexpected issues) fails since the other 3 CatalogSources are not in `READY` status    

When CatalogSources are not available, operator installations fail from a working CatalogSource that the operator is part of    

Operator installations for a working CatalogSource should not fail even if there are other CatalogSource's that are not in `READY` status    

Customer is doing a jump upgrade from 4.14 -> 4.15 -> 4.16 and does not need the CatalogSources for the other operators while on 4.15, only for ODF since it is required to be updated during this process   

Workaround to get the ODF v4.15 operator installed, was by going back and changing the endpoint for the failing CatalogSources back to `v4.14` from `v4.15` and have them set to `READY` status