[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/1833442
Title:
runcmd commands are not parsed / executed
Status in cloud-init:
Expired
Bug description:
Images used from centos.cloud
OS version:
CentOS 7.2 and 7.5
Cloud-init versions tried with:
cloud-init-0.7.9-24.el7.centos.x86_64
cloud-init-18.2-1.el7.centos.2.x86_64
Issue:
- adding 90_custom-runcmd.cfg with following content to
/etc/cloud/cloud.cfg.d/:
runcmd:
- [ ip, "-6", route, add, default, via, "xxxx:yyyy:zzzz::w", dev, eth0 ]
- [ touch, /tmp/file.txt ]
File is not parsed, command not executed.
Cloud init complains about bad datasource and
/var/lib/cloud/instance/scripts/runcmd is not updated.
datasource is:
datasource_list: ["NoCloud", "ConfigDrive"]
We are using cloud-init for initialization of VMs in oVirt.
Please assist, I will provide any additional log files if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1833442/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
