Bug 1475707 - Ansible should configure the engine, even when all of the nodes failed to be configured
Summary: Ansible should configure the engine, even when all of the nodes failed to be ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: Generic
Version: 1.0.5
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Shirly Radco
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks: oVirt-Metrics-and-Logs 1475135
TreeView+ depends on / blocked
 
Reported: 2017-07-27 08:07 UTC by Shirly Radco
Modified: 2017-12-20 11:00 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:00:12 UTC
oVirt Team: Metrics
Embargoed:
rule-engine: ovirt-4.2+
ylavi: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 80398 0 master POST refactor metrics ansible playbook 2017-08-09 15:03:39 UTC
oVirt gerrit 81460 0 ovirt-engine-metrics-4.1 POST refactor metrics ansible playbook 2017-09-05 12:53:43 UTC

Description Shirly Radco 2017-07-27 08:07:50 UTC 
Description of problem:
In ansible, if an entire PLAY failed it will not continue to the next PLAY.
For example, if we have  1 node and 1 engine and the node fluentd/collectd failed then the playbook will stop and will not try to configure the engine, even though it is in a different inventory group.

Version-Release number of selected component (if applicable):
1.0.5

How reproducible:
100%

Steps to Reproduce:
1. Have ovirt env with 1 node and engine.
2. Remove a collectd/fluentd package from the node and remove the repository that provides it.
3. Run the ovirt metrics machine setup script.


Actual results:
Playbook will stop once it can't fing the package that it tries to install and will not try to configure the oVirt engine.

Expected results:
Playbook should try to configure all nodes and engine.


Additional info:
Comment 1 Yaniv Kaul 2017-07-27 12:03:18 UTC 
Doesn't sounds like a FutureFeature to me?
Comment 2 Lukas Svaty 2017-09-21 16:04:54 UTC 
verified in ovirt-engine-metrics-1.1.1-0.0.master.20170919065728.el7.centos.noarch
Comment 3 Sandro Bonazzola 2017-12-20 11:00:12 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.