Description of problem: oc adm diagnostic does not report error after removing endpoint for logging-kibana-ops Version-Release number of selected component (if applicable): v3.9.0-0.24.0 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: [root@host-172-16-120-128 ~]# oc delete endpoints logging-kibana-ops endpoints "logging-kibana-ops" deleted [root@host-172-16-120-128 ~]# oc adm diagnostics aggregatedlogging [Note] Determining if client configuration exists for client/cluster diagnostics Info: Successfully read a client config file at '/root/.kube/config' Info: Using context for cluster-admin access: 'r1-6q/172-16-120-128:8443/system:admin' [Note] Running diagnostic: AggregatedLogging Description: Check aggregated logging integration for proper configuration [Note] Summary of diagnostics execution (version v3.9.0-0.24.0): [Note] Completed with no errors or warnings seen. Expected results: endpoints "logging-kibana-ops" not found Additional info:
An AssetConfig section is being removed from masterConfig and looks like this PR [1] disabled AggregatedLogging diagnostics as a side effect. The PR creates a placeholder loggingURL [2] which was originally retrieved from masterConfig.AssetConfig.loggingPublicURL. The loggingURL is never populated so it skips in Check() [3] silently without any output. [1] https://github.com/openshift/origin/pull/18068 [2] https://github.com/deads2k/origin/blob/04b0801be074eb957fd8f3ab09b785fdc877ee31/pkg/oc/admin/diagnostics/diagnostics/cluster/aggregated_logging/diagnostic.go#L75 [3] https://github.com/deads2k/origin/blob/04b0801be074eb957fd8f3ab09b785fdc877ee31/pkg/oc/admin/diagnostics/diagnostics/cluster/aggregated_logging/diagnostic.go#L180
*** This bug has been marked as a duplicate of bug 1538922 ***