Bug 905479 - Inconsistent case-sensitivity behaviour in network operations
Summary: Inconsistent case-sensitivity behaviour in network operations
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 3.2.0
Assignee: Lior Vernia
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-29 13:46 UTC by Lior Vernia
Modified: 2016-02-10 19:52 UTC (History)
11 users (show)

Fixed In Version: SF9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 10940 0 None None None Never

Description Lior Vernia 2013-01-29 13:46:41 UTC
Description of problem:

When creating a new network, the check whether the network name is already taken by another network in the same data center is performed case-sensitively (i.e. "mynetwork" and "myNetwork" are considered different names). However, when editing an existing network the check is case-insensitive ("mynetwork" and "myNetwork" are considered the same name).


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


How reproducible:

Always.


Steps to Reproduce:

1. Go to networks main tab.
2. Add network named "mynetwork".
3. Add another network named "myothernetwork".
4. Edit "myothernetwork", try to change name to "myNetwork" --> failure.
5. Add new network named "myNetwork" --> success.
  

Actual results:

Steps (4) and (5) produce different results despite essentially trying to do the same thing.


Expected results:

Either both steps (4) and (5) succeeding or both failing (probably better to be strict and check case-insensitively, meaning that both should fail).


Additional info:

Comment 1 Lior Vernia 2013-02-10 14:13:36 UTC
After further deliberation within the network development team, we decided that for backwards compatibility purposes it is better to remain case sensitive (enabling, for example, "network" and "NETWORK").

Comment 2 Meni Yakove 2013-03-03 15:34:30 UTC
Verified on rhevm-3.2.0-10.10.beta1.el6ev.noarch.

Comment 3 Itamar Heim 2013-06-11 09:28:53 UTC
3.2 has been released

Comment 4 Itamar Heim 2013-06-11 09:31:50 UTC
3.2 has been released

Comment 5 Itamar Heim 2013-06-11 09:47:36 UTC
3.2 has been released


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