What happened:
When one element fails to scan, the whole scanning process is blocked. As a result, no other components are scanned, even if they are valid and should proceed independently.
What you expected to happen:
Failure of a single element should not block the entire scanning process. The system should continue scanning remaining components and report failure only for the problematic one.
Maybe It would be possible to use priority of scans, to put lower value of failing elements?
How to reproduce it (as minimally and precisely as possible):
- Configure multiple elements/components for scanning
- Introduce an issue in one element (unreachable source)
- Scans should be triggered automatically (in our step we scanned BDBA)
- Observe that the entire process stops instead of skipping the failed element (Every new BDBA pod is picking only this failing item and stops after)
Anything else we need to know:
This behavior reduces system resilience and delays detection of issues in other components. It would be better to handle failures in isolation and aggregate results at the end.
Environment:
mODG Prod,
delivery-service 0.(?).0-0.427.0
What happened:
When one element fails to scan, the whole scanning process is blocked. As a result, no other components are scanned, even if they are valid and should proceed independently.
What you expected to happen:
Failure of a single element should not block the entire scanning process. The system should continue scanning remaining components and report failure only for the problematic one.
Maybe It would be possible to use
priorityof scans, to put lower value of failing elements?How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
This behavior reduces system resilience and delays detection of issues in other components. It would be better to handle failures in isolation and aggregate results at the end.
Environment:
mODG Prod,
delivery-service
0.(?).0-0.427.0