Bug 1915207 - [UI] user can create more than 1 network with the same name when checking the external provider check box
Summary: [UI] user can create more than 1 network with the same name when checking the...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.4.4.7
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ovirt-4.4.6
: ---
Assignee: eraviv
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-12 09:17 UTC by michal
Modified: 2021-05-05 05:36 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.4.6.6
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-05 05:36:26 UTC
oVirt Team: Network
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 114414 0 master MERGED core: lock when adding external network 2021-04-22 11:24:58 UTC

Description michal 2021-01-12 09:17:50 UTC
Description of problem:

user can create more than 1 network with the same name when checking the external provider check box
Version-Release number of selected component (if applicable):


How reproducible:
in Rhv UI

Steps to Reproduce:
1.Open Network screen
2. Press on 'New' button and add relevant fields, check the check box 'Create on external provider'
3. press on 'ok' button 2 times, or 3 times

Actual results:
user can create more than 1 network with the same name when checking the external provider check box

Expected results:
user can't create more than 1 network with the same name when checking the external provider check box


Additional info:
software version: 4.4.4.7-0.1

Comment 1 Michael Burman 2021-05-02 14:57:15 UTC
Verified on - rhvm-4.4.6.6-0.10.el8ev.noarch

Comment 2 Sandro Bonazzola 2021-05-05 05:36:26 UTC
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.6 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.


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