Cloud-init analyzeand devel commandline traceback
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Chad Smith |
Bug Description
Calling cloud-init analyze from the command line results in a traceback due to the argument parser not properly setting up subparser default behavior.
$ cloud-init devel
Traceback (most recent call last):
File "/usr/bin/
load_
File "/usr/lib/
(name, functor) = args.action
AttributeError: 'Namespace' object has no attribute 'action'
$ cloud-init analyze
# But direct python module calls work
$ python3 -m cloudinit.cmd.main devel
usage: /usr/lib/
[-h] {blame,show,dump} ...
/usr/lib/
$ python3 -m cloudinit.cmd.main analyze
usage: /usr/lib/
[-h] {blame,show,dump} ...
/usr/lib/
Related branches
- Scott Moser: Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 46 lines (+19/-5)2 files modifiedcloudinit/cmd/main.py (+4/-5)
tests/unittests/test_cli.py (+15/-0)
Changed in cloud-init: | |
assignee: | nobody → Chad Smith (chad.smith) |
Changed in cloud-init: | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New
Thank you.