Bug 1592842

Summary: [UI] - Allow to create a subnet with Unicode characters(Hebrew)
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Dan Kenigsberg <danken>
Status: CLOSED WONTFIX QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.2.4.1CC: bugs, ylavi
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-24 07:46:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Burman 2018-06-19 12:31:03 UTC 
Description of problem:
[UI] - Allow to create a subnet with Unicode characters(Hebrew) 

We have a validation when trying to create a subnet with unicode characters in the UI(accept only 'a-z' 'A-Z' '0-9' and '_' '-'

In rest it is allowed to create a subnet with unicode characters and it is working. The subnet is created and displayed in the UI(with Hebrew for example), if it's working via rest then we should allow this also in the UI.

https://10.35.x.z:9696/v2.0/networks - POST

{
    "network": {
        "name": "שתיים"

    }
}

201 Created

{
"network":{
"status": "ACTIVE",
"tenant_id": "00000000000000000000000000000001",
"id": "be4e99c4-171e-4d18-8ea3-d5ffd2c5d4aa",
"name": "שתיים"


Version-Release number of selected component (if applicable):
4.2.4.4-0.1.el7_3

How reproducible:
100%

Steps to Reproduce:
1. Try to create subnet with unicode characters(Hebrew)
2. Create subnet with unicode characters(Hebrew)

Actual results:
1. Can't, there is a validtion in the UI
2. Succeeded

Expected results:
1. Should be allowed if allowed in rest

Additional info:
See also - BZ 1527828
Comment 1 Michael Burman 2018-06-19 12:35:50 UTC 
https://10.35.x.z:9696/v2.0/subnets - POST

{
    "subnet": 
        { 
            "name": "אחד",
            "gateway_ip": "11.0.0.100",
            "enable_dhcp": true,
            "network_id": "1a3f0370-85b0-4db9-80b3-0fe909691528",
            "cidr": "11.0.0.0/24",
            "dns_nameservers": [
                "8.8.8.8"
            ]
        }
    
}

201 Created

{
"subnet":{
"ip_version": 4,
"allocation_pools":[
{
"start": "11.0.0.2",
"stop": "11.0.0.255"
}
],
"gateway_ip": "11.0.0.100",
"name": "אחד",
"enable_dhcp": true,
"network_id": "1a3f0370-85b0-4db9-80b3-0fe909691528",
"tenant_id": "00000000000000000000000000000001",
"cidr": "11.0.0.0/24",
"dns_nameservers":[
"8.8.8.8"
],
"id": "67413c22-c3c1-4684-ab60-40c6df5743d8"
}
}
Comment 2 Yaniv Lavi 2018-06-24 07:46:35 UTC 
This is not a interesting use case.
We do not support subnets from engine.