Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1251928

Summary: Disks Allocations section in new VM/resource allocation Disks Allocation is empty
Product: [oVirt] ovirt-engine Reporter: Vered Volansky <vered>
Component: Frontend.WebAdminAssignee: Idan Shaby <ishaby>
Status: CLOSED CURRENTRELEASE QA Contact: Natalie Gavrielov <ngavrilo>
Severity: low Docs Contact:
Priority: low    
Version: ---CC: amureini, bugs, gklein, ishaby, lsurette, mgoldboi, michal.skrivanek, rbalakri, srevivo, tnisan, ykaul
Target Milestone: ovirt-4.0.4Keywords: UserExperience
Target Release: 4.0.4Flags: rule-engine: ovirt-4.0.z+
rule-engine: planning_ack+
rule-engine: devel_ack+
acanan: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-26 12:34:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot
none
screenshot2
none
snapshot of how it looks now none

Description Vered Volansky 2015-08-10 10:32:59 UTC
Description of problem:
When creating a new VM, in the resource allocation tab, there's a label:
"Disks Allocation:"
With nothing to follow.
There should be a different look to this if it should be displayed, or some statement that there are no options here.
I suppose UX consultant would know better.

Comment 1 Michal Skrivanek 2015-08-11 09:28:13 UTC
this is a known issue when you have no storage available/accessible

Comment 2 Omer Frenkel 2015-08-25 11:58:38 UTC
can you attach a screenshot so it would be clear?

Comment 3 Vered Volansky 2015-08-26 08:52:26 UTC
Created attachment 1067194 [details]
screenshot

Comment 4 Red Hat Bugzilla Rules Engine 2015-10-19 10:58:50 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Moran Goldboim 2016-03-27 08:21:31 UTC
(In reply to Michal Skrivanek from comment #1)
> this is a known issue when you have no storage available/accessible

I think i see the same issue with attached storage domains and when editing functioning vm as well, can you please clarify

Comment 6 Moran Goldboim 2016-03-27 08:22:12 UTC
Created attachment 1140696 [details]
screenshot2

Comment 7 Michal Skrivanek 2016-03-30 14:57:27 UTC
What were your permissions? Any query in engine.log failing?

Comment 8 Moran Goldboim 2016-04-24 11:22:54 UTC
(In reply to Michal Skrivanek from comment #7)
> What were your permissions? 

admin

Any query in engine.log failing?

nothing in the log on INFO level. this should be straight forward from what it looks on my env. doesn't it reproduces on your systems?

Comment 9 Michal Skrivanek 2016-04-25 13:41:59 UTC
this is an existing behavior, it is shown only for a template with disks. the section title should not be there...
I guess it would also make sense to show for New VMs without a template (with redundant information to the main tab with instance images). Or at least grayed out if it can't really be changed, as we try to grey out instead of remove in all the dialogs
The decision is storage's

Comment 10 Allon Mureinik 2016-04-27 11:16:41 UTC
(In reply to Michal Skrivanek from comment #9)
> this is an existing behavior, it is shown only for a template with disks.
> the section title should not be there...
> I guess it would also make sense to show for New VMs without a template
> (with redundant information to the main tab with instance images). Or at
> least grayed out if it can't really be changed, as we try to grey out
> instead of remove in all the dialogs
> The decision is storage's
Definitely doable, and definitely not interesting enough for 4.0.

Comment 12 Tal Nisan 2016-05-16 09:30:13 UTC
Idan, please continue with Vered's patches

Comment 14 Natalie Gavrielov 2016-09-05 15:28:24 UTC
Idan,

The only thing that was changed is in "Edit Virtual Machine"?

Comment 15 Idan Shaby 2016-09-06 05:19:23 UTC
Yes, I removed the unnecessary label "Disks Allocation:" from the "Resource Allocation" tab in the "Edit Virtual Machine" popup.

Comment 16 Natalie Gavrielov 2016-09-07 08:37:14 UTC
Verified, "Disks Allocation:" no longer appears in "Edit Virtual Machine" - "Resource Allocation" tab.

Builds used:
rhevm-4.0.4-0.1.el7ev.noarch
vdsm-4.18.12-1.el7ev.x86_64

Comment 17 Natalie Gavrielov 2016-09-07 08:38:30 UTC
Created attachment 1198586 [details]
snapshot of how it looks now