Bug 1558021

Summary:	When the Hosted Engine Deployment fails the error doesn't report any directory pointing to failed logs
Product:	[oVirt] cockpit-ovirt	Reporter:	bipin <bshetty>
Component:	Hosted Engine	Assignee:	Phillip Bailey <phbailey>
Status:	CLOSED DUPLICATE	QA Contact:	Yihui Zhao <yzhao>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.11.7	CC:	bugs, cshao, huzhao, qiyuan, rbarry, rhs-bugs, sabose, sasundar, sbonazzo, yaniwang, ycui, yzhao
Target Milestone:	ovirt-4.2.4	Flags:	rbarry: ovirt-4.2? bshetty: planning_ack? bshetty: devel_ack? yzhao: testing_ack+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1558018	Environment:
Last Closed:	2018-03-21 11:42:14 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:	1558018

Description bipin 2018-03-19 12:58:41 UTC

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

Description of problem:
While deploying the HE via cockpit, if it error's out (regardless of any issue) the error message no where indicates the log directory where we can check for  messages/debug the issue. 



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
python-ovirt-engine-sdk4-4.2.4-1.el7ev.x86_64


How reproducible:
Everytime


Steps to Reproduce:
1. Login to cockpit finish the Gluster deployment
2. Start the Hosted engine deployment
3. Whenever a failure occurs we don't see a log directory path where the logs are placed

Actual results:
No directory pointed in the UI after the failure

Expected results:
There should be a directory pointed after the failure

Additional info:

Adding the screenshot of the error

Comment 1 Yaniv Kaul 2018-03-19 14:45:05 UTC

I'm quite sure it's a duplicate, can't find it right now.

Comment 2 Ryan Barry 2018-03-19 14:53:13 UTC

I could not either -- patch is already merged from last week, though

Comment 3 Yihui Zhao 2018-03-20 01:55:34 UTC

(In reply to Yaniv Kaul from comment #1)
> I'm quite sure it's a duplicate, can't find it right now.

Is it same as the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1555358

Comment 4 Yihui Zhao 2018-03-21 05:46:46 UTC

Tested with 11.17 , met this issue, I think it is the same as the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1555358

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


*** This bug has been marked as a duplicate of bug 1555358 ***