Bug 1637474

Summary: Hyperconverged deployment fails to proceed with lvcache details
Product: [oVirt] cockpit-ovirt Reporter: Mugdha Soni <musoni>
Component: GdeployAssignee: Rohan CJ <rojoseph>
Status: CLOSED CURRENTRELEASE QA Contact: Mugdha Soni <musoni>
Severity: high Docs Contact:
Priority: high    
Version: 0.11.29CC: bugs, godas, rhs-bugs, sabose, sankarshan, sasundar, sbonazzo
Target Milestone: ovirt-4.2.7Keywords: Regression
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-dashboard-0.11.36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1637468 Environment:
Last Closed: 2018-11-02 14:34:05 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: 1637468    
Attachments:
Description Flags
Screenshot of the error message.
none
Screenshot of the error message.
none
Screenshot of deployment proceeding with lvm cache details none

Description Mugdha Soni 2018-10-09 10:33:49 UTC
Created attachment 1492027 [details]
Screenshot of the error message.

+++ This bug was initially created as a clone of Bug #1637468 +++

Description of problem:
--------------------------------
None of the user input is accepted in SSD parameter under configure LV cache subtab in gluster deployment.When the user clicks on the next button particular error message is displayed " ENTER SSD " despite of the input provided and the deployment does not proceed.


Version-Release number of selected component:
---------------------------------
cockpit-ovirt-dashboard-0.11.35-1.el7ev.noarch
rhvh-4.2.7.1-0.20181003.0+1
ansible-2.7.0-1.el7ae.noarch
gdeploy-2.0.2-29.el7rhgs.noarch

How reproducible:
--------------------------------
Everytime


Steps to Reproduce:
--------------------------------
1.Login to cockpit UI and and start gluster deployment.
2.Configure tabs hosts.FQDN and volumes 
3.Under the bricks tab after user configures the SSD parameter under configure LV cache subtab and clicks on next button the issue is encountered. 

Actual results:
--------------------------------
Error message is displayed " ENTER SSD " despite of the user input and deployment doesnot proceed.


Expected results:
-------------------------------
The error message should not come and the deployment should proceed.

--- Additional comment from Mugdha Soni on 2018-10-09 06:31 EDT ---

Comment 1 Mugdha Soni 2018-10-09 10:34:40 UTC
Created attachment 1492028 [details]
Screenshot of the error message.

Comment 2 Gobinda Das 2018-10-09 11:12:56 UTC
Parth, Can you please check this? And also make sure once user enter device in lvm cache, same has to apply for all hosts.

Comment 3 Parth Dhanjal 2018-10-09 11:17:16 UTC
(In reply to Gobinda Das from comment #2)
> Parth, Can you please check this? And also make sure once user enter device
> in lvm cache, same has to apply for all hosts.

Sure!

Comment 4 Red Hat Bugzilla Rules Engine 2018-10-10 08:54:38 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 5 Gobinda Das 2018-10-12 08:57:39 UTC
I checked in dev environment and not able to reproduce.

Comment 6 Gobinda Das 2018-10-12 09:09:29 UTC
We have new BZ for auto add the device name under the LV Cache column for 2nd and 3rd host: https://bugzilla.redhat.com/show_bug.cgi?id=1638679

Comment 8 SATHEESARAN 2018-10-22 06:09:17 UTC
The issue is fixed with cockpit-ovirt-dashboard-0.11.36

Comment 9 Mugdha Soni 2018-10-22 06:10:54 UTC
Deployment proceeds with LVM cache details. The bug is fixed in cockpit-ovirt-0.11.36 .

Hence moving the bug to verified state.

Comment 10 Mugdha Soni 2018-10-22 06:11:34 UTC
Created attachment 1496294 [details]
Screenshot of deployment proceeding with lvm cache details

Comment 11 Sandro Bonazzola 2018-11-02 14:34:05 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.