Mailinglist Archive: kubic-bugs (110 mails)

< Previous Next >
[kubic-bugs] [Bug 1087891] no python3 mysql module available which works with salt.
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 13 Apr 2018 07:55:21 +0000
  • Message-id: <>

Maximilian Meister <mmeister@xxxxxxxx> changed:

What |Removed |Added
CC| |kmacinnes@xxxxxxxx
Flags| |needinfo?(kmacinnes@xxxxxxx
| |m)

--- Comment #41 from Maximilian Meister <mmeister@xxxxxxxx> ---
(In reply to Thorsten Kukuk from comment #39)
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
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 ->

because we mount the api.conf into the salt-master container for some reason ->

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

You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >