yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #64394
[Bug 1689692] Re: MarkerNotFound when limit>num(instances) and marker starts in cell0
Reviewed: https://review.openstack.org/468559
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dbaf80d2c94db074a6651c890d532a11baec8da0
Submitter: Jenkins
Branch: master
commit dbaf80d2c94db074a6651c890d532a11baec8da0
Author: Matt Riedemann <mriedem.os@xxxxxxxxx>
Date: Fri May 26 17:48:10 2017 -0400
Fix MarkerNotFound when paging and marker was found in cell0
If we're paging over cells and the marker was found in cell0,
we need to null it out so we don't attempt to lookup by marker
from any other cells if there is more room in the limit.
Change-Id: I8a957bebfcecd6ac712103c346e028d80f1ecd7c
Closes-Bug: #1689692
** 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/1689692
Title:
MarkerNotFound when limit>num(instances) and marker starts in cell0
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) newton series:
New
Status in OpenStack Compute (nova) ocata series:
In Progress
Bug description:
In my Ocata/RDO enviroment, nova version is 15.0.3, if I list
instances with a marker&limit, sometimes it says "maker not found".
More details of my operation steps:
First, all instances are listed here without limit&marker:
[root@host015 astute(keystone_admin)]# nova list --sort created_at:desc
+--------------------------------------+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------+--------+------------+-------------+----------+
| 0e02233c-6c73-4bbe-bede-299ba41f44c3 | 11 | ERROR | - | NOSTATE | |
| f6347ddb-e870-447f-8f14-3e3b57a610f2 | 11 | ERROR | - | NOSTATE | |
| 5de9524f-1167-4ccb-b13c-13acf5435ead | 11 | ERROR | - | NOSTATE | |
| 0548ebed-f0e4-4233-acf3-0339c4802f0d | 11 | ERROR | - | NOSTATE | |
| 2c9ee616-eab9-4a4a-af3c-79f858c571d5 | 11 | ERROR | - | NOSTATE | |
| 9aab5d6a-f5bd-459b-bb25-c04bc56efcf0 | 11 | ERROR | - | NOSTATE | |
| f9ca1f1c-01f3-41a5-a68b-63f01fd87081 | 11 | ERROR | - | NOSTATE | |
| dbb3955a-c768-4883-aae4-f3143f7b3a51 | 11 | ERROR | - | NOSTATE | |
| a587dc5c-54c8-432b-9e38-174aae5e848c | 11 | ERROR | - | NOSTATE | |
| 609ba5ca-bc49-4de5-be7a-16aab8fcb6d2 | 11 | ERROR | - | NOSTATE | |
| b42e32e5-2aaa-46ee-b0bf-b08f29867af1 | 11 | ERROR | - | NOSTATE | |
+--------------------------------------+------+--------+------------+-------------+----------+
Then, I try to list with the first instance id as marker, limited to 3, it's OK:
[root@host015 astute(keystone_admin)]# nova list --sort created_at:desc --limit 3 --marker 0e02233c-6c73-4bbe-bede-299ba41f44c3
+--------------------------------------+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------+--------+------------+-------------+----------+
| f6347ddb-e870-447f-8f14-3e3b57a610f2 | 11 | ERROR | - | NOSTATE | |
| 5de9524f-1167-4ccb-b13c-13acf5435ead | 11 | ERROR | - | NOSTATE | |
| 0548ebed-f0e4-4233-acf3-0339c4802f0d | 11 | ERROR | - | NOSTATE | |
+--------------------------------------+------+--------+------------+-------------+----------+
Then, I try to list with another instance, limited to 3, it's error:
[root@host015 astute(keystone_admin)]# nova list --sort created_at:desc --limit 3 --marker a587dc5c-54c8-432b-9e38-174aae5e848c
ERROR (BadRequest): marker [a587dc5c-54c8-432b-9e38-174aae5e848c] not found (HTTP 400) (Request-ID: req-308371f4-2962-4f3f-8d4c-69bf8c19664f)
That's because no enough instance of limitation after the marker?
When I set limitation to 2, it's OK:
[root@host015 astute(keystone_admin)]# nova list --sort created_at:desc --limit 2 --marker a587dc5c-54c8-432b-9e38-174aae5e848c
+--------------------------------------+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------+--------+------------+-------------+----------+
| 609ba5ca-bc49-4de5-be7a-16aab8fcb6d2 | 11 | ERROR | - | NOSTATE | |
| b42e32e5-2aaa-46ee-b0bf-b08f29867af1 | 11 | ERROR | - | NOSTATE | |
+--------------------------------------+------+--------+------------+-------------+----------+
My question: Why does not limitation work when no enough instance ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1689692/+subscriptions
References