Parsed test spec with 2 sessions

starting permutation: s1-begin s1-insert s2-begin s2-update-node-1 s1-abort s2-abort
create_distributed_table


step s1-begin: BEGIN;
step s1-insert: INSERT INTO t1 SELECT generate_series(1, 100);
step s2-begin: BEGIN;
step s2-update-node-1:
    -- update a specific node by address
    SELECT master_update_node(nodeid, 'localhost', nodeport + 10)
      FROM pg_dist_node
     WHERE nodename = 'localhost'
       AND nodeport = 57637;
 <waiting ...>
step s1-abort: ABORT;
step s2-update-node-1: <... completed>
master_update_node


step s2-abort: ABORT;
master_remove_node




starting permutation: s1-begin s1-insert s2-begin s2-update-node-1-force s2-abort s1-abort
create_distributed_table


step s1-begin: BEGIN;
step s1-insert: INSERT INTO t1 SELECT generate_series(1, 100);
step s2-begin: BEGIN;
step s2-update-node-1-force:
    -- update a specific node by address (force)
    SELECT master_update_node(nodeid, 'localhost', nodeport + 10, force => true, lock_cooldown => 100)
      FROM pg_dist_node
     WHERE nodename = 'localhost'
       AND nodeport = 57637;
 <waiting ...>
step s2-update-node-1-force: <... completed>
master_update_node


step s2-abort: ABORT;
step s1-abort: ABORT;
WARNING: this step had a leftover error message
FATAL:  terminating connection due to administrator command
FATAL:  terminating connection due to administrator command
SSL connection has been closed unexpectedly
server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.

master_remove_node