Description of problem: There are not default pattern in the kibana for both kubeadmin and non-kubeadmin users. Version-Release number of selected component (if applicable): Baremetal machine launched by IPv6 4.3.0-0.nightly-2020-02-17-205936-ipv6.1 clusterlogging.4.3.4-202002241021 elasticsearch-operator.4.3.4-202002241021 How reproducible: Always Steps to Reproduce: 1. Deploy clusterlogging in IPv6 clusters. 2. Loging kibana via kubeamdin 3. Loging kibana as non-kubeadmin Actual results: No default pattern in kibana. Expected results: The pod log can be displayed in kibana Additional info:
when login as non-admin user. No kibana index wasn't created. + oc exec -c elasticsearch elasticsearch-cdm-plm0aey0-1-cc5d89488-5fnvn -- es_util --query=_cat/shards .searchguard 0 p STARTED 5 37.3kb 127.0.0.1 elasticsearch-cdm-plm0aey0-1 .kibana 0 p STARTED 2 7kb 127.0.0.1 elasticsearch-cdm-plm0aey0-1 project.logjsonx.f118c918-bb9d-4541-976d-78fce7d84b82.2020.02.25 0 p STARTED 4707 2.6mb 127.0.0.1 elasticsearch-cdm-plm0aey0-1 .operations.2020.02.25 0 p STARTED 383456 569.8mb 127.0.0.1 elasticsearch-cdm-plm0aey0-1
Paul Weil 2:12 PM (2 hours ago) to me, Ben, Ben, Jiri, mfisher, Nick, Sam, Christian, Adam Last word I heard from Russell was that 4.4 still needed bugs addressed if they met this specific scope: "The remaining IPv6 bugs against 4.3 can be closed.