Creating wildcard records fails in v2
Bug #1479459 reported by
Paul Glass
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Medium
|
Mimi Lee |
Bug Description
Try posting any recordset with a wildcard name like *.example.com. like in the following, and Designate will return a 400:
POST /v2/zones/
{
"type": "A",
"name": "*.wumbo.com.",
"records": ["21.21.22.23"],
"ttl": null
}
Response:
{
"code": 400,
"type": "invalid_object",
"errors": {
"errors": [
{
"path": [
"name"
],
"message": "u'*.wumbo.com.' is not a 'domainname'",
}
]
},
"request_id": "req-34ec0e18-
}
Changed in designate: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in designate: | |
milestone: | none → liberty-3 |
importance: | High → Medium |
Changed in designate: | |
assignee: | nobody → Mimi Lee (mimi-lee) |
Changed in designate: | |
status: | Triaged → In Progress |
Changed in designate: | |
status: | In Progress → Fix Committed |
Changed in designate: | |
status: | Fix Committed → Fix Released |
Changed in designate: | |
milestone: | liberty-3 → 1.0.0 |
To post a comment you must log in.
https:/ /review. openstack. org/#/c/ 207232/