Designate DNS – create TLD using valid Unicode string
Bug #1918654 reported by
Arkady Shtempler
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
New
|
Undecided
|
Unassigned |
Bug Description
Scenario:
Try to create a new TLD using Unicode string, for example: “例え”
Actual Result:
API fails with:
Details: {'code': 400, 'type': 'invalid_object', 'message': 'Provided object is not valid. Got a ValueError error with message \u4f8b\u3048 is not an TLD', 'request_id': 'req-fa7cb43e-
Expected Result:
Should pass
Notes:
1) There is an tempest patch could be used to reproduce the scenario:
https:/
affects: | neutron → designate |
Changed in designate: | |
status: | Expired → New |
To post a comment you must log in.
You likely need to use the ascii representation for unicode domains, see https:/ /en.wikipedia. org/wiki/ Internationaliz ed_domain_ name , same as you would need to do for creating a zone matching that TLD later.