MySQL Bugs: #54061: Multiple problems defining new Server Instance using SSH

Bug #54061	Multiple problems defining new Server Instance using SSH
Submitted:	28 May 2010 11:44	Modified:	26 Sep 2012 20:21
Reporter:	Geert Vanderkelen	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.21	OS:	MacOS (10.6.3)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
It's almost impossible to setup some SSH connection using the Server Instance. At one point is works, then it the dialog is unpredictable and uses wrong connection data.

How to repeat:
1) Create New Server Instance, and choose Remote Host. Enter the remote host name or IP address.

This step already has problems on MacOS X 10.6 with text going over the control boundaries as well as the drop down. See screenshot bug_screen1.png.

2) Next is the "Set the Database Values". We are choosing 'Standard TCP/IP over SSH'.

a) the host name we name in step (1) is the one we are connecting too. This should be the SSH Hostname, and not the MySQL Hostname.
b) The last line and text is again not visible.
c) SSH Key File should say: SSH Public Key File. (Also, most of the time, these files are in hidden directories like ~/.ssh, maybe good to mention it in some help because they are not accessible to Finder)
d) If you go back after filling all the correct information, and you do continue again, all data is lost. Annoyance.
e) Something I'm now repeating all time time, but when you entered all data correctly, it uses the root user of MySQL to make the SSH connection. See screenshot bug_screen3.png.

I haven't got further.

Screenshot 2

Attachment: bug_screen2.png (image/png, text), 81.92 KiB.

Screenshot 1

Attachment: bug_screen1.png (image/png, text), 28.94 KiB.

Screenshot 3

Attachment: bug_screen3.png (image/png, text), 21.55 KiB.

This is repeatable, thus setting it to verified using WorkBench 5.2.21 on MacOS X 10.6.3

Changed the DB connection params editor to use the provided host name more inteligently, across Connection methods

- changed SSK Key File caption
- fixed remote file browsing
- removed dummy password field

Geert, there have been several rounds of improvements of the wizards/dialogs since then. Can you try the latest release as see if that solves your problems?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Sorry, missed the Need Feedback on this bug. Still, a few issues:

In the 'Database Connection' step:
1) The 'help' next to the text controls in 'Database Connection' 'Parameters' when choosing '..over SSH' is not readable.
2) SSH hostname is set to 127.0.0.1, and MySQL Hostname set to server.example.org: that should be the reverse.
3) Still says 'SSH Key File', in help it says 'SSH public key file': label should be updated.
4) The file dialog for specifying the key file goes to the 'Macintosh HD', should be the the home of the user /Users/<currentuser>

When I don't want Remote Management, the 'Local Type' is set to FreeBSD.

And when I setup Remote Management, it complains about 'Configuration file did not contain section [], so a new one was added'. What's section []? The user I used actually has no rights to the my.cnf anyway.

Seems like some things were changed to the wizard screen, but still open for improvements.

Fixed as of the upcoming MySQL Workbench 5.2.44, and here's the changelog entry:

 On Mac OS X, the window to set up a "Standard TCP/IP over SSH" 
 connection contained incorrect descriptions. And the dialogue 
 now behaves more intelligently.

Thank you for the report.