Comment 11 for bug 1739318

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

Reviewed: https://review.openstack.org/529384
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c86db10feb07d023b651fd9909e1039fe775424d
Submitter: Zuul
Branch: stable/pike

commit c86db10feb07d023b651fd9909e1039fe775424d
Author: Matt Riedemann <email address hidden>
Date: Tue Dec 19 18:31:27 2017 -0500

    Use instance.project_id when creating request specs for old instances

    The online data migration routine to create request specs for old
    instances is using an admin context, which doesn't have a project_id
    set, which means the request spec that gets created doesn't have
    a project_id set, which matters when the FilterScheduler tries to
    claim resources (create allocations in Placement) using said
    request spec's project_id (PUT /allocations requires a non-null
    project_id).

    This fixes the online data migration by creating the request spec
    using the instance's project_id rather than that from the context.

    Change-Id: I214a44f0eee7d90be5cd89f32f6e0017b19a3fd6
    Partial-Bug: #1739318
    (cherry picked from commit a148e638dd5eaaa6f9c8749782a625c6523b6b6a)