[kubic-bugs] [Bug 1087891] no python3 mysql module available which works with salt.
http://bugzilla.suse.com/show_bug.cgi?id=1087891
http://bugzilla.suse.com/show_bug.cgi?id=1087891#c41
Maximilian Meister
I fixed the setup scripts, container image names and tags and replaced all python2 with python3 code, so there are no visible errors anymore in the logs. Except salt-master, where I still get:
07:10:32,109 [INFO ] Using default for mysql port 07:10:32,109 [INFO ] Using default for mysql ssl_ca 07:10:32,110 [INFO ] Using default for mysql ssl_cert 07:10:32,110 [INFO ] Using default for mysql ssl_key 07:10:32,111 [ERROR ] Could not store events - returner 'mysql.event_return' raised exception: (2003, "Can't connect to MySQL server on 'localhost' ([Errno 111] Connection refused)")
Don't know who prints the "INFO", the ERROR is comming from PyMySQL. Could it be, that we need to provide the informations for mysql in another way?
the INFO logs most likely come from salt-api -> https://github.com/kubic-project/salt/blob/master/config/master.d/50-api.con... because we mount the api.conf into the salt-master container for some reason -> https://github.com/kubic-project/caasp-container-manifests/blob/master/manif... and those configs together lead to this strange behaviour that salt-api logs to salt-master, @kiall did i get that right? i wonder if we can just drop this mount -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com