]> git.ipfire.org Git - thirdparty/open-vm-tools.git/commit
Handle the new cloud-init error code and status
authorKruti Pendharkar <kp025370@broadcom.com>
Thu, 22 Jan 2026 04:42:54 +0000 (20:42 -0800)
committerKruti Pendharkar <kp025370@broadcom.com>
Thu, 22 Jan 2026 04:42:54 +0000 (20:42 -0800)
commitef02e35e7db9bd40734dad78063a62a559de0537
treed99a17b925c5d272c48ab65d24018bb559c6b295
parent62944aee48f5c1b74bf3a996a7f1b7f1a3874f9a
Handle the new cloud-init error code and status

- A new error code[1] was introduced in cloud-init v23.4,
  It was reported that the existing code should handle this
  new error code properly.
  This change follows the backwards-compatible approach as described in
  cloud-init documentation[2], by checking that the return code is
  not equal to 1.
- Running status has been changed from "not run" to "not started" in
  cloud-init v24.1 (see [3]).
  This change adds a "not started" match to CLOUDINIT_STATUS_NOT_RUN to
  maintain compatibility.

Addresses Issue: https://github.com/vmware/open-vm-tools/issues/768

[1]: https://cloudinit.readthedocs.io/en/latest/explanation/failure_states.html#error-codes
[2]: https://cloudinit.readthedocs.io/en/latest/explanation/return_codes.html
[3]: https://github.com/canonical/cloud-init/commit/d175170aedc1398b85ac767573b8773a5a2e7c6f
open-vm-tools/libDeployPkg/linuxDeployment.c