yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #71882
[Bug 1756083] Re: clout init error when running native scripts at start up
Your scripts look like they are calling 'cloud-init collect' and not
'cloud-init collect-logs'
collect is not a valid command
/usr/bin/cloud-init: error: argument subcommand: invalid choice: 'collect' (choose from 'init', 'modules', 'single', 'dhclient-hook', 'features', 'analyze', 'devel', 'collect-logs', 'clean', 'status')
** Changed in: cloud-init
Status: New => Invalid
--
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/1756083
Title:
clout init error when running native scripts at start up
Status in cloud-init:
Invalid
Bug description:
AWS AMI ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-*
ubuntu@ip-10-90-130-11:~$ cloud-init collect
usage: /usr/bin/cloud-init [-h] [--version] [--file FILES] [--debug] [--force]
{init,modules,single,dhclient-hook,features,analyze,devel,collect-logs,clean,status}
...
/usr/bin/cloud-init: error: argument subcommand: invalid choice: 'collect' (choose from 'init', 'modules', 'single', 'dhclient-hook', 'features', 'analyze', 'devel', 'collect-logs', 'clean', 'status')
When cloud init runs and hits my native scripts it err and there is no
Reason, Stdout or Stderr.
These scripts are preforming some string replaces for config files
using 'sed'/
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1756083/+subscriptions
References