Creating wildcard records fails in v2

Bug #1479459 reported by Paul Glass
6
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/6256bad2-e5b5-4769-bff0-b804ad7055e7/recordsets
{
    "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'",
        "validator": "format",
        "validator_value": "domainname"
      }
    ]
  },
  "request_id": "req-34ec0e18-8fc5-4aa3-9916-8b0c3ccf84f3"
}

Tim Simmons (timsim)
Changed in designate:
status: New → Triaged
importance: Undecided → High
Changed in designate:
milestone: none → liberty-3
importance: High → Medium
Mimi Lee (mimi-lee)
Changed in designate:
assignee: nobody → Mimi Lee (mimi-lee)
Changed in designate:
status: Triaged → In Progress
Revision history for this message
Kiall Mac Innes (kiall) wrote :
Kiall Mac Innes (kiall)
Changed in designate:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in designate:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in designate:
milestone: liberty-3 → 1.0.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.