Comment 7 for bug 1878412

Yoctozepto and Mgoddard, I applied the patches in the link by hand and I was able to successfully deploy with central_logging_enable set in globals. Sorry it took so long, it has been crazy for me the past couple of weeks. Still working out some Monasca details, it timed out the first time on tried to deploy with both central_logging_enable and monasca_enable set. I commented monasca_enable back out and had to delete the ".kibana" index from elasticsearch for it to proceed with the deployment the second time. Attached is a screenshot of the Kibana page when I get "logged in". What I mean is Kibana will give me the username and password prompt and I will input the kibana user and the password from the passwords.yml for kibana and it presents me with the attached screenshot. I did not do a "pip -U kolla-ansible" after applying the patches and I didn't apply any patches to Kolla proper itself, not sure if that is what is causing my issue or not. As for this particular bug, kolla-ansible is pulling the elasticsearch container now so that is working. For the other things, I can submit individual bugs for them later so yall have oversight into them. Thanks for you work in Kolla and Kolla-Ansible. Awesome project. If you need anymore information from me, feel free to let me know. Thanks.

PS. I had to post what was returned on the Kibana page below, had trouble "attaching" a screenshot.

{"message":"Rejecting mapping update to [.kibana] as the final mapping would have more than 1 type: [doc, config]: [illegal_argument_exception] Rejecting mapping update to [.kibana] as the final mapping would have more than 1 type: [doc, config]","statusCode":400,"error":"Bad Request"}