MySQL Bugs: #71648: MySQL Workbecn manage server connections->new

Bug #71648	MySQL Workbecn manage server connections->new
Submitted:	10 Feb 2014 8:44	Modified:	10 Sep 2014 4:31
Reporter:	Jack Sitnikov	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.0.9	OS:	Linux (Fedora 20 x86_64)
Assigned to:		CPU Architecture:	Any

Description:
After http://bugs.mysql.com/bug.php?id=71646 I tried to install Mysql Workbench i686 version,before I remove x86_64 version and cleared  ~/.mysql dir.
Here I got more information, interface started and I tried create new connection, but It crash. 
I ran with params  -v --log-level=debug3 and watch I saw:
grt]: Trying to load module '/usr/lib/mysql-workbench/modules/wb_admin_grt.py' (python)
12:26:44 [DB1][            grt]: Traceback (most recent call last):
12:26:44 [DB1][            grt]:   File "/usr/lib/mysql-workbench/modules/wb_admin_ssh.py", line 44, in <module>
12:26:44 [DB1][            grt]:     import paramiko
12:26:44 [DB1][            grt]:   File "/usr/lib/python2.7/site-packages/paramiko/__init__.py", line 62, in <module>
12:26:44 [DB1][            grt]:     from transport import SecurityOptions, Transport
12:26:44 [DB1][            grt]:   File "/usr/lib/python2.7/site-packages/paramiko/transport.py", line 33, in <module>
12:26:44 [DB1][            grt]:     from paramiko import util
12:26:44 [DB1][            grt]:   File "/usr/lib/python2.7/site-packages/paramiko/util.py", line 33, in <module>
12:26:44 [DB1][            grt]:     from paramiko.common import *
12:26:44 [DB1][            grt]:   File "/usr/lib/python2.7/site-packages/paramiko/common.py", line 98, in <module>
12:26:44 [DB1][            grt]:     from Crypto import Random
12:26:44 [DB1][            grt]: ImportError: No module named Crypto
12:26:44 [DB1][            grt]: Warning! Can't use connect with timeout in paramiko None
12:26:44 [DB1][            grt]: Traceback (most recent call last):
12:26:44 [DB1][            grt]:   File "/usr/lib/mysql-workbench/modules/wb_admin_grt.py", line 26, in <module>
12:26:44 [DB1][            grt]:     import wb_admin_main
12:26:44 [DB1][            grt]:   File "/usr/lib/mysql-workbench/modules/wb_admin_main.py", line 35, in <module>
12:26:44 [DB1][            grt]:     from wb_admin_configuration_startup import WbAdminConfigurationStartup
12:26:44 [DB1][            grt]:   File "/usr/lib/mysql-workbench/modules/wb_admin_configuration_startup.py", line 25, in <module>
12:26:44 [DB1][            grt]:     from wb_log_reader import ErrorLogFileReader
12:26:44 [DB1][            grt]:   File "/usr/lib/mysql-workbench/modules/wb_log_reader.py", line 100, in <module>
12:26:44 [DB1][            grt]:     from wb_server_management import SudoTailInputFile, LocalInputFile, SFTPInputFile
12:26:44 [DB1][            grt]:   File "/usr/lib/mysql-workbench/modules/wb_server_management.py", line 36, in <module>
12:26:44 [DB1][            grt]:     from wb_admin_ssh import WbAdminSSH, ConnectionError
12:26:44 [DB1][            grt]:   File "/usr/lib/mysql-workbench/modules/wb_admin_ssh.py", line 136, in <module>
12:26:44 [DB1][            grt]:     log_warning(_this_file, 'Cannot use connect with timeout in paramiko version %s\n' % paramiko.__version__)
12:26:44 [DB1][            grt]: AttributeError: 'NoneType' object has no attribute '__version__'
12:26:44 [ERR][            grt]: Failed loading module '/usr/lib/mysql-workbench/modules/wb_admin_grt.py' (python)

uname -r
3.12.9-301.fc20.x86_64

How to repeat:
Install from site i686 verion and run with -v --log-level=debug3

Can you see if you have python-paramiko installed?

I saw error message and check and tried reinstall paramiko and python-crypto.
rpm -qa | grep paramiko 
python-paramiko-1.10.1-2.fc20.noarch

What version of python-crypto do you have installed? Can you paste the output of rpm -ql python-crypto?

rpm -ql python-crypto

Attachment: rpm-ql.txt (text/plain), 27.46 KiB.

Python-crypto package version is python-crypto-2.6.1-1.fc20.x86_64

This problem is caused by the use of a 32bit package in a 64bit system. 
Hopefully, the reason that prevented the use of native 64bit packages is already resolved, so using the 64bit Workbench is the recommended solution for this.