Bug #57045 agent upgrade installer warning message is confusing
Submitted: 27 Sep 2010 21:31 Modified: 4 Jan 2011 22:27
Reporter: Marcos Palacios Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Installing Severity:S3 (Non-critical)
Version: OS:Mac OS X
Assigned to: BitRock Merlin CPU Architecture:Any

[27 Sep 2010 21:31] Marcos Palacios
On Mac OS X, when doing an agent upgrade install via GUI, if one chose a proxy port different than 6446 (the default), then the installer suggests (puts in the install page displayed) the default port 6446 (instead of what we had used in the current installation). Then when one changes it to what we had used, it gives a warning pop up with a confusing message (see attachment; notice the extra word "do" in the message's question).

This seems to be a problem only on the installer screen that asks for the proxy port, because on the aggregator screen (w/the aggregator ports), if i have changed them and later come back to it, the values i put are still there. However, if i go back to the proxy port installer screen, the value i changed it to has been replaced with 6446 again.

This behavior does not happen on Windows when installing via GUI.

How to repeat:
- install a 2.2 agent using 6448 (or something different than 6446) for the proxy port
- run the agent upgrade installer via GUI for the previous installation
- when it gets to the proxy port installer screen, notice that it does not show port 6448 (or your choice) but it shows 6446
- change the port value to what you had in the previous installation (which should have been read from the file <install-dir>/etc/mysql-monitor-agent.ini)
- click 'Next'
- observe the message as attached here (see red highlights)
- also notice the extra word "do" in the message's question
- notice that, after you click 'ok' on the pop up, you get another pop-up (second attachment here) that tells you that you have changed the port (which is annoying in this case because you were correcting it so it would be what your previous installation had)

Suggested fix:
- display the correct proxy port as used in the previous installation
- correct the message
[6 Oct 2010 14:58] BitRock Merlin
Patch sent to Andy
[8 Oct 2010 15:47] Enterprise Tools JIRA Robot
Andy Bang writes: 
In build
[8 Oct 2010 15:47] Enterprise Tools JIRA Robot
Marcos Palacios writes: 
Verified fixed in Monitor build
[4 Jan 2011 22:27] John Russell
Closed without doc changelog entry.