Merge ~rjschwei/cloud-init:emptyStageOK into cloud-init:master
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Chad Smith | ||||
Approved revision: | 636a27373ef9d7b389a6a273930ab3e0ea73acdc | ||||
Merge reported by: | Chad Smith | ||||
Merged at revision: | fef2616b9876d3d354b0de1a8e753361e52e77b0 | ||||
Proposed branch: | ~rjschwei/cloud-init:emptyStageOK | ||||
Merge into: | cloud-init:master | ||||
Diff against target: |
69 lines (+33/-3) 2 files modified
cloudinit/stages.py (+3/-1) tests/unittests/test_runs/test_simple_run.py (+30/-2) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Chad Smith | Approve | ||
Server Team CI bot | continuous-integration | Approve | |
Review via email: mp+345377@code.launchpad.net |
Commit message
stages: fix tracebacks if a module stage is undefined or empty
In /etc/cloud/
during a specific cloud-init stage by modifying one of the following
lists: cloud_init_modules, cloud_init_modules, cloud_init_
If any of the configured module lists are absent or empty, cloud-init will
emit the same message it already does for existing lists that only contain
modules which are not unsupported on that platform:
No 'config' modules to run under section 'cloud_
LP: #1770462
Description of the change
The user may create a config file that has an empty stage such as
cloud_init_modules:
cloud_config_
- mounts
if a stage is empty a traceback is generated. With this change an informational message logged and continues processing
I looked around the testing code but couldn't figure out where and how I would test this, thus this does not include any testing.