Red Hat Bugzilla – Bug 1507870
The events message delayed about 1min to show in events of oc describe clusterservicebroker ansible-service-broker
Last modified: 2018-04-05 05:31:32 EDT
Created attachment 1345828 [details] log Description of problem: The events message delayed about 1min to show in events of oc describe clusterservicebroker ansible-service-broker Version-Release number of selected component (if applicable): atomic-openshift-service-catalog-3.7.0-0.185.0.git.0.e975556.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. setup a OCP cluster with service catalog & ASB 2. check events of clusterservicebroker ansible-service-broker # oc describe clusterservicebroker ansible-service-broker 3. remove caBundle part of it to get error message # oc edit clusterservicebroker ansible-service-broker 4. keep check its events utill we got error message in events # oc describe clusterservicebroker ansible-service-broker Actual results: 4. There do have Error message in status part as soon as caBundle was removed and saved. But error message is not shown in the first minute in Events part. Expected results: 4. Events should show the error message with no delay. As an OCP user, I usually look into the last message in Events of "oc describe" to get the latest info, The delay is not good. Additional info:
I was unable to reproduce the issue in my environment. Can you please check if the issue is still reproducible.
Thanks, Shawn Not reproduced in openshift3/ose-service-catalog:v3.7.0-0.189.0.0 # oc describe clusterservicebroker ansible-service-broker <---snip---> Events: FirstSeen LastSeen Count From SubObjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 2h 3m 27 service-catalog-controller-manager Normal FetchedCatalog Successfully fetched catalog entries from broker. 9s 8s 6 service-catalog-controller-manager Warning ErrorFetchingCatalog Error getting broker catalog: Get https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog: x509: certificate signed by unknown authority
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0636