Merge ~chad.smith/cloud-init:fix-modules-cmdline-help into cloud-init:master
| Status: | Merged |
|---|---|
| Approved by: | Chad Smith on 2017-12-15 |
| Approved revision: | 3cf942c94deba0554d0829e13c14d14c9d596be6 |
| Merge reported by: | Chad Smith |
| Merged at revision: | 4089e20c0a20bc2ad5c21b106687c4f3faf84b4b |
| Proposed branch: | ~chad.smith/cloud-init:fix-modules-cmdline-help |
| Merge into: | cloud-init:master |
| Diff against target: |
144 lines (+87/-6) 2 files modified
cloudinit/cmd/main.py (+12/-6) tests/unittests/test_cli.py (+75/-0) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Server Team CI bot | continuous-integration | Approve on 2017-12-15 | |
| Chad Smith | Abstain on 2017-12-14 | ||
| Scott Moser | Approve on 2017-12-14 | ||
|
Review via email:
|
|||
Commit Message
cli: Fix error in cloud-init modules --mode=init.
The cli help docs and argument parser allow the 'init' mode value
which caused a traceback.
Fix the cli to support 'init', 'config' and 'final' modes for the
cloud-init modules subcommand.
Add a check in the cli to raise a ValueError if a new
subcommand ends up allowing an unsupported/
Drive by unit test additions for a bit better coverage of error
handling.
LP: #1736600
Description of the Change
cli: Allow providing 'init' mode to cloud-init modules --mode.
The cli help docs and argument parser allow the 'init' mode value
which caused a traceback.
Fix the cli to support 'init', 'config' and 'final' modes for the cloud-init modules subcommand.
Add a check in the cli to raise a ValueError if a new
subcommand ends up allowing an unsupported/
Drive by unit test additions for a bit better coverage of error
handling.
LP: #1736600
| Chad Smith (chad.smith) wrote : | # |
Thanks your your merge proposal.
Your branch /fix-modules-
guidelines before it can be reviewed and landed.
1. All lines must be less than 74 characters.
2. The commit message should adhere to git commit message format conventions:
<Your one-liner subject line>
<empty line>
<more detailed description about the functional changes of your branch>
<optional empty line>
<optional bug link of the format 'LP: #<bug-id>'>
The following issues were found:
The merge proposal /fix-modules-
Please update your commit message for this branch on launchpad and set the branch back to 'Needs review'.
Thanks again,
Your friendly neighborhood cloud-init robot.
| Chad Smith (chad.smith) wrote : | # |
Thanks your your merge proposal.
Your branch /fix-modules-
guidelines before it can be reviewed and landed.
1. All lines must be less than 74 characters.
2. The commit message should adhere to git commit message format:
A one-liner subject line
More detailed paragraphs describing the functional changes of the
branch.
LP: #<bug-id> # if it fixes a specific bug
We discovered the following issues:
-------
The merge proposal /fix-modules-
-------
Please set the branch back to 'Needs Review' after resolving these issues with
your commit message.
Thanks again,
Your friendly neighborhood cloud-init robot.
| Chad Smith (chad.smith) wrote : | # |
Thanks your your merge proposal.
Your branch /fix-modules-
guidelines before it can be reviewed and landed.
1. All lines must be less than 74 characters.
2. The commit message should adhere to git commit message format:
A one-liner subject line
More detailed paragraphs describing the functional changes of the
branch.
LP: #<bug-id> # if it fixes a specific bug
We discovered the following issues:
-------
Commit message lints:
- Commit message line #4 has 71 too many characters.Line begins with: "which caused a traceback"...
-------
Please set the branch back to 'Needs Review' after resolving these issues with
your commit message.
Thanks again,
Your friendly neighborhood cloud-init robot.
| Scott Moser (smoser) wrote : | # |
love the bot voting.
running the 'init' modules does make sense.
there are 3 sets of modules:
init, config, final
the 'init' modules just tag along with either init-local or init-net.
This restores functionality to
cloud-init modules -m init
FAILED: Continuous integration, rev:0e809cb8194
https:/
Executed test runs:
SUCCESS: Checkout
FAILED: Unit & Style Tests
Click here to trigger a rebuild:
https:/
PASSED: Continuous integration, rev:7fb36cd65d7
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 : | # |
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.
Your branch /fix-modules-
commit message guidelines before it can be reviewed and landed.
1. All lines must be less than 74 characters.
2. The commit message listed in launchpad needs to have the format:
A one-liner subject line
More detailed paragraphs describing the functional changes of the
branch.
LP: #<bug-id> # if it fixes a specific bug
Please fix the following errors:
-------
Commit message lints:
- Commit message line #6 has 22 too many characters.Line begins with: "Fix the cli to support"...
-------
PASSED: Continuous integration, rev:3cf942c94de
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:/


PASSED: Continuous integration, rev:171e54e007a 6a5357b194fb580 5451a7bc670682 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 621/
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/ 621/rebuild
https:/