Bug 1382751

Summary: kibana dasboard not being saved
Product: Red Hat OpenStack Reporter: Pratik Pravin Bandarkar <pbandark>
Component: kibanaAssignee: Matthias Runge <mrunge>
Status: CLOSED NOTABUG QA Contact: Udi Shkalim <ushkalim>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: cshastri, mrunge, pbandark
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-11 05:34:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Pratik Pravin Bandarkar 2016-10-07 15:27:22 UTC 
Description of problem:
kibana dasboard not being saved if we move Elasticseach behind a proxy. The Red Hat Operational tools were installed according to the documentation. While using the Kibana dasboard I noticed the "save dashboard" function doesn't work. The following underlying error is causing this issue:
---
<h1>Method Not Allowed</h1>
<p>The requested method PUT is not allowed for the URL /kibana-int/dashboard/test.</p>
</body></html>
---



Version-Release number of selected component (if applicable):
RHOS8,9

How reproducible:
100%

Steps to Reproduce:
1. Configure Centralized Logging as per [1].
2. at step 10, make sure you secure the virtual host using HTTP Basic authentication and move Elasticseach behind a proxy.
3. Try to save dashboard from kibana GUI. Nothing will happen. 



Actual results:
kibana dasboard not being saved

Expected results:
There should be no any issue while saving kibana dashboard. 

Additional info:
Comment 1 Pratik Pravin Bandarkar 2016-10-07 15:27:39 UTC 
[1] https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/single/red-hat-openstack-platform-operational-tools/#installing_the_centralized_logging_suite
Comment 3 Pratik Pravin Bandarkar 2016-10-09 15:38:03 UTC 
kibana-3.1.2-2.el7ost.noarch
elasticsearch-1.5.2.redhat_1-11.el7.noarch
Comment 8 Chaitanya Shastri 2016-10-10 13:11:50 UTC 
Adding the following in kibana3.conf file seems to fix the issue:

# Proxy for kibana-int/{dashboard,temp}
<LocationMatch "^/(kibana-int/dashboard/|kibana-int/temp)(.*)$">
  ProxyPassMatch http://127.0.0.1:9200/$1$2
  ProxyPassReverse http://127.0.0.1:9200/$1$2
</LocationMatch>

Thank you!!
Comment 12 Matthias Runge 2016-10-11 05:34:32 UTC 
With the findings here, I'll close this bug, it's a documentation issue.