yahoo-eng-team team mailing list archive

[Anastasia <anastasia.macmood@xxxxxxxxxxxxx>]

@Andres Rodriguez (andreserl),

Thank you for the prompt reply \o/

I have read comment # 3 (or comment # 4) as in 'could be in MAAS' but
'MAAS layer' (quoting the reporter), from Juju perspective, could be
interpreted as a MAAS provider and, indeed, could involve modification
to juju maas provider user data.

I'll leave as 'New' in juju for further consideration but am not
convinced that it needs to be addressed in Juju if everything works as
desired via model-config as per suggestion.

I am fairly certain that there is nothing to do on cloud-init side
either, I was mostly interested in the advice around pre-runcmd/post-
runcmd...

** Changed in: juju
       Status: Invalid => New

-- 
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:
  New
Status in juju:
  New
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