Swupdate Suricatta Hawkbit Reporting Errors

[Caleb]

Team,

Using swupdate v2025.05.0 suricatta daemon, SWUpdate sends deploymentBase feedback to Hawkbit, but encounters frequent response errors from Hawkbit.

Dec 12 17:40:00 eac6000 swupdate.sh[3301]: [TRACE] : SWUPDATE running :  [channel_log_effective_url] : Channel's effective URL resolved to http://{{hawkbit URL}}:8081/default/controller/v1/{{controllerId}}/deploymentBase/107/feedback
Dec 12 17:40:00 eac6000 swupdate.sh[3301]: [ERROR] : SWUPDATE failed [0] ERROR channel_curl.c : channel_log_reply : 975 : Channel operation returned HTTP error code 403.
Dec 12 17:40:00 eac6000 swupdate.sh[3301]: [DEBUG] : SWUPDATE running :  [channel_log_reply] : The error message is: '{"exceptionClass":"org.eclipse.hawkbit.repository.exception.AssignmentQuotaExceededException","errorCode":"hawkbit.server.error.quota.tooManyEntries","message":"Quota exceeded: Cannot assign 1 more ActionStatus entities to Action '107'. The maximum is 1000."}'
Dec 12 17:40:00 eac6000 swupdate.sh[3301]: [ERROR] : SWUPDATE failed [0] ERROR server_hawkbit.c : process_notification_thread : 1052 : Error while sending log to server.

It doesn't impact the final result, the image still succeeds, but the logs are full of these errors. Performing delta updates also sends feedback for what appears to be all chunks, and as a result there are thousands of reported errors during delta updates. Again, doesn't affect functionality, but appears problematic in the logs.

Has anyone else seen this?

Thanks,

- Caleb