Bug #50175 rpl.rpl_backup fails on mysql-backup-backport; incident is not shown in res file
Submitted: 8 Jan 2010 9:58 Modified: 8 Jan 2010 14:54
Reporter: Andrei Elkin Email Updates:
Status: Patch queued Impact on me:
None 
Category:MySQL Server: Backup Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Triage: Triaged: D2 (Serious)

[8 Jan 2010 9:58] Andrei Elkin
Description:
A recent failure with the test

https://central.sun.net/http://pb2.norway.sun.com/?template=mysql_show_test_failure&test_f...

-master-bin.000001	#	Incident	1	#	#2 (RESTORE_ON_MASTER)
+master-bin.000001	#	Incident	1	#	#2 ((null))
 master-bin.000001	#	Rotate	1	#	master-bin.000002;pos=4
 # Showing tables on master.
 SHOW FULL TABLES FROM rpl_backup;
@@ -227,7 +227,7 @@
 Replicate_Wild_Do_Table	
 Replicate_Wild_Ignore_Table	
 Last_Errno	1590
-Last_Error	The incident RESTORE_ON_MASTER occured on the master. Message: A restore operation was initiated on the master.
+Last_Error	The incident (null) occured on the master. Message: A restore operation was initiated on the master.

indicates an issue with reporting an incident.

How to repeat:
To see PB2 or run the test.
[8 Jan 2010 12:47] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/96381

3043 Andrei Elkin	2010-01-08
      Bug #50175  rpl.rpl_backup fails on mysql-backup-backport; incident is not shown in res file
      
      the test failed because of missed item of Incident_log_event::description array. The one happened to not have been merged.
      
      Fixed with adding RESTORE_ON_MASTER to the array.
[8 Jan 2010 14:44] Chuck Bell
Patch approved.
[8 Jan 2010 14:54] Andrei Elkin
queued to backup-backport tree.