You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have successfully integrated the rauc-hawkbit-client into our embedded system. We are running it as a systemd service, which periodically polls the hawkbit server, then downloads the rauc bundle when it is added to a live 'rollout'. The client then uses the dbus api to update the rauc slot(s).
The issue we are facing is a race between a post_install.sh script that we have added to the rauc.conf file (this essentially stores some app state in a persistent data partition and triggers a reboot) and the final 'POST' message that the rauc-hawkbit-client state machine generates (this is what informs the hawkbit server that the install was successful).
As things stand right now, the rauc-hawkbit-client process simply issues this post after the last rauc command ('writing the new slot and verifying it'), which is 'too soon' for us. Ideally, as the application programmer, we would like to make this call 'at will' (i.e. after verifying that the update succeeded, probably after a restart).
Do you have any plans for introducing such file based hooks (or can you point us in the right direction, in case we want to add them to this project) ?
Hello,
We have successfully integrated the rauc-hawkbit-client into our embedded system. We are running it as a systemd service, which periodically polls the hawkbit server, then downloads the rauc bundle when it is added to a live 'rollout'. The client then uses the dbus api to update the rauc slot(s).
The issue we are facing is a race between a post_install.sh script that we have added to the rauc.conf file (this essentially stores some app state in a persistent data partition and triggers a reboot) and the final 'POST' message that the rauc-hawkbit-client state machine generates (this is what informs the hawkbit server that the install was successful).
As things stand right now, the rauc-hawkbit-client process simply issues this post after the last rauc command ('writing the new slot and verifying it'), which is 'too soon' for us. Ideally, as the application programmer, we would like to make this call 'at will' (i.e. after verifying that the update succeeded, probably after a restart).
Do you have any plans for introducing such file based hooks (or can you point us in the right direction, in case we want to add them to this project) ?
Thanks,
Sidd (delhiryder)