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

Bug 1558053

Summary:	No log files found on Hosted Engine deploying Host after a failure via cockpit
Product:	[oVirt] cockpit-ovirt	Reporter:	bipin <bshetty>
Component:	Hosted Engine	Assignee:	Ryan Barry <rbarry>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yihui Zhao <yzhao>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.11.7	CC:	bugs, cshao, huzhao, jiaczhan, qiyuan, rhs-bugs, sabose, sasundar, weiwang, yaniwang, ycui, yzhao
Target Milestone:	ovirt-4.2.2	Flags:	rbarry: ovirt-4.2? bshetty: planning_ack? rule-engine: devel_ack+ yzhao: testing_ack+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.11.18-0.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1558051	Environment:
Last Closed:	2018-03-29 11:02:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1558051

Description bipin 2018-03-19 14:12:14 UTC

+++ This bug was initially created as a clone of Bug #1558051 +++

Description of problem:
During a RHV based HE deployment failure (via cockpit) no error logs are reported in the directory
/var/log/ovirt-hosted-engine-setup. 
Could not debug on the root cause since there are no logs placed

Version-Release number of selected component (if applicable):
cockpit-ovirt-dashboard-0.11.17-1.el7ev.noarch
ovirt-hosted-engine-ha-2.2.7-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.13-1.el7ev.noarch

How reproducible:
100%


Steps to Reproduce:
1.Login to cockpit finish the Gluster deployment
2.Start the Hosted engine deployment
3.If any failure occurs, go to the host and see that no log files are generated under /var/log/ovirt-hosted-engine-setup

Actual results:
No log files generated

Expected results:
Log files should be generated


Additional info:
I got a deployment failure on 19th marhc but no logs could be found

[root@rhsqa-grafton7-nic2 ovirt-hosted-engine-setup]# ls -lt
total 78760
-rw-r--r--. 1 root root  324108 Mar 16 11:59 ovirt-hosted-engine-setup-20180316115058-aupn0a.log
-rw-r--r--. 1 root root  214838 Mar 16 11:59 ovirt-hosted-engine-setup-ansible-final_clean-20180316115945-ijljm3.log
-rw-r--r--. 1 root root 1812502 Mar 16 11:59 ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20180316115259-0e03v5.log
-rw-r--r--. 1 root root  274191 Mar 16 11:52 ovirt-hosted-engine-setup-ansible-initial_clean-20180316115249-wpgx17.log
-rw-r--r--. 1 root root  419554 Mar 16 11:51 ovirt-hosted-engine-setup-ansible-get_network_interfaces-20180316115112-aand5j.log

Comment 1 Yihui Zhao 2018-03-21 06:46:18 UTC

Tested with 11.17, can reproduce this issue.

Comment 2 Yihui Zhao 2018-03-22 07:42:08 UTC

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


So, change this bug's status to verified.

Comment 3 Sandro Bonazzola 2018-03-29 11:02:50 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.