yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

** Changed in: nova
     Assignee: Matt Riedemann (mriedem) => Andrey Volkov (avolkov)

** Also affects: nova/ocata
   Importance: Undecided
       Status: New

** Also affects: nova/rocky
   Importance: Undecided
       Status: New

** Also affects: nova/queens
   Importance: Undecided
       Status: New

** Also affects: nova/pike
   Importance: Undecided
       Status: New

** Changed in: nova/ocata
       Status: New => Triaged

** Changed in: nova/pike
       Status: New => Triaged

** Changed in: nova/rocky
   Importance: Undecided => Low

** Changed in: nova/ocata
   Importance: Undecided => Low

** Changed in: nova/queens
   Importance: Undecided => Low

-- 
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/1808286

Title:
  Inconsistent behavior for the marker option for instances and build
  requests

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) ocata series:
  Triaged
Status in OpenStack Compute (nova) pike series:
  Triaged
Status in OpenStack Compute (nova) queens series:
  New
Status in OpenStack Compute (nova) rocky series:
  New

Bug description:
  When --marker is used for instances it skips instance with marker
  http://ix.io/1vU9.

  For build request instances --marker option includes instance with
  marker http://ix.io/1vUa.

  It's hard to catch moment with build request available and I used the
  following sql to emulate build request presence http://ix.io/1vUb

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1808286/+subscriptions