Summary: | Creating a new VM with invalid Name errors and exits the form | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ulhas Surse <usurse> | ||||
Component: | ovirt-engine | Assignee: | jniederm | ||||
Status: | CLOSED ERRATA | QA Contact: | Ilanit Stein <istein> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.5.3 | CC: | gklein, juwu, lsurette, mavital, michal.skrivanek, rbalakri, Rhev-m-bugs, yeylon, ykaul | ||||
Target Milestone: | ovirt-3.6.0-rc | ||||||
Target Release: | 3.6.0 | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 3.6.0-4 alpha3 | Doc Type: | Bug Fix | ||||
Doc Text: |
In the Edit Virtual Machine dialog, if an invalid name was entered, the dialog closed and a server-side error was reported. With this update, an invalid virtual machine name is handled in the standard way. The field is highlighted with a red border.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-03-09 21:09:10 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: | |||||
Attachments: |
|
Description
Ulhas Surse
2015-06-27 03:55:13 UTC
Created attachment 1043835 [details]
after error, the form closes and need to fill the information again from start.
the validation seems to be broken (again) (In reply to Michal Skrivanek from comment #2) > the validation seems to be broken (again) in master - ??? pattern in pool dialog is broken too. Verified on 3.6.0-15 For invalid VM name or VM pool name, press OK highlighted in red the name field (mentioning the problem, when pointing on it with mouse cursor), and it didn't exit from the whole form. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0376.html |