yahoo-eng-team team mailing list archive

[Chad Smith <1756083@xxxxxxxxxxxxxxxxxx>]

James, sorry I misunderstood because of your description on this bug. I
had miswritten the protocol "cloud-init bug reporting guidelines:"  when
you clicked the original https://bugs.launchpad.net/cloud-init/+filebug.

It should have told you to run "sudo cloud-init collect-logs" instead of
'cloud-init collect'. I fixed that in Launchpad.


cloud-init-output.log will contain your stdout & stderr from scripts run
if the traceback didn't give you enough into in /var/log/cloud-init.log

Looking in the cloud-init-output.log that you attached I see sed related errors reported:
sed: -e expression #1, char 37: unknown option to `s'


One quick way to diagnose and fix custom scripts you deliver is to run them in the deployed instance. they all get written to /var/lib/cloud/instance/scripts/.
You can look at those scripts to make sure they show the content you expected and iteratively run then and sort the errors with your scripts there to figure out what's wrong.


Setting this back in invalid, unless you have updates that you think
indicate a cloud-init bug.

** 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