incusd/instance/common: Fix CanMigrate mutating devices #649
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.
This was leading to very odd validation errors in some cases if the instance being considered as part of a cluster restore happened to have a network device that would get an otherwise restricted key be internally set.
The root of the issue was that CanMigrate didn't operate against a copy of the devices but would instead mutate the whole devices config, which would then trigger the validation error when sent through the devices logic for the second time as part of startup.
This issue would only hit if:
Sponsored-by: Buddy (https://buddy.works)