-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
None
-
False
-
None
-
False
-
MGDOBR - Sprint 222
Issue Description:
BridgeIngressServiceImpl and BridgeExecutorServiceImpl make the bold claim that if the CRD already exists and it's Spec is unchanged the resource is READY however the resource could be FAILED. We need to check the CRD Status.
Acceptance Criteria:
A FAILED CRD whose Specification is unchanged should stay as FAILED in the manager and not set to READY.
- duplicates
-
MGDOBR-989 Bridge/Processor status set to READY without being fully initialized
- Closed
- relates to
-
MGDOBR-779 Make BridgeInstance error handling strategy editable
- Closed