Hi,
We are using mender for OTA update.
From today, our device kitting process is hanged up at installing mender. Our process is to run `get-mender.sh --force-mender-client4` for installation.
Yesterday, I got a successful kitting at version 5.0.3-1+ubuntu+jammy. But now the installer might try to install 5.1.0-1+ubuntu+jammy and try to configure at installation timing and waiting interactive response from user.
root 18563 0.0 0.0 10176 3448 pts/2 S+ 19:15 0:00 /bin/bash ./get-mender.sh --force-mender-client4
root 20174 0.4 0.1 111912 97368 pts/2 S+ 19:15 0:02 apt-get install -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold mender-client4 mender-configure mender-connect
root 20303 0.0 0.0 9780 3112 pts/3 S+ 19:15 0:00 /bin/bash /var/lib/dpkg/info/mender-setup.postinst configure
root 20305 0.0 0.0 1231976 9884 pts/3 Sl+ 19:15 0:00 mender-setup --quiet --device-type eac-035.local --demo=false --hosted-mender --tenant-token Paste your Hosted Mender token here --update-poll 1800 --inventory-poll 28800 --retry-poll 300
In our kitting procedure is done by ansible automatically so this design change causes hangup problem on our system.
Please revert the change as soon as possible or release new install script to be able to skip interactive configuration at install timing!!!