Bug 1383635

Summary: Remove opstools-ansible from oVirt repos
Product: [oVirt] ovirt-distribution Reporter: Sandro Bonazzola <sbonazzo>
Component: GeneralAssignee: Ido Rosenzwig <irosenzw>
Status: CLOSED CURRENTRELEASE QA Contact: Pavol Brilla <pbrilla>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: bugs, didi, lnatapov, pbrilla, sradco
Target Milestone: ovirt-4.1.1-1Keywords: FutureFeature, Rebase
Target Release: ---Flags: sbonazzo: ovirt-4.1?
pbrilla: testing_plan_complete-
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-24 06:28:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Sandro Bonazzola 2016-10-11 10:05:12 UTC
Description of problem:
https://github.com/centos-opstools/opstools-ansible.git provide ansible playbook for handling collectd and fluentd.
We should package it for oVirt consumption.

Comment 1 Sandro Bonazzola 2016-12-12 13:54:48 UTC
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.

Comment 2 Pavol Brilla 2017-01-31 13:12:58 UTC
# yum info opstools-ansible
Available Packages
Name        : opstools-ansible
Arch        : noarch
Version     : 0.0.1
Release     : 0.20161102gitff6aa42.el7
Size        : 68 k
Repo        : ovirt-4.1-pre/7

Comment 3 Yedidyah Bar David 2017-02-01 08:08:22 UTC
Eventually we didn't use opstools-ansible, as that project decided to focus on the server side of things, and the scope of current work is on client side. See also e.g.:

https://review.rdoproject.org/r/4318

We should drop this package from the repos. Moving to assigned for now.

Comment 4 Red Hat Bugzilla Rules Engine 2017-02-01 08:08:28 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Yedidyah Bar David 2017-03-13 08:39:48 UTC
Changed the summary according to comment 3.