Bug 1555111

Summary:	FFU: ceph-ansible playbooks are failing when callback_whitelist=profile_tasks is set in /etc/ansible/ansible.cfg
Product:	Red Hat OpenStack	Reporter:	Marius Cornea <mcornea>
Component:	openstack-tripleo-common	Assignee:	Giulio Fidente <gfidente>
Status:	CLOSED ERRATA	QA Contact:	Yogev Rabl <yrabl>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	13.0 (Queens)	CC:	dbecker, gfidente, jschluet, mburns, morazi, rhel-osp-director-maint, slinaber
Target Milestone:	beta	Keywords:	Triaged
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-common-8.6.1-0.20180417180425.19d9b91.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-27 13:36:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marius Cornea 2018-03-14 00:29:08 UTC

Description of problem:
FFU: ceph-ansible playbooks are failing when callback_whitelist=profile_tasks is set in /etc/ansible/ansible.cfg

collect_nodes_uuid parses json output from ansible-playbook command, but it might be polluted with spurious lines if additional output callbacks are enabled

Version-Release number of selected component (if applicable):
openstack-tripleo-common-8.4.1-0.20180224032817.d51ed49.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Deploy OSP10 with ceph osd nodes
2. Upgrade undercloud to OSP13
3. Add callback_whitelist=profile_tasks  to /etc/ansible/ansible.cfg
4. Upgrade overcloud

Actual results:
ceph-ansible playbook fails.

Expected results:
ceph-ansible succeeds

Additional info:

Comment 9 Yogev Rabl 2018-06-21 14:46:57 UTC

verified on openstack-tripleo-common-8.6.1-20.el7ost.noarch

Comment 11 errata-xmlrpc 2018-06-27 13:36:14 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://access.redhat.com/errata/RHEA-2018:2086