Description of problem: ------------------------ As part of replace host workflow, the particular case here is replacing the primary volfile server (ie) the server used to mount the gluster volume corresponding to the storage domain. When its replaced, the storage domains needs to be edited to contain the new server info. When updating the storage domain, it throws 'operation cancelled dialog box', but still the value is updated and storage domain is rightly mounted Version-Release number of selected component (if applicable): -------------------------------------------------------------- RHV 4.4.1 RHHI-V 1.8 How reproducible: ----------------- Always Steps to Reproduce: --------------------- 1. Poweroff the VMs running on the storage domain 2. Move the storage domain to maintenance 3. Click on 'Manage domain' and edit the path field to point to different gluster storage server / HC host 4. Press ok Actual results: --------------- Error dialog opens with 'operation cancelled', but path gets updated Expected results: ----------------- No error dialog box, and path should get update as it is now --- Additional comment from RHEL Program Management on 2020-07-06 05:12:43 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-06 05:13:55 UTC ---
can you please attach a screenshot of the bug, also the error logs from the engine? Thanks
(In reply to Ahmad Khiet from comment #1) > can you please attach a screenshot of the bug, also the error logs from the > engine? > Thanks Hello Ahmad. I will attach the screenshot shortly, but I do not have engine logs. My bad, that I felt that the issue was straight forward and haven't captured the engine log.
Created attachment 1713550 [details] Error screenshot
Hello Ahmad, Let me know, if you still need engine.log, I can reproduce the issue and attach the required logs. Advance Thanks.
Hi, The screenshot really helped to investigate the bug, I need one more screenshot for the screen where you edit the path of a working glusterfs storage. Thank you
Created attachment 1714287 [details] Recording of editing the glusterfs storage domain Recording of the issue is attached here
Created attachment 1714288 [details] engine.log.tar.gz
(In reply to SATHEESARAN from comment #7) > Created attachment 1714288 [details] > engine.log.tar.gz Hello Ahmad, I have also captured engine.log and attached to the bug
(In reply to SATHEESARAN from comment #8) > (In reply to SATHEESARAN from comment #7) > > Created attachment 1714288 [details] > > engine.log.tar.gz > > Hello Ahmad, > > I have also captured engine.log and attached to the bug Hi SATHEESARAN, Are all the glusterfs storages are identical in block size configuration? is the new changed storage has different block size value than the current storage? can you please attach vdsm logs?
(In reply to Ahmad Khiet from comment #9) > (In reply to SATHEESARAN from comment #8) > > (In reply to SATHEESARAN from comment #7) > > > Created attachment 1714288 [details] > > > engine.log.tar.gz > > > > Hello Ahmad, > > > > I have also captured engine.log and attached to the bug > > Hi SATHEESARAN, > > Are all the glusterfs storages are identical in block size configuration? is > the new changed storage has different block size value than the current > storage? > > can you please attach vdsm logs? Hi Ahmad, Yes, all glusterfs storages are identical in block size configuration. I'm just changing the server that I used to mount, the gluster volume remains the same before and after that edit in the storage domain. Its only the gluster volfile server FQDN is updated, so that the mount will happen from new server, on the existing host. Nothing else changes. I do not have vdsm logs, its quite easily always reproducible.
Any update on this?
I'm submitting a patch fixing this bug soon.
Tested with RHV 4.4.3 ( 4.4.3.10-0.1.el8ev ) 1. Poweroff the VMs running on the storage domain 2. Move the storage domain to maintenance 3. Click on 'Manage domain' and edit the path field to point to different gluster storage server / HC host 4. Press ok No error dialog is seen
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.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.