`No SBOM` logic between SBOM deleted and literally no SBOM generation should be the same
zyyw opened this issue · comments
How to reproduce?
- deploy a harbor instance with the latest source code
- replicate redis:latest from dockerhub to harbor
- select all artifacts of the redis artifacts replicated, and click
GENERATE SBOM
- delete the first SBOM generated
- the
No SBOM
between SBOM deleted and literally no SBOM generation is not the same regarding layout and hover message
![Screenshot 2024-05-31 at 4 16 48 PM](https://private-user-images.githubusercontent.com/6709992/335499626-a9585fbf-55ce-461c-b17f-362a8473ea81.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAyMDE4OTQsIm5iZiI6MTcyMDIwMTU5NCwicGF0aCI6Ii82NzA5OTkyLzMzNTQ5OTYyNi1hOTU4NWZiZi01NWNlLTQ2MWMtYjE3Zi0zNjJhODQ3M2VhODEucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcwNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MDVUMTc0NjM0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZGI5ZjcwNmNmYzhiNDA3NTQ2M2RkZjRiOGQ2M2JhMTEwNGExMTIyYTNjZTBkYmZmOTk4MzllYzI1ODFlZmY5OCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.u53GrMqf92kGAfTW1YVUS8yvVu6hCaap9JBUBgBHmGU)
This might be due to red rectangle having sbom_overview
of something like below:
"sbom_overview": {
"duration": 16,
"end_time": "2024-05-31T08:11:23.000Z",
"scan_status": "Success",
"start_time": "2024-05-31T08:11:06.808Z"
}
this issue #20320 requires the sbom_overview to return a status to stop refresh