Bug 1569116

Summary: Hyperconverged wizard is not disabled when gdeploy is not present
Product: [oVirt] cockpit-ovirt Reporter: Denis Chaplygin <dchaplyg>
Component: GdeployAssignee: Parth Dhanjal <dparth>
Severity: high Docs Contact:
Priority: high    
Version: 0.11.20CC: bugs, cshao, huzhao, jiaczhan, qiyuan, rbarry, sabose, weiwang, yaniwang, ycui, yzhao
Target Milestone: ovirt-4.2.3Flags: sabose: ovirt-4.2?
sabose: blocker?
sabose: planning_ack?
sabose: devel_ack+
sasundar: testing_ack+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: cockpit-ovirt-0.11.23-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-10 06:28:40 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:

Description Denis Chaplygin 2018-04-18 15:51:07 UTC
Description of problem: When gdeploy is not present user still can run hyperconverged wizard and it will fail

Version-Release number of selected component (if applicable): master

How reproducible: always

Steps to Reproduce:
1. install cockpit and cockpit ovirt plugin
2. Make sure you don't have gdeploy installed on the same host
3. Start hyperconverged setup wizard. It will start successfully and silently fail at the end of the wizard

Actual results: Wizard start and silently fails when i tries to run gdeploy

Expected results: Wizard should not start and tell user, that gdeploy is not available

Comment 1 SATHEESARAN 2018-04-28 08:45:01 UTC
Tested with cockpit-ovirt-dashboard-0.11.23.el7rhgs.

Installation wizard throws warning, and doesn't allows to proceed with installation, when gdeploy is not available

Comment 2 Sandro Bonazzola 2018-05-10 06:28:40 UTC
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 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.