could we add redis connection succeded log once it ready

[MinerYang]

Description

When redis service is not ready, will have the redis connection refused error without timestamp, but once it's ready, no log here, inconvenient to check is redis ready for trivy.

kubo@W6878U70Y2IWQ:~$ kubectl logs -f harbor-trivy-0 -n tanzu-system-registry
Appending internal tls trust CA to ca-bundle ...
Internal tls trust CA /etc/harbor/ssl/trivy/ca.crt appended ...
Internal tls trust CA appending is Done.
{"time":"2023-11-28T02:50:44.031587812Z","level":"INFO","msg":"Starting harbor-scanner-trivy","version":"dev","commit":"none","built_at":"unknown"}
{"time":"2023-11-28T02:50:44.033398243Z","level":"WARN","msg":"trivy cache dir does not exist","path":"/home/scanner/.cache/trivy"}
{"time":"2023-11-28T02:50:44.034127583Z","level":"WARN","msg":"trivy reports dir does not exist","path":"/home/scanner/.cache/reports"}
ERROR: write_concurrency_controls_max_concurrency - dial tcp 100.66.252.29:6379: connect: connection refused
ERROR: worker.fetch - dial tcp 100.66.252.29:6379: connect: connection refused
ERROR: periodic_enqueuer.should_enqueue - dial tcp 100.66.252.29:6379: connect: connection refused
ERROR: heartbeat - dial tcp 100.66.252.29:6379: connect: connection refused
ERROR: write_known_jobs - dial tcp 100.66.252.29:6379: connect: connection refused
ERROR: periodic_enqueuer.loop.enqueue - dial tcp 100.66.252.29:6379: connect: connection refused
ERROR: worker.fetch - dial tcp 100.66.252.29:6379: connect: connection refused
ERROR: worker.fetch - dial tcp 100.66.252.29:6379: connect: connection refused
ERROR: worker.fetch - dial tcp 100.66.252.29:6379: connect: connection refused
ERROR: worker.fetch - dial tcp 100.66.252.29:6379: connect: connection refused
ERROR: worker.fetch - dial tcp 100.66.252.29:6379: connect: connection refused

Desired Behavior

• could we add something like redis is ready for trivy log for user to acknowledge
• wanna to confirm what kind of data trivy would written into redis db ? I got something like this

127.0.0.1:6379[5]> keys *
1) "harbor.scanner.trivy:job-queue:worker_pools:c42e86939479a920c2650a48"
2) "harbor.scanner.trivy:job-queue:known_jobs"
3) "harbor.scanner.trivy:job-queue:worker_pools"
4) "harbor.scanner.trivy:job-queue:jobs:scan_artifact:lock"
5) "harbor.scanner.trivy:job-queue:last_periodic_enqueue"
6) "harbor.scanner.trivy:job-queue:jobs:scan_artifact:lock_info"
7) "harbor.scanner.trivy:job-queue:jobs:scan_artifact:max_concurrency"
127.0.0.1:6379[5]>
127.0.0.1:6379[5]>
127.0.0.1:6379[5]> keys *
1) "harbor.scanner.trivy:job-queue:worker_pools:c42e86939479a920c2650a48"
2) "harbor.scanner.trivy:job-queue:worker:68a700ad8439f606a1b25993"
3) "harbor.scanner.trivy:job-queue:jobs:scan_artifact:c42e86939479a920c2650a48:inprogress"
4) "harbor.scanner.trivy:data-store:scan-job:54c4d6519490e8de5ec03b4a"
5) "harbor.scanner.trivy:job-queue:known_jobs"
6) "harbor.scanner.trivy:job-queue:worker_pools"
7) "harbor.scanner.trivy:job-queue:jobs:scan_artifact:lock"
8) "harbor.scanner.trivy:job-queue:last_periodic_enqueue"
9) "harbor.scanner.trivy:job-queue:jobs:scan_artifact:lock_info"
10) "harbor.scanner.trivy:job-queue:jobs:scan_artifact:max_concurrency"
127.0.0.1:6379[5]>
127.0.0.1:6379[5]> keys *
1) "harbor.scanner.trivy:job-queue:worker_pools:c42e86939479a920c2650a48"
2) "harbor.scanner.trivy:data-store:scan-job:54c4d6519490e8de5ec03b4a"
3) "harbor.scanner.trivy:job-queue:known_jobs"
4) "harbor.scanner.trivy:job-queue:worker_pools"
5) "harbor.scanner.trivy:job-queue:jobs:scan_artifact:lock"
6) "harbor.scanner.trivy:job-queue:last_periodic_enqueue"
7) "harbor.scanner.trivy:job-queue:jobs:scan_artifact:lock_info"
8) "harbor.scanner.trivy:job-queue:jobs:scan_artifact:max_concurrency"

Actual Behavior

errors out at the time container initialized with error but no timestamp, then trivy would scanning as normal without connection error later.
Inconvenient to judge is Redis still have issue or not.

Reproduction Steps

1. install harbor 2.9.1 with trivy
2. sometimes redis start and ready after trivy
3. trivy conatiner log has error without timestamp
...

Target

None

Scanner

None

Output Format

None

Mode

None

Debug Output

trivy: 0.46.1

Operating System

Photon

Version

scanner [ / ]$ trivy -v
Version: dev

Checklist

• Run trivy image --reset
• Read the troubleshooting

[chen-keinan]

@MinerYang can you turn on debug level by setting Env SCANNER_LOG_LEVEL=debug

you can also doing so by helm value

After log level is updated please run again with redis and add logs with connection issue

btw: this issue related to harbor-scanner-trivy repo

[knqyf263]

I've transferred it under harbor-scanner-trivy.

[MinerYang]

Thanks @chen-keinan ,

I will take a try