Skip to content
This repository has been archived by the owner on Nov 6, 2024. It is now read-only.

Graylog Puppet Module support for Elasticsearch >= 6 #159

Closed
dfrise opened this issue Jul 27, 2018 · 3 comments · Fixed by #160
Closed

Graylog Puppet Module support for Elasticsearch >= 6 #159

dfrise opened this issue Jul 27, 2018 · 3 comments · Fixed by #160
Assignees
Milestone

Comments

@dfrise
Copy link

dfrise commented Jul 27, 2018

/tmp/vagrant-puppet/modules-18ae87aac2f39a8ff527bd66f25d97c4/profiles/manifests/graylog/elasticsearch.pp throws error during Puppet environment provision

Expected Behavior

Full Puppet environment provision

Current Behavior

[graylog-vagrant-up.log](https://github.com/Icinga/icinga-vagrant/files/2235922/graylog-vagrant-up.log)
==> icinga2-graylog: Error: Evaluation Error: Error while evaluating a Resource Statement, Class[Elasticsearch]: has no parameter named 'repo_version' (file: /tmp/vagrant-puppet/modules-18ae87aac2f39a8ff527bd66f25d97c4/profiles/manifests/graylog/elasticsearch.pp, line: 14, column: 3) on node icinga2-graylog.vagrant.demo.icinga.com

Possible Solution

repo_version parameter is no longer supported by elasticsearch class.
See voxpupuli/puppet-elasticsearch#959

Steps to Reproduce (for bugs)

  1. git clone https://github.com/Icinga/icinga-vagrant && cd icinga-vagrant
  2. cd graylog
  3. vagrant up

Context

icinga2-graylog.vagrant.demo.icinga.com VM creation

Your Environment

  • Vagrant version (vagrant -v): 2.1.2
  • Box name: Icinga/icinga-vagrant/graylog
  • Release version: 7.5
  • Operating system: RHEL
  • Provider (VirtualBox, Parallels, libvirt): VirtualBox-5.2
@dnsmichi
Copy link
Contributor

Hm, crap, I forgot that Elasticsearch has a specific profile for Graylog.

@dnsmichi dnsmichi added this to the 2.0.0 milestone Jul 27, 2018
@dnsmichi dnsmichi self-assigned this Jul 27, 2018
@dnsmichi
Copy link
Contributor

There was a wedding weekend in between, I'm pushing a PR soon ;-)

@dfrise
Copy link
Author

dfrise commented Jul 31, 2018 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants