Hide Forgot
Created attachment 1149110 [details] logs: chrome, engine, proxy, vdsm Description of problem: After finishing upload disk operations, sometimes (well, many times..) Trying to do something such as - view disk properties (tabs: virtual machines, storage, permissions) causes an error "operation canceled". Version-Release number of selected component: ovirt-engine-4.0.0-0.0.master.20160310051350.git3151c66.el7.centos.noarch ovirt-image-common-0.1-1.noarch vdsm-4.17.999-724.gitb8cb30a.el7.centos.noarch ovirt-image-daemon-0.1-1.noarch How reproducible: 50% Steps to Reproduce: 1. Upload a disk. 2. After operation completed successfully, switch to one of the other properties tabs: virtual machines, storage, permissions. Actual results: Operation Canceled Error while loading data from server: Download of https://ngavrilo1.scl.lab.tlv.redhat.com/ovirt-engine/webadmin/deferredjs/293BBBD68CBF4ADD714EA2F1CEB1632D/48.cache.js?manualRetry=1&autoRetry=3 failed with status 404(Script Tag Failure - no status available) Expected results: No such errors.
Created attachment 1149111 [details] snapshot
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
Hi I can't reproduce this scenario, can you please provide more info about how to reproduce it? did you do anything specific and got this error except for switching the tabs?
The original issue was reported against: (In reply to Natalie Gavrielov from comment #0) > Version-Release number of selected component: > ovirt-engine-4.0.0-0.0.master.20160310051350.git3151c66.el7.centos.noarch > ovirt-image-common-0.1-1.noarch > vdsm-4.17.999-724.gitb8cb30a.el7.centos.noarch > ovirt-image-daemon-0.1-1.noarch Which we could not reproduce in dev: (In reply to Amit Aviram from comment #5) > Hi > I can't reproduce this scenario, can you please provide more info about how > to reproduce it? did you do anything specific and got this error except for > switching the tabs? Additionally, in last week's face-to-face discussion we found that a significant amount of dev's effort simply did not reach QA due to a misunderstanding on dev's side on how to properly deliver all the way to them. I'm returning this to ON_QA to retest with the newer delivery. If this really doesn't reproduce, we could set it to VERIFIED. If it does, we'll need a more accurate description of the steps to reproduce, if possible. Thanks!
I haven't witnessed this in awhile now.. setting to verified. Builds used: rhevm-4.0.2-0.2.rc1.el7ev.noarch ovirt-imageio-common-0.3.0-0.el7ev.noarch ovirt-imageio-proxy-0.3.0-0.el7ev.noarch vdsm-4.18.6-1.el7ev.x86_64 ovirt-imageio-daemon-0.3.0-0.el7ev.noarch