Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1475707

Summary:	Ansible should configure the engine, even when all of the nodes failed to be configured
Product:	[oVirt] ovirt-engine-metrics	Reporter:	Shirly Radco <sradco>
Component:	Generic	Assignee:	Shirly Radco <sradco>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1.0.5	CC:	bugs, pstehlik, ylavi
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+ ylavi: planning_ack+ rule-engine: devel_ack+ pstehlik: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:00:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1402901, 1475135

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.