Description of problem: ------------------------- Create a 6 node RHHI-V deployment. Post the RHHI-V deployment, try to expand the volume from web console ( cockpit ). Cockpit errors out and dialog box is closed Version-Release number of selected component (if applicable): -------------------------------------------------------------- cockpit-ovirt-dashboard-0.14.9 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Create a 6 node RHHI-V deployment 2. Try expanding the volume but using 'Manager Gluster' > 'Expand volume' Actual results: ---------------- Dialog opens up, after selecting the hosts, proceeding to next tab, dialog closes. Expected results: ------------------ Expand volume should be successful --- Additional comment from RHEL Program Management on 2020-07-14 07:46:01 UTC --- This bug is automatically being proposed for RHHI-V 1.8 release at Red Hat Hyperconverged Infrastructure for Virtualization product, by setting the release flag 'rhiv‑1.8' to '?'. If this bug should be proposed for a different release, please manually change the proposed release flag. --- Additional comment from SATHEESARAN on 2020-07-14 07:54:18 UTC --- Additional info: ---------------- The following is the error message seen in the browse console: TypeError: "this.state.bricksList[this.state.selectedHost.hostIndex] is undefined" cockpit localhost/ovirt-dashboard/app.js:58 cockpit localhost/ovirt-dashboard/app.js:27 cockpit localhost/ovirt-dashboard/app.js:27 cockpit localhost/ovirt-dashboard/app.js:27 cockpit localhost/ovirt-dashboard/app.js:27 cockpit localhost/ovirt-dashboard/app.js:27
I expect this is related to bz 1856685 - which shows a similar behaviour on gluster volumes. So also the same guidance applies: This should work with any number of gluster nodes - so we should test all supported combinations (which I hope we already do). One additional question: Is that the documented default procedure for creating new gluster volumes on a hyperconverged environment?
(In reply to Martin Tessun from comment #1) > I expect this is related to bz 1856685 - which shows a similar behaviour on > gluster volumes. > > So also the same guidance applies: > This should work with any number of gluster nodes - so we should test all > supported combinations (which I hope we already do). > Yes RHHI-V supports till 12 nodes cluster and we are testing all supported combinations. > One additional question: Is that the documented default procedure for > creating new gluster volumes on a hyperconverged environment? In Day2 operation we provide option for user to create New Gluster volume which is documented in RHHI-V guide.
*** This bug has been marked as a duplicate of bug 1859085 ***