yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1806504@xxxxxxxxxxxxxxxxxx>]

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => Expired

-- 
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/1806504

Title:
  userdata runcmd overwrites runcmd under cloud.cfg.d

Status in cloud-init:
  Expired
Status in juju:
  Invalid
Status in MAAS:
  Invalid

Bug description:
  I'm using Juju to deploy machine. Added runcmd section in
  /etc/cloud.cfg.d/60-my-conf.cfg:

  ```
  merge_how: 'list(append)+dict(recurse_array)+str()'

  runcmd:
   - echo "run in 60 my cloudinit cfg"
   - usermod -aG docker ubuntu

  merge_how: 'list(append)+dict(recurse_array)+str()'
  ```

  This script works when deploy machine using MAAS. But it didn't work
  when deploy machine using JUJU, Seems merge_how doesn't works.

  I want to use cloud-init single to seem how runcmd executes, but seems
  it's only displaying the last execution's status?

  ```
  cloud-init single --name cc_runcmd --frequency always
  Cloud-init v. 18.4-0ubuntu1~16.04.2 running 'single' at Tue, 04 Dec 2018 00:01:54 +0000. Up 1338.24 seconds
  ```

  Seems I didn't find a good way to debug this problem, appreciate any
  debug commands or tips for debug this kind of problems here.

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