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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1712676

Title:
  Cloud-init analyzeand devel  commandline traceback

Status in cloud-init:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1712676/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to