Bug 1415644 - [RFE] - Better error handling is required while deploying gluster
Summary: [RFE] - Better error handling is required while deploying gluster
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Gdeploy
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.2.0
: ---
Assignee: Devyani Kota
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks: Gluster-HC-3
TreeView+ depends on / blocked
 
Reported: 2017-01-23 10:35 UTC by RamaKasturi
Modified: 2017-05-10 10:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-10 10:06:59 UTC
oVirt Team: Gluster
Embargoed:
sabose: ovirt-4.2?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.