Lucian Petrut f8a721ae85 Fix os-simple-tenant-usage result order ... nova usage-list can return incorrect results, having resources counted twice. This only occurs when using the 2.40 microversion or later. This microversion introduced pagination, which doesn't work properly. Nova API will sort the instances using the tenant id and instance uuid, but 'os-simple-tenant-usage' will not preserve the order when returning the results. For this reason, subsequent API calls made by the client will use the wrong marker (which is supposed to be the last instance id), ending up counting the same instances twice. NOTE(melwitt): The differences from the Queens change in the sample .tpl and .json files are because change I3b25debb0bcfd4e211734307c8d363f2b5dbc655 is not in Pike, so there are only two generated UUIDs per server (instance UUID and vif UUID) instead of three (instance UUID, vif UUID, and bdm UUID). Change-Id: I6c7a67b23ec49aa207c33c38580acd834bb27e3c Closes-Bug: #1796689 (cherry picked from commit afc3a16ce3) (cherry picked from commit 133b194ba0) (cherry picked from commit 70b4cdce68)		2020-08-03 13:43:55 +02:00
..
notes	Fix os-simple-tenant-usage result order	2020-08-03 13:43:55 +02:00
source	doc: Switch to openstackdocstheme	2017-07-21 11:35:48 +01:00