Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-23608

galera_sr.GCF-597 MTR failed: query 'ROLLBACK' succeeded - should have failed with errno 1213

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.4.15, 10.5.6
    • 10.4.16, 10.5.7, 10.6.0
    • Galera, Tests
    • None
    • kvm-rpm-rhel8-amd64

    Description

      galera_sr.GCF-597 failed on BB 10.4 and BB 10.5: "query 'ROLLBACK' succeeded - should have failed with errno 1213".
      It seems to be a sporadic issue.

      stdio.log:

      10.4.15 88e70f4caea34e0d7677b1fa646151b8b87dd3ab

      galera_sr.GCF-597 'innodb'               w2 [ fail ]
              Test ended at 2020-08-25 08:20:17
       
      CURRENT_TEST: galera_sr.GCF-597
      mysqltest: At line 27: query 'ROLLBACK' succeeded - should have failed with errno 1213...
       
      The result from queries just before the failure was:
      < snip >
      connection node_1;
      connection node_1;
      CREATE TABLE t1 (f1 INTEGER PRIMARY KEY AUTO_INCREMENT) ENGINE=InnoDB;
      SET wsrep_trx_fragment_size = 1;
      SET AUTOCOMMIT=OFF;
      START TRANSACTION;
      connection node_2;
      SET AUTOCOMMIT=OFF;
      START TRANSACTION;
      INSERT INTO t1 VALUES (1);
      connection node_1;
      INSERT INTO t1 VALUES (1);
      INSERT INTO t1 VALUES (2);
      INSERT INTO t1 VALUES (3);
      INSERT INTO t1 VALUES (4);
      INSERT INTO t1 VALUES (5);
      connection node_2;
      ROLLBACK;
      

      Attachments

        Activity

          People

            jplindst Jan Lindström (Inactive)
            stepan.patryshev Stepan Patryshev (Inactive)
            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.