On the TX2 is the resin-device-register exists with a failure code if the needed variables (API_ENDPOINT or CONFIG_PATH) aren't set. This causes resin-init-flasher to get stopped, although it has a weak dependence (Wants) on resin-devkice-register.
On the NUC the resin-init-flasher service isn't stopped although resin-device-register fails when the required variables aren't set. Both TX2 and the NUC use the same systemd 250.5, but the NUC runs on a newer kernel version 5.15, which is not available on the TX2.
This issue has been observed on the TX2 based type only and has been addressed by setting the api endpoint in the config.json, for the HUP test.
acostach
commented
1 year ago
On the TX2 is the resin-device-register exists with a failure code if the needed variables (API_ENDPOINT or CONFIG_PATH) aren't set. This causes resin-init-flasher to get stopped, although it has a weak dependence (Wants) on resin-devkice-register. On the NUC the resin-init-flasher service isn't stopped although resin-device-register fails when the required variables aren't set. Both TX2 and the NUC use the same systemd 250.5, but the NUC runs on a newer kernel version 5.15, which is not available on the TX2.
This issue has been observed on the TX2 based type only and has been addressed by setting the api endpoint in the config.json, for the HUP test.