-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request juju#18860 from nvinuesa/implement_app_constraints…
…_migration juju#18860 This patch adds model migration for domain application constraints. Note: The migration import does not use the validation that is used when setting constraints in the app service. The reason is that we don't have a provider for migration yet. The validation will be added in a follow-up patch. ## QA steps 1. Bootstrap a 3.6 controller and deploy a charm. ```sh $ juju bootstrap lxd src36 $ juju add-model moveme1 $ juju deploy juju-qa-test $ juju set-constraints juju-qa-test spaces=^alpha cpu-cores=2 ``` 2. Bootstrap a 4.0 controller with the changes and migrate the model. ```sh $ juju bootstrap lxd dst40 $ juju migrate src36:moveme1 dst40 $ juju add-unit juju-qa-test $ juju constraints juju-qa-test cores=2 spaces=^alpha ``` 3. Verify no errors exist in the model logs for the agents. If there are errors, this is a bug and should be fixed before merging. The fix can either be applied to the 4.0 branch (preferable) or the 3.6 branch, though that needs to be discussed with the team. ```sh $ juju debug-log -m dst40:controller $ juju debug-log -m dst40:moveme1 ``` 4. We also need to test a model migration from 4.0 to 4.0. ```sh $ juju bootstrap lxd src40 $ juju add-model moveme2 $ juju deploy juju-qa-test $ juju set-constraints juju-qa-test spaces=^alpha cpu-cores=2 ``` ```sh $ juju migrate src40:moveme2 dst40 $ juju add-unit juju-qa-test $ juju constraints juju-qa-test cores=2 spaces=^alpha ``` 5. Verify that there are no errors in the controller or model logs. ```sh $ juju debug-log -m dst40:controller $ juju debug-log -m dst40:moveme2 ``` ## Links **Jira card:** JUJU-7420
- Loading branch information
Showing
8 changed files
with
362 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.