Cloud-init analyzeand devel commandline traceback

Bug #1712676 reported by Chad Smith on 2017-08-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
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/cloud-init", line 9, in <module>
    load_entry_point('cloud-init==0.7.9', 'console_scripts', 'cloud-init')()
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 784, in main
    (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/python3/dist-packages/cloudinit/cmd/main.py analyze
       [-h] {blame,show,dump} ...
/usr/lib/python3/dist-packages/cloudinit/cmd/main.py analyze: error: the following arguments are required: subcommand

$ python3 -m cloudinit.cmd.main analyze
usage: /usr/lib/python3/dist-packages/cloudinit/cmd/main.py analyze
       [-h] {blame,show,dump} ...
/usr/lib/python3/dist-packages/cloudinit/cmd/main.py analyze: error: the following arguments are required: subcommand

Related branches

Chad Smith (chad.smith) on 2017-08-23
Changed in cloud-init:
assignee: nobody → Chad Smith (chad.smith)
Scott Moser (smoser) on 2017-08-25
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.

Changed in cloud-init:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers