Bug: Kibana 5.1.1 RPM offline-install

[wrightj5]

Kibana version: 5.1.1

Elasticsearch version: 5.1.1

Server OS version: Centos 7

Original install method (e.g. download page, yum, from source, etc.): Yum localinstall kibana-5.1.1.rpm

Description of the problem including expected versus actual behavior:

Not sure where to post this but there's a small bug with the Kibana RPM not assigning the correct permissions when installed on a Centos 7 server in an offline environment.

Specifically, I've noticed that files under /usr/share/kibana/optimize/bundles are owned by several users (root, and kibana) when they should all be owned by Kibana.

Forgive me if this is an issue with how I've installed Kibana. But, as root, I simply ran 'yum localinstall kibana-5.1.1.rpm'

Steps to reproduce:

1. Download Kibana 5.1.1.rpm
2. (as root) - Yum localinstall Kibana-5.1.1.rpm
3. (as root) - cd /usr/share/kibana/optimize/bundles
4. (as root) - ls -al
5. Permissions should be noticeably disparate across the .js files (files owned by root & kibana)
6. Alternatively, just trying to start Kibana will produce EACCESS errors to the .js files owned by root that it's trying to access. It's also always the monitoring*.js files which have alternate ownership.

Edit: Just noticed that this has been reported before (#8818)

[jbudz]

Yep this is the same as #8818, closing in favor of. When installing plugins, kibana generates bundles, which if ran as root will cause the bundles to be owned by root.