-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 10.2
-
Fix Version/s: 10.10
-
Component/s: BlobManager, S3
-
Tags:
-
Backlog priority:500
-
Sprint:nxFG 10.10.4
-
Story Points:1
The S3BinaryManagerStatusProbe does only check the first S3BinaryManager found when calling Framework.getService(BlobManager.class).getBlobProviders();.
As a result, if the deployed server has several deployed S3BinaryManager the Probe result can be partial or even inconsistent (for example if S3BinaryManager deployment order changes between environments).
The target solution return a status including all S3BinaryManager.
- causes
-
NXP-28437 S3 probe should not report failure when there are not S3 blob providers
- Resolved