Bug #53826 Possible to load custom-export bundle as regular bundle, trash schedules
Submitted: 19 May 2010 20:21 Modified: 27 May 2010 13:11
Reporter: Josh Sled Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Web Severity:S3 (Non-critical)
Version:2.2.0.1709 OS:Any
Assigned to: Josh Sled CPU Architecture:Any

[19 May 2010 20:21] Josh Sled 
Description:
See subject.

How to repeat:
- Export custom bundle or take one from email.
- Global Settings > Advisor Bundle > select custom export bundle, "import"
- watch the logs as all your collections are unscheduled and deleted.
- be sad.
[20 May 2010 21:42] Enterprise Tools JIRA Robot 
Josh Sled writes: 
revno: 8087
revision-id: josh.sled@oracle.com-20100520213941-mg5l907yu53bcrm4
parent: josh.sled@oracle.com-20100520171557-2spqankqqf33wr95
committer: Josh Sled <josh.sled@oracle.com>
branch nick: 2.2
timestamp: Thu 2010-05-20 17:39:41 -0400
message:
  EM-4515: make sure the advisor bundle jar is not a custom-export jar
[24 May 2010 16:41] Enterprise Tools JIRA Robot 
Andy Bang writes: 
In build build 2.2.1.1721.
[24 May 2010 18:14] Enterprise Tools JIRA Robot 
Marcos Palacios writes: 
Verified fixed in Monitor build 2.2.1.1721.
[27 May 2010 13:11] MC Brown 
A note has been added to the 2.2.1 changelog: 

        It was possible to import a custom advisor bundle to replace                                                                                       
        the main advisor bundle. This would delete all existing rules,                                                                                     
        schedules and advisors. The system now checks the bundle                                                                                           
        before import.