Hi,
On 12/05/2017 05:46 PM, Laurent GUILLIER wrote:
Hi,
first of all thanks for Rauc which is a very nice piece of software!
I am now trying to use rauc on a imx6 target, along with hawkbit as the
update server. Everything runs fine, except that after the reboot
following the successful slot update, the rauc-hawkbit client detects
the update again, and starts the process again and again ... the slots
are alternated as it would expected if each update cycle was required
(i.e. different bundles).
Looks like the client doesn't tell hawkbit the update process was
succesfully performed, from downloading to reboot on the brand new slot.
Any clue to solve that little issue would be appreciated!
do you have any log from the rauc-hawkbit python client running during
the update? Not that you can also start it in debug mode to increase
verbosity as listed here [1]. A log would help finding out what is going
on and what not.
And, do you see feedback in the targets Action history view in the
hawkBit Web UI? As in the Demo video [2] shown at 0:25. The update must
have a green mark to be considered successful by hawkBit and to not
trigger an update again.
Best regards
Enrico
[1] https://github.com/rauc/rauc-hawkbit#debugging
[2] https://www.youtube.com/watch?v=SLX0Fd_y6Cc
--
Pengutronix e.K. | Enrico Jörns|
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
___
RAUC mailing list
