CatalogSource status should show the following information - If a `ConfigMap` is missing the status should reflect that. - Any error while setting up the registry pod - Last observed state of the gRPC connection to the registry pod. Currently none of the information is available in the status block of a CatalogSource. How to reproduce: a) 1. Create a `CatalogSource` object that points to an non existing ConfigMap object. Actual Results: - The status block of the CatalogSource will have no information regarding the missing ConfigMap object. Expected Results: - The status block of the CatalogSource displays information regarding the missing ConfigMap. b) 2. Add a ConfigMap object that the above CatalogSource refers to, make sure the fill the `data` section with invalid metadata that causes the registry pod to go into CrashLoop state. For example, you can put a non existing csv name for `currentCSV` inside the channel of the package. Actual Results: - The status block of the CatalogSource will have no information regarding the crash looping registry pod. Expected Results: - The status block of the CatalogSource displays information about the current state of the gRPC connection.
*** This bug has been marked as a duplicate of bug 1737081 ***