Created attachment 1632898 [details] video_capture of the issue Description of problem: destroy storage domain is not possible via UI , see the video capture. Version-Release number of selected component (if applicable): rhv-4.4.0-4 (http://bob.eng.lab.tlv.redhat.com/builds/4.4/rhv-4.4.0-4/) ovirt-engine-4.4.0-0.4.master.el7.noarch vdsm-4.40.0-127.gitc628cce.el8ev.x86_64 python3-libvirt-5.0.0-5.module+el8.0.1+3755+6782b0ed.x86_64 qemu-kvm-3.1.0-30.module+el8.0.1+3755+6782b0ed.x86_64 How reproducible: 100% Steps to Reproduce: 1.Try to destroy a storage domain(ISCSI) Actual results: destroy storage domain is not possible via UI , see the video capture. Expected results: Additional info:
Created attachment 1637023 [details] preview_master_17nov19 I tried it on master, I did not see this issue. ( attached a gif ) did I miss something?
(In reply to Ahmad Khiet from comment #1) > Created attachment 1637023 [details] > preview_master_17nov19 > > I tried it on master, I did not see this issue. ( attached a gif ) > did I miss something? Occurs with firefox(66.0.4 (64-bit)) or chrome.( I used Version 78.0.3904.87 (Official Build) (64-bit) ) you can check out the ENV this occurred on(storage-ge-04) for reproduction - you can also debug there.
tried on master build in both chrome and firefox and it did not reproduce! chrome : Version 78.0.3904.97 (Official Build) (64-bit) firefox: 66.0.4 (64-bit)
(In reply to Ahmad Khiet from comment #3) > tried on master build in both chrome and firefox and it did not reproduce! > chrome : Version 78.0.3904.97 (Official Build) (64-bit) > firefox: 66.0.4 (64-bit) did you try it on my ENV(https://storage-ge-04.scl.lab.tlv.redhat.com) which is on formal [rhv-4.4.0-4]? This reproduce each time(see print screen from another attempt I made today)
Created attachment 1639235 [details] Another attempt shows the issue on rhv-4.4.0-4 storage-ge-04 ENV
for now, the issue is not present in master, after testing it in the environment you provided, I saw that it was present in the build you are working on. can you please re-check if it still presents in the next build?
(In reply to Ahmad Khiet from comment #6) > for now, the issue is not present in master, > after testing it in the environment you provided, I saw that it was present > in the build you are working on. > can you please re-check if it still presents in the next build? Yep, it's still here.(see print screen attached) Tested on rhv-4.4.0-6 (http://bob.eng.lab.tlv.redhat.com/builds/4.4/rhv-4.4.0-6/) I sent you a mail with the ENV details you can check it out.
Created attachment 1643017 [details] issue print screen of the issue at rhv-4.4.0-6
FYI, the bug did not appear in master, the 'before' screenshots from rhev.
*rhv Screenshots : https://imgur.com/a/Ckqcic7
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Tag 'ovirt-engine-4.4.0' doesn't contain patch 'https://gerrit.ovirt.org/105763'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.4.0 For more info please contact: infra
Verified on ovirt-engine-4.4.0-0.25.master.el8ev.noarch Both on chrome and ff. Attaching the screenshot of well scaled dialog window for destroying the SD.
Created attachment 1671396 [details] verified
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 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.