Trusts expires_at field is rounded down, doesn't match docs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
The API docs[1] state:
"expires_at (string, ISO 8601 extended format date time with microseconds)"
and in the examples:
"expires_at": "2013-02-
However this doesn't match the actual behaviour of the API, which rounds down the microseconds component. Rounding down seems perfectly reasonable, but we should probably modify the docs to match, if this is correct behaviour:
Creating a trust with this post body:
{
"trust": {
"roles": [
{
}
],
}
}
Results in a trust which looks like this:
{
"trust": {
"id": "f2588d87f82d4e
"links": {
"self": "http://
},
"roles": [
{
},
}
],
"next": null,
"self": "http://
},
}
}
Changed in keystone: | |
importance: | Undecided → Medium |
Changed in keystone: | |
assignee: | nobody → Juan Manuel Ollé (juan-m-olle) |
Changed in keystone: | |
status: | New → Confirmed |
Actually, it seems the response from the POST to create the trust is not rounded, but subsequent GET's to retrieve the trust are.