Bug 1643921
Summary: | Incorrect behavior of IOThreads text box in edit VM dialog | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | meital avital <mavital> | ||||
Component: | Frontend.WebAdmin | Assignee: | Andrej Krejcir <akrejcir> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | meital avital <mavital> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 4.3.0 | CC: | akrejcir, bugs, michal.skrivanek, rbarry | ||||
Target Milestone: | ovirt-4.3.0 | Keywords: | ZStream | ||||
Target Release: | 4.3.0 | Flags: | rule-engine:
ovirt-4.3+
|
||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | ovirt-engine-4.3.0_alpha | Doc Type: | No Doc Update | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 1660055 (view as bug list) | Environment: | |||||
Last Closed: | 2019-02-13 07:43:21 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1660055 | ||||||
Attachments: |
|
Description
meital avital
2018-10-29 12:53:31 UTC
Created attachment 1498550 [details]
screen video
validation done wrong? I think the validation in the UI is ignored. It can be seen in the video, that the textbox turns red, because the value fails validation, but the update operation continues anyway. The wrong value is not sent to backend, as the parameter have to be an integer. This is a duplicate of Bug 1455944 which was closed for capacity reasons. We could write a workaround for this specific case, but it would not fix all the text boxes that expect integers. Verified on : ovirt-engine-4.3.0-0.2.master.20181120211612.git51027b1.el7.noarch This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.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. |