Many error logs about ParseUInt

[sven-urbanski-freiheit-com]

We should consider silencing those, as they are generally not helpful.

[martin-gutwin]

Hi @sven-urbanski-freiheit-com ,

I just stumbled upon this in v13.20.1.

kuberpult-rollout-service gives us constant errors like this:

{"level":"warn","ts":1753784561.576356,"caller":"service/dispatcher.go:52","msg":"error getting version \"6a0e1ff20a68eab57e3cd5876e08bdd53a54f6af\" for app \"my-app\" on environment \"dev\": could not parse GitRevision '6a0e1ff20a68eab57e3cd5876e08bdd53a54f6af' for app 'my-app' in env 'dev': strconv.ParseUint: parsing \"6a0e1ff20a68eab57e3cd5876e08bdd53a54f6af\": invalid syntax"}

I looked a bit into it and it seems to me that this line:

kuberpult/services/rollout-service/pkg/service/dispatcher.go

Line 49 in 0449463

revision := ev.Application.Status.Sync.Revision

is a problem.

For us Application.Status.Sync.Revision is the commitSHA of the HEAD of the main branch in our manifest repository for all apps in all environments and I don't understand how and why we should change this to integers, since the HEAD of main contains all information about the current desired state in every environment/app.

For now it seems it just affects:

1. the ability of the rollout service to display the state of each ArgoCD app/environment in the Kuberpult frontend and
2. warnings spam in the logs

Am I right with my assumptions of the effects of this error? Is there a way to fix this for us so we can see the rollout status in Kuberpult again? Can we assist in Debugging?

Thank you very much for your help!