Bug 1415644

Summary:	[RFE] - Better error handling is required while deploying gluster
Product:	[oVirt] cockpit-ovirt	Reporter:	RamaKasturi <knarra>
Component:	Gdeploy	Assignee:	Devyani Kota <dkota>
Status:	CLOSED WORKSFORME	QA Contact:	RamaKasturi <knarra>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, cshao, dguo, sabose, ycui, yzhao
Target Milestone:	ovirt-4.2.0	Keywords:	FutureFeature
Target Release:	---	Flags:	sabose: ovirt-4.2? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
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:	2017-05-10 10:06:59 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:	1411323

Description RamaKasturi 2017-01-23 10:35:22 UTC

Description of problem:
I had encountered an issue where cockpit-ovirt gdeploy plugin failed to install ovirt-engine-appliance and it just says 'Deployment Failed'. Installing ovirt-engine-appliance is a last step in deployment and all other steps are executed successfully. 

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

How reproducible:



Steps to Reproduce:
1. Install latest cockpit-ovirt-dashboard
2. Login to the UI
3. Provide all the inputs and make sure that ovirt-engine-appliance rpm is not present on any repos on the system.

Actual results:
plugin fails to install ovirt-engine-appliance and it gives an error message saying " Deployment Failed"

Expected results:
I think it is not a good idea to show  "Deployment Failed" even if one of the step fails . There should be a better error handling in such cases.

Additional info:

Comment 1 Sahina Bose 2017-05-10 10:06:59 UTC

ovirt-engine-appliance is installed as part of HE deployment, so this usecase is no longer valid. Closing this bug