yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

The alternative hosts calculation code in the scheduler (since Queens)
uses max_attempts incorrectly, as if it's max_retries, but max_attempts
can be set to 1 meaning no retries, but the scheduler would still
calculate that as 1 retry so 1 alternate host.

This is fixed in Rocky with change:
https://review.openstack.org/#/c/569127/

But this bug report is for fixing it in Queens also.

** Affects: nova
     Importance: Medium
     Assignee: Dan Smith (danms)
         Status: Fix Released

** Affects: nova/queens
     Importance: Medium
     Assignee: Dan Smith (danms)
         Status: In Progress


** Tags: scheduler

** Changed in: nova
     Assignee: (unassigned) => Dan Smith (danms)

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

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

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

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

Title:
  nova-scheduler calculates alternative hosts incorrectly

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) queens series:
  In Progress

Bug description:
  The alternative hosts calculation code in the scheduler (since Queens)
  uses max_attempts incorrectly, as if it's max_retries, but
  max_attempts can be set to 1 meaning no retries, but the scheduler
  would still calculate that as 1 retry so 1 alternate host.

  This is fixed in Rocky with change:
  https://review.openstack.org/#/c/569127/

  But this bug report is for fixing it in Queens also.

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