Merge lp:~blake-rouse/maas/fix-1341001 into lp:~maas-committers/maas/trunk
Proposed by
Blake Rouse
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Blake Rouse | ||||
Approved revision: | no longer in the source branch. | ||||
Merged at revision: | 2552 | ||||
Proposed branch: | lp:~blake-rouse/maas/fix-1341001 | ||||
Merge into: | lp:~maas-committers/maas/trunk | ||||
Diff against target: |
185 lines (+76/-23) 4 files modified
src/provisioningserver/import_images/boot_resources.py (+25/-16) src/provisioningserver/import_images/tests/test_boot_resources.py (+2/-0) src/provisioningserver/tests/test_upgrade_cluster.py (+34/-1) src/provisioningserver/upgrade_cluster.py (+15/-6) |
||||
To merge this branch: | bzr merge lp:~blake-rouse/maas/fix-1341001 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gavin Panella (community) | Approve | ||
Review via email: mp+226673@code.launchpad.net |
Commit message
Re-write maas.tgt on cluster upgrade, when moving from 1.5 to 1.6.
To post a comment you must log in.
Looks good, one comment in the diff.
Is there a reason to choose this approach rather than running an import? Would the ideal actually be to run this migration *and then* run an import too?