Bug 1456778 - Physical Memory Guaranteed validation error highlight doesnt' work
Summary: Physical Memory Guaranteed validation error highlight doesnt' work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.1.3
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ovirt-4.2.0
: ---
Assignee: Phillip Bailey
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-30 11:06 UTC by Michal Skrivanek
Modified: 2017-12-20 11:45 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:45:13 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: planning_ack+
dfediuck: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)
screenshot with fix (146.76 KB, image/png)
2017-09-24 14:25 UTC, Israel Pinto 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 80054 0 master MERGED webadmin: Fix missing validation highlight 2017-08-01 13:22:34 UTC

Description Michal Skrivanek 2017-05-30 11:06:08 UTC 
When you exceed the configured memory by requesting larger phys mem guaranteed the validation blocks you correctly from saving the VM, the Resourca Allocation tab is highlighted with red box, and teh hover popup with error message is there, but the actual Physical Memory Guaranteed  field is missing the red border
Comment 1 Israel Pinto 2017-09-24 14:23:42 UTC 
Verify with:
Software version:4.2.0-0.0.master.20170917124606.gita804ef7.el7.centos

Attached screenshot
Comment 2 Israel Pinto 2017-09-24 14:25:29 UTC 
Created attachment 1330168 [details]
screenshot with fix
Comment 3 Sandro Bonazzola 2017-12-20 11:45:13 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.