commit f9a06c42535ef7ebba92c793afd947073352f850
Author: Matt Riedemann <email address hidden>
Date: Tue Dec 19 18:40:31 2017 -0500
Workaround missing RequestSpec.project_id when moving an instance
The online data migration routine to create request specs for old
instances used an admin context which has an empty project_id,
so when scheduling (moving) one of these, if we try to PUT /allocations
in placement using the FilterScheduler we'll fail because the project_id
is None.
This works around that by putting the instance.project_id on the request
spec before calling the scheduler to pick a node and claim resources
against it.
A later change will need to add some sort of online data migration
routine so that we properly update and persist the fix for these
older records.
Reviewed: https:/ /review. openstack. org/529185 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=f9a06c42535 ef7ebba92c793af d947073352f850
Committed: https:/
Submitter: Zuul
Branch: master
commit f9a06c42535ef7e bba92c793afd947 073352f850
Author: Matt Riedemann <email address hidden>
Date: Tue Dec 19 18:40:31 2017 -0500
Workaround missing RequestSpec. project_ id when moving an instance
The online data migration routine to create request specs for old
instances used an admin context which has an empty project_id,
so when scheduling (moving) one of these, if we try to PUT /allocations
in placement using the FilterScheduler we'll fail because the project_id
is None.
This works around that by putting the instance.project_id on the request
spec before calling the scheduler to pick a node and claim resources
against it.
A later change will need to add some sort of online data migration
routine so that we properly update and persist the fix for these
older records.
Change-Id: I34b1d99a9d0d2a ca80f094a79ec16 56abaf762dc
Partial-Bug: #1739318