GET /os-migrations sample has incorrect sort order
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Takashi Natsume |
Bug Description
The API reference sample for the GET /os-migrations API with the 2.59 microversion:
https:/
Shows an incorrect sort order. The returned migrations are sorted by [created_at, id] in descending order:
The response sample shows several random migration records and they aren't sorted by created_at in descending order, because the sample is based on stubs in the functional test:
Since the API reference does not mention what the sort order is, a user might have to guess from the sample, which would be pretty much impossible with the existing sample.
With this bug, the API reference sample should:
1. Fix the sample response data to use proper sort order from the API for the 2.59 samples (since there is no guaranteed sort order for microversion < 2.59, especially with multiple cells).
2. Mention the sort order in the API reference when using microversion 2.59+.
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in nova: | |
assignee: | nobody → Takashi NATSUME (natsume-takashi) |
status: | Triaged → In Progress |
Changed in nova: | |
assignee: | Takashi NATSUME (natsume-takashi) → Ken'ichi Ohmichi (oomichi) |
Changed in nova: | |
assignee: | Ken'ichi Ohmichi (oomichi) → Takashi NATSUME (natsume-takashi) |
The v2.59 example has already sorted by created_at in descending order.
So add a description about the sort order in the API reference when using microversion 2.59+.