Bug #45020 Data purge setting incorrect after updating from 1.3

• Submitted: 21 May 2009 23:31
• Modified: 25 Jun 2009 17:32
• Reporter: Bill Weber
• Status: Closed
• Category: MySQL Enterprise Monitor: Server
• Severity: S3 (Non-critical)
• Version: 2.1.0.1049
• OS: Any
• Assigned to: Eric Herman
• CPU Architecture: Any

[21 May 2009 23:31] Bill Weber

Description:
If setting the historical data purge to anything over 4 weeks (didn't try them all) in 1.3, they (data and quan) will be set to 4 weeks after upgrading to 2.1. The purge setting for logs is correct. Also, the purge settings are correct if updating from 1.3 to 2.0 (although the quan data is not set as it is in 2.1).

How to repeat:
- install and run 1.3 dashboard
- set historical data purge to anything *more* 4 weeks
- run 2.1 update installer
| historical data and quan purge is set to 4 weeks

[26 May 2009 16:13] Gary Whizin

Because there's no quan setting in 1.3, it should default to whatever the data purge setting is