yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #75499
[Bug 1796689] Re: Incorrect results for tenant usage
Reviewed: https://review.openstack.org/608685
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=afc3a16ce3364c233e6e1cffc9f38987d1d65318
Submitter: Zuul
Branch: master
commit afc3a16ce3364c233e6e1cffc9f38987d1d65318
Author: Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>
Date: Mon Oct 8 17:13:55 2018 +0300
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.
Change-Id: I6c7a67b23ec49aa207c33c38580acd834bb27e3c
Closes-Bug: #1796689
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1796689
Title:
Incorrect results for tenant usage
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) ocata series:
Triaged
Status in OpenStack Compute (nova) pike series:
Triaged
Status in OpenStack Compute (nova) queens series:
Triaged
Status in OpenStack Compute (nova) rocky series:
Triaged
Bug description:
nova usage-list can return incorrect results, having resources counted
twice. This only occurs when using the 2.40 microversion or later.
http://paste.openstack.org/raw/731560/
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1796689/+subscriptions
References