Bug 1555358

Summary:	No logs under /var/log/ovirt-hosted-engine-setup/ deploying hosted-engine from cockpit
Product:	[oVirt] cockpit-ovirt	Reporter:	Simone Tiraboschi <stirabos>
Component:	Hosted Engine	Assignee:	Ido Rosenzwig <irosenzw>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yihui Zhao <yzhao>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.11.12	CC:	bshetty, bugs, cshao, dfediuck, huzhao, irosenzw, jiaczhan, msivak, qiyuan, sbonazzo, weiwang, yaniwang, ycui, yzhao
Target Milestone:	ovirt-4.2.2	Flags:	rule-engine: ovirt-4.2+ ycui: testing_plan_complete? yzhao: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.11.18-0.1	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-29 11:19:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Simone Tiraboschi 2018-03-14 14:38:17 UTC

Description of problem:
No logs under /var/log/ovirt-hosted-engine-setup/ deploying hosted-engine from cockpit.
The folder is empty.

Version-Release number of selected component (if applicable):
cockpit-ovirt-dashboard.noarch        0.11.16-1.el7.centos 

How reproducible:
100%

Steps to Reproduce:
1. Try deploying hosted-engine from cockpit
2. Check /var/log/ovirt-hosted-engine-setup
3.

Actual results:
/var/log/ovirt-hosted-engine-setup is empty

Expected results:
All the relevant logs are saved under /var/log/ovirt-hosted-engine-setup

Additional info:
Didi wrote a great callback plugin for ansible called 2_ovirt_logger but it has to be explicitly white-listed.

HE_ANSIBLE_LOG_PATH env variable has to be set as well with something like:
https://github.com/oVirt/ovirt-hosted-engine-setup/blob/master/src/ovirt_hosted_engine_setup/ansible_utils.py#L135

Comment 1 Yaniv Kaul 2018-03-15 13:22:04 UTC

Personally, I'm not sure how we can release without logs.
(I've just failed to deploy and was quite clueless without logs)

Comment 2 Sandro Bonazzola 2018-03-15 15:33:07 UTC

(In reply to Yaniv Kaul from comment #1)
> Personally, I'm not sure how we can release without logs.
> (I've just failed to deploy and was quite clueless without logs)

I agree, but I see Martin moved to 4.2.3 so I'd like to ask his opinion on this too.

Comment 3 Martin Sivák 2018-03-15 15:39:41 UTC

There are logs for the command line install. But since nobody marked this as a blocker and there is no 4.2.2 compose planned I moved it to 4.2.3.

Comment 4 Yihui Zhao 2018-03-16 06:56:39 UTC

QE can reproduce this issue with these versions:

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

Comment 5 Ryan Barry 2018-03-21 11:42:14 UTC

*** Bug 1558021 has been marked as a duplicate of this bug. ***

Comment 6 Yihui Zhao 2018-03-22 07:45:10 UTC

Tested with cockpit-ovirt-dashboard-0.11.18-1.el7ev.noarch, deploy HE via cockpit , the logs will be generated under /var/log/ovirt-hosted-engine-setup/ .

So, change this bug's status to verified.

Comment 7 Sandro Bonazzola 2018-03-29 11:19:41 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.