id can be set in the post body with v2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Critical
|
Vinod Mangalpally | ||
Icehouse |
Fix Released
|
Critical
|
Vinod Mangalpally |
Bug Description
I used MySQL with BIND for these tests.
For a POST at /v2/zones with a body as below
{
"zone" : {
"id" : "2a1d1d1d-
"pool_id" : "2b1d1d1d-
"project_id" : "my_project_id",
"status" : "ERROR",
"ttl" : 12,
"serial" : 100,
"version" : 5,
"created_at" : "2014-02-
"updated_at" : "2014-02-
"name" : "example2.com.",
"email" : "<email address hidden>"
}
}
the Response is
{
"zone":{
"status"
"description
"links":{
"self":"http://
},
"updated_
"ttl":12,
"serial"
"id"
"name"
"created_
"pool_
"version":1,
"project_
"email":"<email address hidden>"
}
}
The id field is updated. pool_id, project_id, status, version, serial, created_at, updated_at can be specified in the body but are ignored.
Changed in designate: | |
assignee: | nobody → Vinod Mangalpally (vinod-mang) |
summary: |
- id can be set in the post body with both v1 and v2 + id can be set in the post body with v2 |
description: | updated |
Changed in designate: | |
importance: | Undecided → Critical |
Fix proposed to branch: master /review. openstack. org/80076
Review: https:/