Red Hat Bugzilla – Bug 1519706
[3.6.1 REF]Shouldn't show .operations index in non-ops kibana
Last modified: 2018-01-23 12:59:00 EST
Description of problem: When ops is enabled, there is still a .operations index in non-ops kibana, when we click the .operations index, the kibana was tring to search records. that is wrong. We should use ops kibana to view operation logs. the .operations index should be deleted in non-ops elasticsearch and kibana Version-Release number of selected component (if applicable): logging-elasticsearch/images/v3.6.173.0.63-12 logging-elasticsearch/images/v3.6.173.0.63-12 logging-auth-proxy/images/v3.6.173.0.63-11 logging-fluentd/images/v3.6.173.0.63-11 How reproducible: always Steps to Reproduce: 1. Deploy logging and enable ops elasticsearch openshift_logging_install_logging=true openshift_logging_image_prefix=registry.example.com/openshift3/ openshift_logging_namespace=logging openshift_logging_es_cluster_size=1 openshift_logging_es_memory_limit=1Gi openshift_logging_use_ops=true openshift_logging_es_ops_memory_limit=1Gi openshift_logging_es_ops_cluster_size=1 openshift_logging_use_mux=true openshift_logging_use_mux_client=true 2. cluster-admin search records in non-ops kibana Actual results: There is a .operations index. Expected results: There isn't .operations index. Additional info:
This should be resolved when https://bugzilla.redhat.com/show_bug.cgi?id=1519705 is resolved.
Enabled ops cluster, .operations index is not shown in non-ops kibana UI Images: logging-kibana/images/v3.6.173.0.89-1 logging-elasticsearch/images/v3.6.173.0.89-1 logging-fluentd/images/v3.6.173.0.89-1 logging-auth-proxy/images/v3.6.173.0.89-1 logging-curator/images/v3.6.173.0.89-1 elasticsearch-plugin in logging-elasticsearch image is openshift-elasticsearch-plugin-2.4.4.20 now bash-4.2$ rpm -qa | grep elasticsearch-plugin openshift-elasticsearch-plugin-2.4.4.20__redhat_1-1.el7.noarch
Created attachment 1369250 [details] enabled ops cluster,kibana UI, there is not .operations index in non-ops kibana UI
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:0113