Created attachment 1184276 [details] snapshot Description of problem: This situation happened only once, for a reason I can't explain, disk profile shows in the drop down list a value "null". Version-Release number of selected component: rhevm-4.0.2-0.1.rc.el7ev.noarch ovirt-imageio-proxy-0.3.0-0.el7ev.noarch ovirt-imageio-common-0.3.0-0.el7ev.noarch How reproducible: Was unable to reproduce yet. Steps to Reproduce: 1. Go to disks tab, "Upload". 2. Fill in fields as in the snapshot attached. 3. Click on Disk options drop down list. Actual results: one of the options is null. Expected results: There is no such option as null.
Tentatively setting to 4.0.4 as we couldn't reproduce this either, yet. Natalie, if you find a good reproducer for this please share it here, and based on that we can consider pretargeting.
See also https://bugzilla.redhat.com/show_bug.cgi?id=1361838
(In reply to Raz Tamir from comment #2) > See also https://bugzilla.redhat.com/show_bug.cgi?id=1361838 Amit, won't the solution for bug 1361838 solve this one too?
Seems it originates from the same problem, though it is required to take a deeper look.
Created attachment 1202990 [details] snapshot Happened again.. using the following builds: rhevm-4.0.4.3-0.1.el7ev.noarch ovirt-imageio-proxy-0.4.0-0.el7ev.noarch ovirt-imageio-common-0.3.0-0.el7ev.noarch vdsm-4.18.13-1.el7ev.x86_64 ovirt-imageio-daemon-0.4.0-0.el7ev.noarc
(In reply to Natalie Gavrielov from comment #5) > Created attachment 1202990 [details] > snapshot > > Happened again.. > using the following builds: > rhevm-4.0.4.3-0.1.el7ev.noarch > ovirt-imageio-proxy-0.4.0-0.el7ev.noarch > ovirt-imageio-common-0.3.0-0.el7ev.noarch > vdsm-4.18.13-1.el7ev.x86_64 > ovirt-imageio-daemon-0.4.0-0.el7ev.noarc bug 1361838 merged to 4.0.4.4, can you update your env and see if the problem still exists? if not, 1361838 did solve this problem and the bug can be closed.
Natalie, few questions - 1. When the window first opened - was the selected value null or did the value only appear when you clicked the drop down (or changed other drop downs selected values) 2. Do you recall how many profiles did you actually have for that domain? Thanks, Liron
(In reply to Liron Aravot from comment #7) > Natalie, few questions - > > 1. When the window first opened - was the selected value null or did the > value only appear when you clicked the drop down (or changed other drop > downs selected values) > > 2. Do you recall how many profiles did you actually have for that domain? > > Thanks, > Liron 1. When opening the drop down list I saw the value null (it wasn't the default value). 2. I didn't configure any profiles, so it's the default one.. (so there was only one).
Hi Natalie, * Was there any error in browser console or ui.log when reproducing it? * Is it still reproduced in latest build?
Created attachment 1246392 [details] ui.log (In reply to Daniel Erez from comment #9) > Hi Natalie, > > * Was there any error in browser console or ui.log when reproducing it? No errors in browser console (I would have attached it if there were any) ui.log didn't show anything interesting (attached). > * Is it still reproduced in latest build? I haven't witnessed it recently
As we didn't manage to reproduce (by modifying responses in debug mode as well) and the issue haven't reproduced lately - I'm closing as WORKSFORME, please reopen if it happens again.
I managed to find the scenario to reproduce that issue: 1. Attempt to perform disk upload 2. Fill a size bigger then the free space available on the selected domain, fill all the other fields as needed. 3. Click 'OK' 4. Error message will appear indicating there's not enough free space on the domain. 5. Select a different domain for the upload 6. null/empty (on 4.1) profile will appear. Natalie, can you please verify that null appears on 4.0 on that scenario?
(In reply to Liron Aravot from comment #12) > I managed to find the scenario to reproduce that issue: > 1. Attempt to perform disk upload > 2. Fill a size bigger then the free space available on the selected domain, > fill all the other fields as needed. > 3. Click 'OK' > 4. Error message will appear indicating there's not enough free space on the > domain. > 5. Select a different domain for the upload > 6. null/empty (on 4.1) profile will appear. > > Natalie, can you please verify that null appears on 4.0 on that scenario? The scenario you descried here is not the one described in comment 0.
I can see at least in the first screenshot, that indeed the provided size is larger than the free size (which aligns with the scenario I found). However, as we didn't find another scenario to reproduce the issue - let's handle this scenario in this bz. If we ever find another scenario causing this, we can open a new bug. Regards, Liron
(In reply to Liron Aravot from comment #14) > I can see at least in the first screenshot, that indeed the provided size is > larger than the free size (which aligns with the scenario I found). > However, as we didn't find another scenario to reproduce the issue - let's > handle this scenario in this bz. > If we ever find another scenario causing this, we can open a new bug. > > Regards, > Liron Agreed. (In reply to Liron Aravot from comment #12) > Natalie, can you please verify that null appears on 4.0 on that scenario? I don't fully understand why you want me to verify what you already reproduced?
I reproduced it on 4,1, I preferred to verify that the reproduction steps are relevant to v4.0 as well (so we can conclude that it's indeed the reproducer).
(In reply to Liron Aravot from comment #12) > I managed to find the scenario to reproduce that issue: > 1. Attempt to perform disk upload > 2. Fill a size bigger then the free space available on the selected domain, > fill all the other fields as needed. > 3. Click 'OK' > 4. Error message will appear indicating there's not enough free space on the > domain. > 5. Select a different domain for the upload > 6. null/empty (on 4.1) profile will appear. > > Natalie, can you please verify that null appears on 4.0 on that scenario? Tested the scenario described above on 4.0.7.4-0.1.el7ev I do get the error message described in step 4, but there is no null/empty profile, so I was unable to recreate this.
Verified using scenario described in comment 12, rhevm-4.1.2-0.1.el7.noarch