Bug 1252525 - For New Data Center dialog need to "jump" to first section with validation error upon click on "OK"
For New Data Center dialog need to "jump" to first section with validation er...
Product: oVirt
Classification: Community
Component: ovirt-engine-webadmin (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: 3.6.0
Assigned To: Alexander Wels
Karolína Hajná
Depends On:
Blocks: 1057386
  Show dependency treegraph
Reported: 2015-08-11 11:42 EDT by Ravi Nori
Modified: 2016-05-19 21:24 EDT (History)
10 users (show)

See Also:
Fixed In Version: 3.6.0-11
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-11-04 06:29:11 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: UX
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 45328 master MERGED webadmin: New datacenter invalid highlight Never
oVirt gerrit 45468 ovirt-engine-3.6 MERGED webadmin: New datacenter invalid highlight Never

  None (edit)
Description Ravi Nori 2015-08-11 11:42:54 EDT
Description of problem:

When creating a new data center leave the name field blank and then navigate to another page of the dialog "MAC Address Pool", then click OK. Nothing visible happens. The dialog does not do anything.

Version-Release number of selected component (if applicable): 3.6

How reproducible: 

Steps to Reproduce:
1. Open New Data Center dialog
2. Leave Name empty
3. Go to "MAC Address Pool" tab
4. click ok

Actual results: Nothing visible happens

Expected results: The user is taken to the dialog where the missing required field should be filled (and is correctly marked in red).
Comment 1 Einav Cohen 2015-08-11 12:07:31 EDT
found during ovirt 3.6 test day when attempting to verify bug 1057386.
Comment 2 Karolína Hajná 2015-09-11 01:58:46 EDT
Verified on 3.6.0-11
Comment 3 Sandro Bonazzola 2015-11-04 06:29:11 EST
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.

Note You need to log in before you can comment on or make changes to this bug.