Use default arch when provisioning a machine #14042
Merged
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.
Found when doing the 2.9.30 release candidate smoke tests - a 2.8 model does not record machine architecture. In 2.9, we default to amd64, and recent changes have added more strict checks around this. Upgrading from a 2.8 controller, if there is a machine that was not yet provisioned at the time of the upgrade, there would be no arch specified when locating agents to use, and so multiple would be found, one for each arch. This is now an error in 2.9.
The fix is to use the default arch when provisioning in case the model doesn't have one.
QA steps
bootstrap a 2.8 model and deploy a charm
immediately upgrade before the machine has been provisioned