creating scan job creating scan job using external trivy adapter

[tangyanhan]

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

Expected behavior and actual behavior:

External trivy adapter should work with harbor properly

Steps to reproduce the problem:

1. Install trivy adapter with helm chart separately
2. Add trivy adapter and the status says 'Healthy'
3. Use this external trivy adapter to scan images and the job soon failed with log:

2025-03-21T10:37:33Z [INFO] [/pkg/scan/job.go:167]: Report mime types: [application/vnd.security.vulnerability.report; version=1.1]
2025-03-21T10:37:34Z [ERROR] [/pkg/scan/job.go:370]: scan job: submit scan request: v1 client: submit scan: enqueuing scan job: creating scan job creating scan job: write tcp 172.21.9.169:52842->172.21.9.181:6379: write: broken pipe: general response handler: unexpected status code: 500, expected: 202

Versions:
Please specify the versions of following systems.

• harbor version: [v2.10.3-c8c11b46]

[Vad1mo]

can you share your config?

[MinerYang]

Could you please share your logs of harbor-jobservice and the redis log?

[tangyanhan]

can you share your config?

![Image](https://github.com/user-attachments/assets/68ec111c-42e5-4ed9-b2ce-6121535e3e49)

This trivy adapter is actually installed independently with helm install and standalone redis instance, while the harbor system was installed with offline installer, which has a builtin trivy adapter as well.