Bug 1578334 - The expand cluster(Day 2 operations ) is hung.
Summary: The expand cluster(Day 2 operations ) is hung.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Gdeploy
Version: 0.11.20
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ovirt-4.2.4
: 0.11.25
Assignee: Gobinda Das
QA Contact: Mugdha Soni
URL:
Whiteboard:
Depends On:
Blocks: 1578332 cockpit-ovirt-0.11.28
TreeView+ depends on / blocked
 
Reported: 2018-05-15 10:00 UTC by Mugdha Soni
Modified: 2018-06-26 08:43 UTC (History)
6 users (show)

Fixed In Version: cockpit-ovirt-0.11.25-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1578332
Environment:
Last Closed: 2018-06-26 08:43:22 UTC
oVirt Team: Gluster
Embargoed:
rule-engine: ovirt-4.2?
sasundar: planning_ack?
rule-engine: devel_ack+
sasundar: testing_ack+


Attachments (Terms of Use)
screenshot of gdeploy logs (299.97 KB, image/png)
2018-05-15 10:04 UTC, Mugdha Soni
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 91376 0 master MERGED Changed current obj ref to avoid expand cluster hang issue 2018-05-23 11:38:41 UTC
oVirt gerrit 91532 0 ovirt-4.2 MERGED Changed current obj ref to avoid expand cluster hang issue 2018-05-23 11:38:55 UTC

Comment 1 Mugdha Soni 2018-05-15 10:04:07 UTC
Created attachment 1436754 [details]
screenshot  of gdeploy logs

Comment 2 Mugdha Soni 2018-06-04 11:04:25 UTC
Tested with the following:

(i)redhat-release-virtualization-host-4.2-3.0.el7.x86_64
(ii)gdeploy-2.0.2-27.el7rhgs.noarch
(iii)cockpit-ovirt-dashboard-0.11.999-0.0.master.el7.noarch.rpm

Following are the steps performed for testing:

(i) Successfully deployed gluster and hosted engine.

(ii)Reached out to the gluster management wizard via hosted engine.

(iii)Clicked on the expand cluster button and proceeded with configuring the tabs
 required for expanding the cluster .

(iv) The expand cluster was not hung after the peers were probed.

Comment 3 Sandro Bonazzola 2018-06-26 08:43:22 UTC
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

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