Comment 2 for bug 1404484

I hame mariadb 10.0.14
From my servers last backup
innobackupex: MySQL binlog position: filename 'mysql-bin.000024', position 883188569, GTID of the last change '0-148-29896064'

Setting the slave up as follows after recovery from the using xtrabackup to backup and restore should allow the new slave to identify to and recover correctly with the master not the slave it was recovered from

CHANGE MASTER TO MASTER_HOST = TruemasterIp/hostmname , MASTER_USER ='repluser', MASTER_PASSWORD = 'replpass';
SET GLOBAL gtid_slave_pos
CHANGE MASTER TO '0-148-29896064'
CHANGE MASTER TO master_use_gtid=slave_pos;
start slave;

Is the steps correct?
GTID isn't well documented as yet This may help others to understand the way to get a new slave created and get around this bug