yahoo-eng-team team mailing list archive

[OpenStack Infra <1732707@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/522407
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5e95c807d1d0ca23c4042d6df54c0cdda72b0caa
Submitter: Zuul
Branch:    master

commit 5e95c807d1d0ca23c4042d6df54c0cdda72b0caa
Author: Tetsuro Nakamura <nakamura.tetsuro@xxxxxxxxxxxxx>
Date:   Thu Nov 23 07:56:12 2017 +0900

    Add aggregates check in allocation candidates
    
    Allocation candidates api returned some wrong
    combinations of non-sharing resource provider and
    shared resource provider, ignoring aggregates.
    
    This patch adds aggregate check when constructing
    shared allocation request being aware of non-sharing
    resource in _shared_allocation_request_resources.
    
    Change-Id: Ib45fde56706a861df0fc048bbec8a568fd26d85d
    Closes-Bug:#1732707


** 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/1732707

Title:
  AllocationCandidates.get_by_filters returns candidates containing non
  connected RPs

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Consider the following setup in placement:

         CN1 (VCPU)          CN2 (VCPU)
        / agg3   \ agg1     / agg1   \ agg2
    SS3 (IPV4)   SS1 (DISK_GB)      SS2 (IPV4)

  Then VCPU, DISK_GB  nd IPV4 resources are requested. However besides
  the expected candidates we get invalid candidates mixing CN1 with SS2
  and CN2 with SS3 which are clearly invalid.

  Here is a functional test reproducing the issue:
  https://review.openstack.org/#/c/519617

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