errors while running runcmd lines should fail the first boot

[Thomas JOUANNOT]

given a list of commands specified in a "runcmd" list, if a command fails i think it should prevent the next commands from running and mark the execution as failed
also, the power_state should be ignored.

[Scott Moser (smoser)]

> given a list of commands specified in a "runcmd" list, if a command fails
> i think it should prevent the next commands from running and mark the
> execution as failed

I generally agree that that is how it *should* have been done.
At this point though we'd have to extend... so that backwards compatibility
is maintained.

> also, the power_state should be ignored.

For this I'm not so sure. power_state does have a 'condition' which
allows you to implement the logic yourself.

https://cloudinit.readthedocs.io/en/latest/topics/modules.html#power-state-change

[Thomas JOUANNOT (mazerty)]

that's really a shame :(
isn't there a way to optionally have this behavior ? like with a boolean which would default to false for backward compatibility, but set to true, would behave like described above ?

[Ryan Harper (raharper)]

Hi,

Thanks for filing the issue. It would be possible to introduce new cloud-config for run_cmd, something like:

#cloud-config
runcmd_chain_commands: true # we can bikeshed this
runcmd:
   - /bin/false
   - echo "Hi, this shouldn't execute"

Alternatively, you can use write_files to render a shell command which runs with set -e; and then runcmd to execute it.

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3277