TRITON-2435 Preserve internal_metadata_namespaces property when migrating VMs. #93
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a VM is using
internal_metadata_namespaces
, and is then migrated, theinternal_metadata_namespaces
field is lost. Hilarity ensues.Example VM before transfer:
Example VM metadata in VMAPI before transfer:
Performing the transfer:
Example VM after transfer:
Example VM metadata in VMAPI after transfer:
After this patch, the sdc-migration (in this case back to e4-43-4b-86-72-c8) preserves
internal_metadata_namespaces
: