Comment 9 for bug 1606496

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/mitaka)

Reviewed: https://review.openstack.org/367403
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=13513e6232366a82a8a81c01f9ec8210f6da3a30
Submitter: Jenkins
Branch: stable/mitaka

commit 13513e6232366a82a8a81c01f9ec8210f6da3a30
Author: Roman Podoliaka <email address hidden>
Date: Wed Jul 27 19:46:16 2016 +0300

    ironic_host_manager: fix population of instances info on start

    IronicHostManager currently overrides the _init_instance_info()
    method of the base class and unconditionally skips population of
    instances information for all compute nodes, even if they are not
    Ironic ones.

    If there are compute nodes with the hypervisor_type different from
    Ironic in the same cloud. the instances info will be missing in
    nova-scheduler (if IronicHostManager is configured as a host manager
    impl in nova.conf), which will effectively break instance affinity
    filters like DifferentHostFilter or SameHostFilter, that check set
    intersections of instances running on a particular host and the ones
    passed as a hint for nova-scheduler in a boot request.

    IronicHostManager should use the method implementation of the base
    class for non-ironic compute nodes.

    Ib1ddb44d71f7b085512c1f3fc0544f7b00c754fe fixed the problem with
    scheduling, this change is needed to make sure we also populate the
    instances info on start of nova-scheduler.

    Closes-Bug: #1606496

    Co-Authored-By: Timofei Durakov <email address hidden>

    (cherry-picked from cc64a45d98d7576a78a853cc3da8109c31f4b75d)
    Change-Id: I9d8d2dc99773df4097c178d924d182a0d1971bcc