Loading...

XML

Word

Printable

Type: Task
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Blocked:
False
Blocked Reason:
None
Ready:
False

Sprint:
MGDOBR - Sprint 222

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Issue Description:

BridgeIngressServiceTest.testBridgeIngressCreationWhenSpecAlreadyExists() and BridgeExecutorServiceTest.testBridgeExecutorCreationWhenSpecAlreadyExists() are failing regularly and have been disabled. Their approach needs to be reviewed. Disable for now.

Acceptance Criteria:
The tests work reliably.

is caused by

MGDOBR-779 Make BridgeInstance error handling strategy editable

Closed

relates to

MGDOBR-989 Bridge/Processor status set to READY without being fully initialized

Closed

MGDOBR-991 BridgeIngressServiceTest/BridgeExecutorServiceTest: Disable failing tests

Closed

mentioned on

Merge request - Updated US source to: 3eb202f MGDOBR-992: BridgeIngressServiceTest/BridgeExecutorServiceTest: Fix disabled tests (#1034)

Merge request - Updated US source to: 4b353d8 MGDOBR-992: BridgeIngressServiceTest/BridgeExecutorServiceTest: Fix disabled tests (#1034) - Update kustomization images (#1038)

Merge request - Updated US source to: 422c4be MGDOBR-951: shard exposes applications with the host and the ssl certificates provided by the manager (#1006) - Update kustomization images (#1039)

Merge request - Updated US source to: 2949763 [MGDOBR-899] Implement E2E test to allow a user to update Action Para… (#1019)

Merge request - Updated US source to: adfda32 [MGDOBR-989] Update Bridge/Processor from Shard only for READY status

Solved by commit 98b0282a3fe053052d8e19dc1ad7ed5a12290320.

(4 mentioned on)

Assignee:: Michael Anstis

Reporter:: Michael Anstis

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2022/08/04 8:00 AM

Updated:: 2022/09/09 7:17 AM

Resolved:: 2022/08/08 8:34 AM