Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4309

mxs2456_trx_replay_cap assumes a promotion order for servers

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.5
    • 2.5.25
    • test
    • None
    • 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.

      Attachments

        Activity

          People

            markus makela markus makela
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.