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:
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").
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: