Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GС schedule causes errors #20384

Closed
sivsoft opened this issue May 1, 2024 · 3 comments
Closed

GС schedule causes errors #20384

sivsoft opened this issue May 1, 2024 · 3 comments
Assignees
Labels
more-info-needed The issue author need to provide more details and context to the issue Stale

Comments

@sivsoft
Copy link

sivsoft commented May 1, 2024

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior:
I have a schedule set up to clean up Garbage Collection. However, it is not working. I can manually execute "GC Now" with no problem. But the automatic schedule causes errors.

sy-harbor_jobservice_GC_error_001

Here is the error in the jobservice.log
May 1 03:00:01 172.26.0.1 jobservice[931]: 2024-05-01-01T00:00:01Z [ERROR] [/jobservice/runner/redis.go:123]: Job 'GARBAGE_COLLECTION:0d2d09b7da4adcf767d0dee8' exit with error: runtime error: interface conversion: interface {} is nil, not string; stack: goroutine 51 [running]:

Harbor was updated sequentially from 2.3.1 to 2.4.0, then to 2.6.0 and finally to 2.8.3, this is not a new install.

Versions:

  • harbor version: [2.8.3]
  • docker engine version: [24.0.5, build ced0996]
  • docker-compose version: [2.19.1]
@MinerYang
Copy link
Contributor

MinerYang commented May 6, 2024

Hi @sivsoft ,

Are you using internal or external Redis ?
Could you give us more contexts if your jobservice logs and the env of your jobservice?

  • And the data from your db
select * from schedule where vender_type='GARBAGE_COLLECTION';

ref: #15850

@wy65701436 wy65701436 added the more-info-needed The issue author need to provide more details and context to the issue label Jun 12, 2024
Copy link

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

@github-actions github-actions bot added the Stale label Aug 11, 2024
Copy link

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more-info-needed The issue author need to provide more details and context to the issue Stale
Projects
None yet
Development

No branches or pull requests

3 participants