Description of problem: Diagnostics logging on a healthy openshift env, reported an error: # 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: 'openshift-logging/qe-qitang-311-gce-master-etcd-1:8443/system:admin' [Note] Running diagnostic: AggregatedLogging Description: Check aggregated logging integration for proper configuration ERROR: [AGL0065 from diagnostic AggregatedLogging@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/aggregated_logging/diagnostic.go:129] Did not find a DeploymentConfig to support component 'curator' Info: Did not find a DeploymentConfig to support optional component 'curator-ops'. If you require this component, please re-install or update logging and specify the appropriate variable to enable it. Info: Did not find a DeploymentConfig to support optional component 'es-ops'. If you require this component, please re-install or update logging and specify the appropriate variable to enable it. Info: Did not find a DeploymentConfig to support optional component 'kibana-ops'. If you require this component, please re-install or update logging and specify the appropriate variable to enable it. Info: Did not find a DeploymentConfig to support optional component 'mux'. If you require this component, please re-install or update logging and specify the appropriate variable to enable it. Info: Looked for 'logging-es-ops' among the logging services for the project but did not find it. This optional component may not have been specified by logging install options. Info: Looked for 'logging-es-ops-cluster' among the logging services for the project but did not find it. This optional component may not have been specified by logging install options. Info: Looked for 'logging-kibana-ops' among the logging services for the project but did not find it. This optional component may not have been specified by logging install options. Info: Looked for 'logging-mux' among the logging services for the project but did not find it. This optional component may not have been specified by logging install options. [Note] Summary of diagnostics execution (version v3.11.0-0.19.0): [Note] Errors seen: 1 Version-Release number of selected component (if applicable): openshift v3.11.0-0.19.0 kubernetes v1.11.0+d4cacc0 logging-elasticsearch5-v3.11.0-0.19.0.0 logging-fluentd-v3.11.0-0.19.0.0 logging-kibana5-v3.11.0-0.19.0.0 How reproducible: Always Steps to Reproduce: 1.Deploy logging 2.execute 'oc adm diagnostics AggregatedLogging' 3. Actual results: Diagnostics logging report an error: Did not find a DeploymentConfig to support component 'curator' Expected results: Aggregated logging diagnostics should report: Logging system running healthy & no issue found. Additional info:
Lowering the priority to remove from blocker as this is not.
Moving to target release 4.0
To be clear, the problem is that curator is now a scheduled job and not a deploymentconfig? The diagnostics/health check needs to be updated to reflect this too?
(In reply to Mark McKinstry from comment #3) > To be clear, the problem is that curator is now a scheduled job and not a > deploymentconfig? correct > The diagnostics/health check needs to be updated to > reflect this too? correct
Will this be fixed on 3.11.z ?
*** This bug has been marked as a duplicate of bug 1676720 ***