Typically, "user data" containing start-up parameters can be passed to an image. For XLT images, the user data format is JSON. See below for a user data example:
{"acPassword":"abc","hostData":"1.1.1.1 foo\n2.2.2.2 bar"}
The password is then set in the XLT configuration and the host data is appended to /etc/hosts. However, if hostData is empty, the hosts file gets corrupted and looks like this:
# User data entries START
{"acPassword":"abc","hostData":""}
# User data entries END
Note that this happened with an AWS image, but it is likely that all other images are affected similarly.
Typically, "user data" containing start-up parameters can be passed to an image. For XLT images, the user data format is JSON. See below for a user data example:
The password is then set in the XLT configuration and the host data is appended to
/etc/hosts. However, ifhostDatais empty, the hosts file gets corrupted and looks like this:Note that this happened with an AWS image, but it is likely that all other images are affected similarly.