Bug 1551258

Summary:	[ansible] Output is not displayed during playbook execution
Product:	[oVirt] cockpit-ovirt	Reporter:	Phillip Bailey <phbailey>
Component:	Hosted Engine	Assignee:	Phillip Bailey <phbailey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yihui Zhao <yzhao>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.11.12	CC:	bugs, cshao, huzhao, jiaczhan, qiyuan, rbarry, sbonazzo, weiwang, yaniwang, ycui, yzhao
Target Milestone:	ovirt-4.2.2	Flags:	rule-engine: ovirt-4.2+ yzhao: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-05 09:56:32 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:
Embargoed:

Description Phillip Bailey 2018-03-04 02:45:58 UTC

Description of problem:
Ansible output is not displayed during execution.

Version-Release number of selected component (if applicable):
cockpit-ovirt-dashboard-0.11.12-0.1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Enter engine VM FQDN
2. Execute first ansible stage from the Preview sub-step of the first main step by clicking the 'Execute' button

Actual results:
No output is displayed.

Expected results:
Ansible output is displayed.

Additional info:
Problem introduced in https://gerrit.ovirt.org/#/c/87370/.

Comment 1 Yihui Zhao 2018-03-16 07:12:16 UTC

Test with these versions cannot met this issue again:

cockpit-dashboard-160-3.el7.x86_64
cockpit-system-160-3.el7.noarch
cockpit-ovirt-dashboard-0.11.17-1.el7ev.noarch
cockpit-bridge-160-3.el7.x86_64
cockpit-ws-160-3.el7.x86_64
cockpit-storaged-160-3.el7.noarch
cockpit-160-3.el7.x86_64
ovirt-hosted-engine-ha-2.2.7-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.13-1.el7ev.noarch

vdsm-http-4.20.22-1.el7ev.noarch
vdsm-hook-ethtool-options-4.20.22-1.el7ev.noarch
vdsm-network-4.20.22-1.el7ev.x86_64
vdsm-api-4.20.22-1.el7ev.noarch
vdsm-python-4.20.22-1.el7ev.noarch
vdsm-hook-vmfex-dev-4.20.22-1.el7ev.noarch
vdsm-hook-vhostmd-4.20.22-1.el7ev.noarch
vdsm-yajsonrpc-4.20.22-1.el7ev.noarch
vdsm-client-4.20.22-1.el7ev.noarch
vdsm-4.20.22-1.el7ev.x86_64
vdsm-gluster-4.20.22-1.el7ev.noarch
vdsm-hook-vfio-mdev-4.20.22-1.el7ev.noarch
vdsm-common-4.20.22-1.el7ev.noarch
vdsm-hook-openstacknet-4.20.22-1.el7ev.noarch
vdsm-jsonrpc-4.20.22-1.el7ev.noarch
vdsm-hook-fcoe-4.20.22-1.el7ev.noarch

rhvm-appliance-4.2-20180202.0.el7.noarch
OS tree: rhvh-4.2.1.4-0.20180305.0+1

So, I will change the bug's status to verified when it becomes ON_QA.

Comment 2 Yihui Zhao 2018-03-17 07:53:47 UTC

From the Comment 1, change this bug's status to verified.

Comment 3 Sandro Bonazzola 2018-04-05 09:56:32 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.