[
https://issues.apache.org/jira/browse/METRON-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722906#comment-15722906
]
ASF GitHub Bot commented on METRON-604:
---------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/385
Original Travis error unrelated and fixed by
https://github.com/apache/incubator-metron/pull/383
> Mpack installs do not work on clean machines due to missing Elastic repo
> ------------------------------------------------------------------------
>
> Key: METRON-604
> URL: https://issues.apache.org/jira/browse/METRON-604
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: David M. Lyle
> Assignee: Justin Leet
>
> I cut fresh rpms/mpack for myself following [~justinleet]'s [readme|
> https://github.com/justinleet/metron-rpm]
> 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.
> {noformat}
> [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
> {noformat}
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
