[MXS-4309] mxs2456_trx_replay_cap assumes a promotion order for servers Created: 2022-09-23 Updated: 2023-01-20 Resolved: 2023-01-19 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | test |
| Affects Version/s: | 2.5 |
| Fix Version/s: | 2.5.25 |
| Type: | Task | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-172, MXS-SPRINT-173, MXS-SPRINT-174, MXS-SPRINT-175 |
| Description |
|
The test_replay_failure section in mxs2456_trx_replay_cap assumes that the servers are promoted in the order they are declared. However, it does not check that failover has actually happened before proceeding to block the next node. This causes the test to fail as it assumes the third failover would be rejected but it ends up working as there is only two replay attempts. The right thing to do would be to check that failover has happened before proceeding to block the next node. |