You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Launchpad user Ryan Harper(raharper) wrote on 2019-11-20T21:58:36.505217+00:00
Thanks for filing the bug.
As it turns out, this results in a null entry in the list, which cloud-init fails to "shellify" when rendering this list of commands to a shell script. This results in not writing any of the commands which is why you don't see an failure in the module status.
That's clearly a bug; so we'll need to make a change so that
we handle null or other entries where shellify fails as errors and log them.
Launchpad user James Falcon(falcojr) wrote on 2021-11-02T19:54:15.122296+00:00
This bug is believed to be fixed in cloud-init in version 21.4. If this is still a problem for you, please make a comment and set the state back to New
This bug was originally filed in Launchpad as LP: #1853146
Launchpad details
Launchpad user manuel(boillodmanuel) wrote on 2019-11-19T12:42:40.250969+00:00
Info :
/usr/bin/cloud-init 19.2-36-g059d049c-0ubuntu2~16.04.1
Issue:
If user-data script contains a malformed runcmd script, cloud-init fails to parse it but do not mark cloud-init as failed.
Example:
The second line is empty, and causes the following warning in
/var/log/cloud-init.log
:There is no error log in
/var/log/cloud-init-output.log
But cloud-init status is "done"
I expect the status to be "error"
The text was updated successfully, but these errors were encountered: