Bug #26237 Advisor rules need to include their subscription level

• Submitted: 9 Feb 2007 19:01
• Modified: 15 Oct 2009 16:02
• Reporter: Sloan Childers
• Status: Closed
• Category: MySQL Enterprise Monitor: Advisors/Rules
• Severity: S2 (Serious)
• OS: Any
• Assigned to: Sloan Childers
• CPU Architecture: Any

[9 Feb 2007 19:01] Sloan Childers

Description:
Currently you can import a platinum level bundle into a Merlin server that only has a gold product key.

How to repeat:
See above.

Suggested fix:
Add an XML field to each rule containing it's subscription level.  We can then filter out inappropriate rules based on the installed server product key.

[2 Mar 2007 19:51] Sloan Childers

I added the subscription level to each advisor bundle.

[2 Mar 2007 19:52] Sloan Childers

We are not going to enforce the product key check with advisor bundle imports for the 1.1.0 release.

[27 Aug 2009 16:12] Enterprise Tools JIRA Robot

Sloan Childers writes: 
this has been fixed in trunk/2.2

[22 Sep 2009 15:32] Enterprise Tools JIRA Robot

Sloan Childers writes: 
Patch installed in versions => 2.2.0.1501.

[12 Oct 2009 23:52] Enterprise Tools JIRA Robot

Marcos Palacios writes: 
Verified fixed in service manager build 2.2.0.1501.

[15 Oct 2009 16:02] Tony Bedford

An entry was added to the 2.2.0 changelog:

        It was possible to import a Platinum level bundle into a
        MySQL Monitor server that only had a Gold product key.