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

Jump to bottom

CVE export error "404 page not found" #18380

Closed
AlexBarth13 opened this issue Mar 20, 2023 · 4 comments · Fixed by #18398
Closed

CVE export error "404 page not found" #18380

AlexBarth13 opened this issue Mar 20, 2023 · 4 comments · Fixed by #18398
Assignees
@chlins
Labels
area/cve-export Related to cve export feature kind/bug known-issue target/2.6.5 target/2.7.2 target/2.8.0

Comments

@AlexBarth13
Copy link

Hi all,

In our environment (Harbor v2.7.0) we detected the issue with exporting the CVE report.

image

jobservice.log:

Mar 20, 2023 @ 19:46:19.396    Mar 20 15:16:19 172.20.0.1 jobservice[25867]: 2023-03-20T14:16:19Z [ERROR] [/jobservice/job/impl/scandataexport/scan_data_export.go:130]: Export Job Id = 7.678138e+06. Error when persisting report file /var/scandata_exports/scandata_export_7.678138e+06.csv to persistent storage: http status code: 404, body: 404 page not found    
Mar 20, 2023 @ 19:45:48.329    Mar 20 15:15:48 172.20.0.1 jobservice[25867]: 2023-03-20T14:15:48Z [ERROR] [/jobservice/job/impl/scandataexport/scan_data_export.go:130]: Export Job Id = 7.678137e+06. Error when persisting report file /var/scandata_exports/scandata_export_7.678137e+06.csv to persistent storage: http status code: 404, body: 404 page not found    
Mar 20, 2023 @ 19:45:25.889    Mar 20 15:15:25 172.20.0.1 jobservice[25867]: 2023-03-20T14:15:25Z [ERROR] [/jobservice/job/impl/scandataexport/scan_data_export.go:130]: Export Job Id = 7.678135e+06. Error when persisting report file /var/scandata_exports/scandata_export_7.678135e+06.csv to persistent storage: http status code: 404, body: 404 page not found

We already checked the permissions in the filesystem and the Docker configuration and we didn't saw any "strange" configuration.

Does anyone have an idea, why this is not working?

P.S.: Maybe related to goharbor/harbor-helm#1444

Thank you in advance!



Alexander Barth (alexander.barth@mercedes-benz.com) on behalf of Mercedes-Benz Tech Innovation GmbH, Provider Information
@Vad1mo
Copy link
Member

Vad1mo commented Mar 20, 2023

Duplicate of goharbor/harbor-helm#1444

@Vad1mo Vad1mo marked this as a duplicate of goharbor/harbor-helm#1444 Mar 20, 2023
@Vad1mo
Copy link
Member

Vad1mo commented Mar 20, 2023

related to goharbor/harbor-helm#1320

@chlins
Copy link
Member

chlins commented Mar 23, 2023

related to goharbor/harbor-helm#1320

@Vad1mo We reproduced this issue seems not related with goharbor/harbor-helm#1320, it's another issue.

chlins added a commit to chlins/harbor that referenced this issue Mar 23, 2023
@chlins
fix: fix the invalid jobid for scan data export
92e00f1 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
@chlins chlins added target/2.8.0 area/cve-export Related to cve export feature kind/bug labels Mar 23, 2023
@chlins chlins mentioned this issue Mar 23, 2023
Merged
5 tasks
chlins added a commit to chlins/harbor that referenced this issue Mar 23, 2023
@chlins
fix: fix the invalid jobid for scan data export
c53584d 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
@zyyw zyyw mentioned this issue Mar 23, 2023
Closed
chlins added a commit to chlins/harbor that referenced this issue Mar 24, 2023
@chlins
fix: fix the invalid jobid for scan data export
3a0a0c2 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
@chlins chlins mentioned this issue Mar 24, 2023
Merged
5 tasks
chlins added a commit to chlins/harbor that referenced this issue Mar 24, 2023
@chlins
fix: fix the invalid jobid for scan data export
e6a46d4 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Mar 24, 2023
@chlins
fix: fix the invalid jobid for scan data export
9f313f7 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Mar 24, 2023
@chlins
fix: fix the invalid jobid for scan data export
64c2dfe 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
@chlins chlins mentioned this issue Mar 24, 2023
Merged
5 tasks
@chlins
Copy link
Member

chlins commented Mar 25, 2023 •
edited

The issue will happen when the execution primary key auto-increment ID grows to 1000000+, currently no temporary workaround for this, please upgrade to v2.6.5/v2.7.2/v2.8.0 to fix it.

chlins added a commit to chlins/harbor that referenced this issue Mar 28, 2023
@chlins
fix: fix the invalid jobid for scan data export
28a0a36 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Mar 28, 2023
@chlins
fix: fix the invalid jobid for scan data export
6033f78 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Mar 28, 2023
@chlins
fix: fix the invalid jobid for scan data export
79cb349 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Mar 28, 2023
@chlins
fix: fix the invalid jobid for scan data export
45643cc 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit that referenced this issue Mar 28, 2023
@chlins
[cherry-pick] fix: fix the invalid jobid for scan data export (#18421)
f615e41 
fix: fix the invalid jobid for scan data export

Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: #18380

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit that referenced this issue Mar 28, 2023
@chlins
[cherry-pick] fix: fix the invalid jobid for scan data export (#18420)
4a09c55 
fix: fix the invalid jobid for scan data export

Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: #18380

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Mar 28, 2023
@chlins
fix: fix the invalid jobid for scan data export
31449cd 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Mar 28, 2023
@chlins
fix: fix the invalid jobid for scan data export
f3667d5 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: goharbor#18380

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit that referenced this issue Mar 29, 2023
@chlins
fix: fix the invalid jobid for scan data export (#18398)
6e9f723 
Change the JobId param type from int to string, use int will bring some
problems for encode/decode type mismatch which generate the invalid
repository name.

Fixes: #18380

Signed-off-by: chlins <chenyuzh@vmware.com>
@zyyw zyyw mentioned this issue Apr 10, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chlins chlins

Labels
area/cve-export Related to cve export feature kind/bug known-issue target/2.6.5 target/2.7.2 target/2.8.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: fix the invalid jobid for scan data export chlins/harbor
4 participants
@Vad1mo @wy65701436 @chlins @AlexBarth13