RequestSpec online data migration context does not contain project_id
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Matt Riedemann | ||
Newton |
Fix Released
|
High
|
Matt Riedemann | ||
Ocata |
Fix Released
|
High
|
Matt Riedemann | ||
Pike |
Fix Released
|
High
|
Matt Riedemann |
Bug Description
The online data migration generates a context in order to be able to execute migrations:
https:/
However, this context does not contain a `project_id` when running this via CLI.
https:/
During the creation of RequestSpec's for old instances, the context which contains no `project_id`.
https:/
This means that a RequestSpec gets created with `project_id` set to `null`. During the day-to-day operations, things work okay, however, when attempting to do a live migration, the `project_id` is set to `null` when trying to claim resources which the placement API refuses.
https:/
This will give errors as such:
<html>
<head>
<title>400 Bad Request</title>
</head>
<body>
<h1>400 Bad Request</h1>
The server could not comply with the request since it is either malformed or otherwise incorrect.<br /><br />
JSON does not validate: None is not of type 'string'
Failed validating 'type' in schema[
{'maxLength': 255, 'minLength': 1, 'type': 'string'}
On instance[
None
</body>
</html>
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Matt Riedemann (mriedem) |
summary: |
- Online data migration context does not contain project_id + RequestSpec online data migration context does not contain project_id |
tags: | added: up |
tags: |
added: upgrade removed: up |
Fix proposed to branch: master /review. openstack. org/529184
Review: https:/