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
Currently, the namespace value is hardcoded as "harbor_job_service_namespace".
I encountered issues with the garbage collection job, which was consistently in an ERROR state with the following message:
2025-01-21T12:05:04Z [ERROR] [/jobservice/runner/redis.go:123]: Job 'GARBAGE_COLLECTION:556a5514773eda909642fa2d' exit with error: run error: error retrieving 'blobs::*' keys
Initially, I thought that "harbor_job_service_namespace" was meant to be a reference that shouldn't be customized. However, after changing it to match the current Redis namespace, the garbage collection jobs started working correctly.
Could you please confirm if my understanding is correct and whether this variable should indeed be configurable?
Thanks in advance for your support!
The text was updated successfully, but these errors were encountered:
How do you install and use the redis? Jobservice load the config from a internal config yaml file by default,so if jobservice start and running normally without any error msg, this issue suppose not occurs due to the namespace config.
BTW, have you set any env JOB_SERVICE_POOL_REDIS_NAMESPACE inside your container?
Hi Harbor team,
I noticed that in the Harbor Helm chart, the jobservice configuration includes a hardcoded namespace:
Currently, the namespace value is hardcoded as "harbor_job_service_namespace".
I encountered issues with the garbage collection job, which was consistently in an ERROR state with the following message:
Initially, I thought that "harbor_job_service_namespace" was meant to be a reference that shouldn't be customized. However, after changing it to match the current Redis namespace, the garbage collection jobs started working correctly.
Could you please confirm if my understanding is correct and whether this variable should indeed be configurable?
Thanks in advance for your support!
The text was updated successfully, but these errors were encountered: