Merge ~smoser/cloud-init:bug/1724354-debug-only-on-missing-json-schema into cloud-init:master
| Status: | Merged |
|---|---|
| Approved by: | Chad Smith on 2017-10-18 |
| Approved revision: | 24afb7d32ba3deb4097f8812122b5a7bf6279806 |
| Merged at revision: | 41152f10ddbd8681cdac44b408038a4f23ab02df |
| Proposed branch: | ~smoser/cloud-init:bug/1724354-debug-only-on-missing-json-schema |
| Merge into: | cloud-init:master |
| Diff against target: |
150 lines (+32/-9) 8 files modified
cloudinit/config/cc_users_groups.py (+2/-1) cloudinit/config/schema.py (+1/-1) doc/examples/cloud-config-user-groups.txt (+3/-3) tests/cloud_tests/testcases/base.py (+4/-0) tests/cloud_tests/testcases/examples/including_user_groups.py (+6/-0) tests/cloud_tests/testcases/examples/including_user_groups.yaml (+5/-2) tests/cloud_tests/testcases/modules/user_groups.py (+6/-0) tests/cloud_tests/testcases/modules/user_groups.yaml (+5/-2) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Chad Smith | 2017-10-17 | Approve on 2017-10-18 | |
| Server Team CI bot | continuous-integration | Approve on 2017-10-18 | |
|
Review via email:
|
|||
Commit Message
schema: Log debug instead of warning when jsonschema is not available.
When operating in expected path, cloud-init should avoid logging with
warning. That causes 'WARNING' messages in /var/log/
By default, warnings also go to the console.
Since jsonschema is a optional dependency, and not present on xenial
and zesty, cloud-init should not warn there.
Also here:
* Add a test to integration tests to assert that there are no
warnings in /var/log/
* Update one integration test that did show warning and the related
documentation and examples.
LP: #1724354
FAILED: Continuous integration, rev:1dc8e693e88
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
FAILED: Ubuntu LTS: Integration
Click here to trigger a rebuild:
https:/
FAILED: Continuous integration, rev:5a46b85c35e
https:/
Executed test runs:
SUCCESS: Checkout
FAILED: Unit & Style Tests
Click here to trigger a rebuild:
https:/
FAILED: Continuous integration, rev:bc70e1578b9
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
FAILED: Ubuntu LTS: Integration
Click here to trigger a rebuild:
https:/
FAILED: Continuous integration, rev:9a07f80e8e6
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
FAILED: MAAS Compatability Testing
Click here to trigger a rebuild:
https:/
FAILED: Continuous integration, rev:24afb7d32ba
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
FAILED: MAAS Compatability Testing
Click here to trigger a rebuild:
https:/
PASSED: Continuous integration, rev:
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:/
| Chad Smith (chad.smith) wrote : | # |
Ran tox locally and all good here. Looks like remote service timeouts for centos/yum etc as the failing points on CI tests. unrelated to this changeset.
py27: commands succeeded
py3: commands succeeded
flake8: commands succeeded
xenial: commands succeeded
pylint: commands succeeded
congratulations :)


PASSED: Continuous integration, rev:526ae49fa43 ba0528ce4ffc30c fa56a1fe433221 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 402/
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: /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 402/rebuild
https:/