New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a strict-migration feature flag #7176
Conversation
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
Build failed: Tests failed |
Scary but true... I suspect that it is actually a failure related to the patch: migration_internal_test.go:335: OOPS: 1845 passed, 1 skipped, 1 FAILED |
d26d09a
to
13618e2
Compare
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
Build failed: Tests failed |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
Description of change
This branch adds a strict validation check to migrations it ensure that all status, status history, annotations, and settings are exported.
During this change, it was identified that the unit workload version was not using the status documents already retrieved, and also that the cloud instance status was being migrated from the wrong place. The Status field in the instanceDoc was depricated, but not removed, nor even mentioned that it was deprecated. This branch removes it from the instanceDoc, and updates the migration code to migrate the status and status history for the instance status.
Documentation changes
None.