Bug 1378479 - New package request: rubygem-fluent-plugin-secure-forward
Summary: New package request: rubygem-fluent-plugin-secure-forward
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: fluentd
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ga
: 10.0 (Newton)
Assignee: Lon Hohberger
QA Contact: Udi Shkalim
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 13:49 UTC by Lars Kellogg-Stedman
Modified: 2016-12-14 16:36 UTC (History)
9 users (show)

Fixed In Version: rubygem-fluent-plugin-secure-forward-0.4.3-2.el7
Doc Type: Enhancement
Doc Text:
Feature: Add secure-forward plugin for fluentd. Reason: Allows fluentd to forward logs to a log collector over an encrypted connection.
Clone Of:
Environment:
Last Closed: 2016-12-14 16:36:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:2950 0 normal SHIPPED_LIVE Operational Tools for Red Hat OpenStack Platform 10 Enhancement Advisory 2016-12-14 20:29:53 UTC

Description Lars Kellogg-Stedman 2016-09-22 13:49:41 UTC 
We need the rubygem-fluent-plugin-secure-forward in order to support logging over SSL with fluentd.  mrunge built a package in CBS here:

  http://cbs.centos.org/koji/buildinfo?buildID=12077
Comment 2 Lars Kellogg-Stedman 2016-09-22 14:06:50 UTC 
This package is also under review in Fedora:

  https://bugzilla.redhat.com/show_bug.cgi?id=1369471
Comment 3 Lars Kellogg-Stedman 2016-10-07 19:24:06 UTC 
Set blocker? on this, because we need the secure-forward plugin in order to support logging over SSL.
Comment 15 errata-xmlrpc 2016-12-14 16:36:08 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2950.html
Note You need to log in before you can comment on or make changes to this bug.