Bug 1386643

Summary: Package rubygem-fluent-plugin-elasticsearch missing from OpsTools OSP 10 repo
Product: Red Hat OpenStack Reporter: Ramon Acedo <racedoro>
Component: distributionAssignee: Lon Hohberger <lhh>
Status: CLOSED WONTFIX QA Contact: Udi Shkalim <ushkalim>
Severity: unspecified Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: markmc, mbracho, mburns, mmagr, rtweed, srevivo
Target Milestone: ---   
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-fluent-plugin-elasticsearch-1.7.0-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-20 11:25:21 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 Ramon Acedo 2016-10-19 11:19:35 UTC 
Deploying Fluentd to test OpsTools in OSP 10 requires the package rubygem-fluent-plugin-elasticsearch if you install the server following https://github.com/centos-opstools/opstools-ansible.

The package was available in OSP 9:

$ sudo yum list rubygem-fluent-plugin-elasticsearch
Loaded plugins: search-disabled-repos
Available Packages
rubygem-fluent-plugin-elasticsearch.noarch                                                       0.7.0-1.el7ost                                                       rhel-7-server-openstack-9-optools-rpms

Not having the package makes the Ansible playbook failing to install the Fluentd server.

The current workaround is adding the OSP 9 opstools repo to the server. If this package is to be required in the GA release to build the Fluentd server then we should have it as part of the repo.
Comment 1 Mike Burns 2016-10-19 12:14:29 UTC 
Maria,

Is this something we need in 10? or should we be pushing this out to 11?
Comment 6 RHEL Program Management 2016-10-20 11:25:21 UTC 
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.