Bug 1386643 - Package rubygem-fluent-plugin-elasticsearch missing from OpsTools OSP 10 repo
Summary: Package rubygem-fluent-plugin-elasticsearch missing from OpsTools OSP 10 repo
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: distribution
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 10.0 (Newton)
Assignee: Lon Hohberger
QA Contact: Udi Shkalim
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-19 11:19 UTC by Ramon Acedo
Modified: 2016-11-03 18:06 UTC (History)
6 users (show)

Fixed In Version: rubygem-fluent-plugin-elasticsearch-1.7.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-20 11:25:21 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.