Bug 1608660 - Support single node deployment from cockpit
Summary: Support single node deployment from cockpit
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Gdeploy
Version: 0.11.29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.2.7
: ---
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1619642 cockpit-ovirt-0.11.37
TreeView+ depends on / blocked
 
Reported: 2018-07-26 06:04 UTC by Gobinda Das
Modified: 2018-11-02 14:33 UTC (History)
4 users (show)

Fixed In Version: cockpit-ovirt-0.11.34-1
Clone Of:
: 1619642 (view as bug list)
Environment:
Last Closed: 2018-11-02 14:33:40 UTC
oVirt Team: Gluster
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)
screenshot of hosted engine setup (44.52 KB, image/png)
2018-08-30 21:46 UTC, Gianluca Cecchi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 93340 0 master MERGED Support for Single node deployment from cockpit 2018-08-06 14:21:04 UTC
oVirt gerrit 93517 0 ovirt-4.2 MERGED Support for Single node deployment from cockpit 2018-08-06 14:21:22 UTC
oVirt gerrit 94122 0 master MERGED Validation for reusing the existing gluster configuration Added a file once the deployment through UI cpompletes or fail... 2018-09-07 13:35:54 UTC
oVirt gerrit 94231 0 ovirt-4.2 MERGED Validation for reusing the existing gluster configuration Added a file once the deployment through UI cpompletes or fail... 2018-09-07 13:36:23 UTC

Description Gobinda Das 2018-07-26 06:04:29 UTC 
Description of problem:
Right now we don't support single node deployment from cockpit.To achieve this user has to create gdeploy conf file and execute manually. 

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


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
There should be some option to deploy single node from cockpit UI.

Additional info:
Comment 1 Gianluca Cecchi 2018-08-30 15:46:53 UTC 
Doesn't work for me in 4.2.6 rc3: ovirt-node-ng-installer-ovirt-4.2-pre-2018082812.iso
Comment 2 Gobinda Das 2018-08-30 16:49:41 UTC 
Did you get any error? Can you please put more details here?
Comment 3 Gianluca Cecchi 2018-08-30 21:43:52 UTC 
I get this window I'm going to attach, telling me that I have to fill in information also for host2 and host3, as it was in 4.2.5
Comment 4 Gianluca Cecchi 2018-08-30 21:46:27 UTC 
Created attachment 1479915 [details]
screenshot of hosted engine setup

In Hosted Engine Setup I select the choice on the right
"
   Hyperconverged 
Configure gluster storage and oVirt hosted engine
" 
and then press the "Start" button.
In the landing page related to gluster setup I have to fill in all 3 hosts/IPs, otherwise I get the error in the attached image
Comment 5 Gianluca Cecchi 2018-09-03 12:07:59 UTC 
Any other information needed?
Did anything changed in this respect between 4.2.6rc3 and final 4.2.6 announced today?
Comment 6 Gobinda Das 2018-09-03 12:14:12 UTC 
I got the issue and fixing it.The fix will be available in 4.2.7 first build.
Comment 7 Sandro Bonazzola 2018-09-03 15:09:49 UTC 
(In reply to Gobinda Das from comment #6)
> I got the issue and fixing it.The fix will be available in 4.2.7 first build.

Can you please update this bug status? Right now it seems it's included in 4.2.6 GA. I'm moving back to MODIFIED and clearing Fixed In Version
Comment 8 Gobinda Das 2018-09-04 05:08:17 UTC 
Moving to POST as another patch required to fix.
Comment 9 bipin 2018-10-12 05:54:48 UTC 
Verified the HE deployment on single node. The workflow works fine.

Tested on RHHI 2.0 ( RHV 4.2 + RHGS 3.4.1)

Steps:
=====
1. Start the installation via cockpit using "single node deployment"
2. Complete the gluster deployment
3. Complete the HE deployment
4. The RHV-M is up and running. Create and attach the gluster network

As the above steps were successfully executed moving the bug to verified.
Comment 10 Sandro Bonazzola 2018-11-02 14:33:40 UTC 
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 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.
Note You need to log in before you can comment on or make changes to this bug.