MySQL Bugs: #43735: Multiple Agent Instance Config Files Lost when using MEM Upgrade Installer

Bug #43735	Multiple Agent Instance Config Files Lost when using MEM Upgrade Installer
Submitted:	18 Mar 2009 20:59	Modified:	22 Sep 2009 17:20
Reporter:	Chris Calender	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Enterprise Monitor: Installing	Severity:	S3 (Non-critical)
Version:	2.0.5.7153	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	Agent, configuration files lost, multiple, upgrade installer

Description:
It is possible to monitor multiple MySQL instances using the same agent.

What you do is simply create an additional folder, say "mysql2", in the following directory:

/opt/mysql/enterprise/agent/etc/instances

In that folder, you create a file named: agent-instance.ini.

This is an exact duplicate of the file in /opt/mysql/enterprise/agent/etc/instances/mysql/agent-instance.ini, however, just the mysql host, username, password, and port differ.

When you upgrade MEM using the Upgrade Installer, the extra instance folders and files that were created are deleted.

Note they do exist in the backup, but it would be nice if they were simply included when the upgrade occurs. 

How to repeat:
Create additional instance folders and ini files to montitor more than one instance with a single agent.

Then, upgrade MEM using an Upgrade Installer.

You'll see your extra instance folders are deleted.

Suggested fix:
Include these folders when upgrading.

Should we work to fix this issue? Could you specify the approach for the upgrade installer to support multiple agent instances? Please specify the "Target Version" tag, thanks.

This bug is not scheduled to be fixed at this time.