[METRON-604] Mpack installs do not work on clean machines due to missing Elastic Curator repo

• Type: Bug
• Status: Done
• Priority: Major
• Resolution: Done
• Affects Version/s: 0.3.0
• Fix Version/s: 0.3.1
• Assignee: Justin Leet
• Reporter: David M. Lyle
• Created: 02/Dec/16 14:01
• Updated: 26/Jan/17 22:40
• Resolved: 05/Dec/16 21:40

Description

I cut fresh rpms/mpack for myself following justinleet's readme
Add the mpack to Ambari and then build a fresh 10 node cluster, HDP 2.5.3 and Ambar 2.4.2 (note my last attempt was with HDP 2.5.0 and Ambari 2.4.1 iirc)
Add the services, hit deploy, everything goes fine until it attempts to deploy kibana, the install fails because it cannot find the python-elasticsearch package within the repos we deploy using the mpack.
If I manually add the following repo to the server where Ambari is attempting to install Kibana then I can retry and everything works fine.

[curator-4]
name=CentOS/RHEL 7 repository for Elasticsearch Curator 4.x packages
baseurl=http://packages.elastic.co/curator/4/centos/7
gpgcheck=1
gpgkey=http://packages.elastic.co/GPG-KEY-elasticsearch
enabled=1

I don’t know for sure this is the correct repository for us to use based on the version of ES/Kibana that we’re using, I just know it contains a package which satisfies the dependency requirements and allows the install to complete successfully.

Issue Links

• links to: GitHub Pull Request #385