Merge ~smoser/cloud-init:bug/1686514-azure-reformat-large into cloud-init:master
| Status: | Merged |
|---|---|
| Merged at revision: | 31b6f173280fcc8e9be2732ae2e9b6f6c89679d4 |
| Proposed branch: | ~smoser/cloud-init:bug/1686514-azure-reformat-large |
| Merge into: | cloud-init:master |
| Diff against target: |
588 lines (+307/-77) 4 files modified
cloudinit/config/cc_disk_setup.py (+14/-5) cloudinit/sources/DataSourceAzure.py (+49/-35) tests/unittests/test_datasource/test_azure.py (+228/-37) tests/unittests/test_handler/test_handler_disk_setup.py (+16/-0) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Scott Moser | Approve on 2017-05-17 | ||
| Server Team CI bot | continuous-integration | Approve on 2017-05-17 | |
| Ryan Harper | 2017-04-29 | Needs Fixing on 2017-05-16 | |
|
Review via email:
|
|||
Commit Message
Azure: fix reformatting of ephemeral disks on resize to large types.
Large instance types have a different disk format on the newly
partitioned ephemeral drive. So we have to adjust the logic in the
Azure datasource to recognize that a disk with 2 partitions and
an empty ntfs filesystem on the second one is acceptable.
This also adjusts the datasources's builtin fs_setup config to remove
the 'replace_fs' entry. This entry was previously ignored, and confusing.
I've clarified the doc on that also.
LP: #1686514
PASSED: Continuous integration, rev:225163c43eb
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
PASSED: Continuous integration, rev:f3efa89cce9
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
PASSED: Continuous integration, rev:d6cfcd4f0ec
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
| Ryan Harper (raharper) wrote : | # |
Please look at the discussion of realpath; I believe the code works as you have it but I'd prefer to be explicit in where we use realpath.
PASSED: Continuous integration, rev:e4d051d05a6
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
PASSED: Continuous integration, rev:b5722bd1358
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
| Scott Moser (smoser) wrote : | # |
Going to merge this based on
05/17/17 10:09:05 <smoser> rharper, thanks. can you read my comments on my azure branch ? want to get that landed today.
05/17/17 10:09:12 <smoser> if you have somethign you want me to review, please po int.
05/17/17 10:09:58 <rharper> smoser: ack; I read them; I still don't like the side-effects but I won't object any more;


PASSED: Continuous integration, rev:66073f870cc 2a7a3794c59293c a9bf715dddf1f6 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 325/ /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- amd64/325 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- arm64/325 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- ppc64el/ 325 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=vm- i386/325
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 325/rebuild
https:/