Merge ~chad.smith/cloud-init:azure-no-ifupdown into cloud-init:master
| Status: | Merged |
|---|---|
| Approved by: | Scott Moser on 2017-12-21 |
| Approved revision: | 6d567fe2e563f27412b4c6527eb12f57c81aeeea |
| Merged at revision: | b05b9972d20ec3ea699d1691b67314d04e852d2f |
| Proposed branch: | ~chad.smith/cloud-init:azure-no-ifupdown |
| Merge into: | cloud-init:master |
| Diff against target: |
134 lines (+40/-13) 2 files modified
cloudinit/sources/DataSourceAzure.py (+16/-9) tests/unittests/test_datasource/test_azure.py (+24/-4) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Scott Moser | 2017-12-20 | Needs Fixing on 2017-12-21 | |
| Server Team CI bot | continuous-integration | Approve on 2017-12-20 | |
|
Review via email:
|
|||
Commit Message
azure: Only bounce network when necessary.
This fixes a traceback when attempting to bounce the network after
hostname resets.
In artful and bionic ifupdown package is no longer installed in default
cloud images. As such, Azure can't use those tools to bounce the network
informing DDNS about hostname changes. This doesn't affect DDNS updates
though because systemd-networkd is now watching hostname deltas and with
default behavior to SendHostname=True over dhcp for all hostname updates
which publishes DDNS for us.
LP: #1722668
Description of the Change
azure: Don't bounce network with ifdown ifup when those tools don't exist
This fixes a traceback when attempting to bounce the network after
hostname resets.
In artful and bionic ifupdown package is no longer installed in default
cloudimages. As such, Azure can't use those tools to bounce the network
informing DDNS about hostname changes. This doesn't affect DDNS updates
though because systemd-networkd is now watching hostname deltas and with
default behavior to SendHostname=True over dhcp for all hostname updates
which publishes DDNS for us.
LP: #1722668
| Chad Smith (chad.smith) wrote : | # |
FAILED: Continuous integration, rev:74f546422a0
https:/
Executed test runs:
SUCCESS: Checkout
FAILED: Unit & Style Tests
Click here to trigger a rebuild:
https:/
- c092c12... by Chad Smith on 2017-12-20
FAILED: Continuous integration, rev:c092c12f606
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
FAILED: Ubuntu LTS: Build
Click here to trigger a rebuild:
https:/
- fdf3923... by Chad Smith on 2017-12-20
- 74fb5bb... by Chad Smith on 2017-12-20
FAILED: Continuous integration, rev:74fb5bb7fdd
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
FAILED: Ubuntu LTS: Build
Click here to trigger a rebuild:
https:/
- 6d567fe... by Chad Smith on 2017-12-20
PASSED: Continuous integration, rev:6d567fe2e56
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
SUCCESS: MAAS Compatability Testing
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild:
https:/
| Scott Moser (smoser) wrote : | # |
Thank you for your merge proposal.
Your branch has been set to 'Work in progress'.
Please set the branch back to 'Needs Review' after resolving the issues below.
Thanks again,
Your friendly neighborhood cloud-init robot.
Please fix the following issues:
-------
Commit message lints:
- Expected empty line on line 2 of the commit message
-------
For more information, see commit message guidelines at
https:/


One inline comment about a potential alternative that may be more palatable/specific.