Bug 1401840 - package rubygem-fluent-plugin-rewrite-tag-filter
Summary: package rubygem-fluent-plugin-rewrite-tag-filter
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-distribution
Classification: oVirt
Component: General
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.1.0-beta
: 4.1.0
Assignee: Sandro Bonazzola
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-06 08:52 UTC by Yedidyah Bar David
Modified: 2019-04-28 13:54 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-15 14:57:13 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.1+

Attachments (Terms of Use)

Description Yedidyah Bar David 2016-12-06 08:52:12 UTC 
Description of problem:

Our planned metrics framework [1] requires ruby gem fluent-plugin-rewrite-tag-filter.

Currently added it to [2] from a fedora copr build, and emailed [3] centos-devel
about adding it to the centos opstools sig.

[1] http://www.ovirt.org/develop/release-management/features/engine/metrics-store/
[2] https://gerrit.ovirt.org/67738
[3] https://lists.centos.org/pipermail/centos-devel/2016-December/015444.html
Comment 1 Sandro Bonazzola 2016-12-06 08:57:24 UTC 
Published on ovirt-master-snapshot-static, will be in next beta compose
Comment 2 Pavol Brilla 2017-02-02 16:04:45 UTC 
# dnf list rubygem-fluent-plugin-rewrite-tag-filter.noarch
Last metadata expiration check: 0:32:24 ago on Thu Feb  2 16:28:06 2017.
Available Packages
rubygem-fluent-plugin-rewrite-tag-filter.noarch                                                                       1.5.5-1.fc24                                                                        ovirt-4.1
# dnf repolist
repo id                        repo name                             status
*fedora                        Fedora 24 - x86_64                    49,722
ovirt-4.1                      Latest oVirt 4.1 Release                 327
...
Note You need to log in before you can comment on or make changes to this bug.