Merge ~raharper/cloud-init:bug-lp-1645644-ntp into cloud-init:master
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merged at revision: | e11d3899d47ec5fcb545e0c7820af9d3995cb574 | ||||
| Proposed branch: | ~raharper/cloud-init:bug-lp-1645644-ntp | ||||
| Merge into: | cloud-init:master | ||||
| Diff against target: |
352 lines (+183/-28) 8 files modified
cloudinit/config/cc_ntp.py (+22/-2) tests/cloud_tests/configs/modules/ntp_pools.yaml (+6/-4) tests/cloud_tests/configs/modules/ntp_servers.yaml (+10/-6) tests/cloud_tests/testcases/modules/ntp.py (+2/-2) tests/cloud_tests/testcases/modules/ntp_pools.py (+19/-6) tests/cloud_tests/testcases/modules/ntp_servers.py (+14/-5) tests/unittests/test_handler/test_handler_ntp.py (+76/-2) tox.ini (+34/-1) |
||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Server Team CI bot | continuous-integration | Needs Fixing on 2017-05-12 | |
| Scott Moser | 2017-01-11 | Needs Fixing on 2017-01-12 | |
|
Review via email:
|
|||
Description of the Change
cc_ntp: write template before installing and add service restart
On systems which installed ntp and specified servers or pools in the
config ntpd didn't notice the updated configuration file and didn't
use the correct configuration. Resolve this by rendering the template
first which allows the package install to use the existing
configuration. Additionally add a service restart to handle the case
where ntp does not need to be installed but it may not have started.
Add an integration test to confirm that cc_ntp enables ntp to use the
specific servers and pools in the cloud-config.
LP: #1645644
- 7ca55db... by Ryan Harper on 2017-01-11
- 95f8e85... by Ryan Harper on 2017-01-11
- f5fdb6c... by Ryan Harper on 2017-01-11
- 62e56aa... by Ryan Harper on 2017-01-12
- d801528... by Ryan Harper on 2017-01-12
- 2571946... by Ryan Harper on 2017-01-12
- b97c262... by Ryan Harper on 2017-01-12
- 97b0ad4... by Ryan Harper on 2017-01-12
| Scott Moser (smoser) wrote : | # |
i rebased to master, dropped the tox changes and then submitted a MP back here.
https:/
i think its sane, would appreciate your input.
the tox changes are welcome in a separate commit.
| Ryan Harper (raharper) wrote : | # |
pretty sure the tox changes weren't needed for the fix, but it was useful when exercising this fix under ci. I'll re-run that and propose separately
- 06008d2... by Ryan Harper on 2017-05-12
- 61fa4b0... by Ryan Harper on 2017-05-12
- 039fad4... by Ryan Harper on 2017-05-12
FAILED: Continuous integration, rev:039fad44ce2
https:/
Executed test runs:
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/


FAILED: Continuous integration, rev:97b0ad442bb 251a519a5ed8344 32d1a75c20bb9f /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 73/ /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- arm64/73/ console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- ppc64el/ 73/console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- s390x/73/ console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=vm- amd64/73/ console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=vm- i386/73/ console
https:/
Executed test runs:
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 73/rebuild
https:/