MySQL Bugs: #42395: Warning for DROP DATABASE send to slave as an error if mysql.proc is corrupted

Bug #42395	Warning for DROP DATABASE send to slave as an error if mysql.proc is corrupted
Submitted:	27 Jan 2009 20:16
Reporter:	Serge Kozlov	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: General	Severity:	S2 (Serious)
Version:	5.1,6.0	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
The problem found for bug#37710. 
Even bug appears for replication it is not a replication issue.

There are master and slave. Master has the corrupted table mysql.proc.
DROP DATABASE on master performed successfully but returns following warning:

Warnings:
Error	1017	Can't find file: 'proc' (errno: 2)

Same statement on slave returns the error :

Query caused different errors on master and slave.     Error on master:
'Can't find file: '%-.200s' (errno: %d)' (1017), Error on slave: 'no error' (0). Default
database: 'mysqltest1'. Query: 'DROP DATABASE mysqltest1'

How to repeat:
Please use description or attached file with test case.

Suggested fix:
Mats suggestion:
Probably there are two options to solve the problem:
1. It is not critical and then it should not be an error in the warning stack
2.It is critical and do not allow the DROP statement to proceed, effectively leaving database in place.