[kubic-bugs] [Bug 1087891] New: Velum: Unable to find any pending nodes
http://bugzilla.opensuse.org/show_bug.cgi?id=1087891 Bug ID: 1087891 Summary: Velum: Unable to find any pending nodes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Containers Assignee: containers-bugowner@suse.de Reporter: rbrown@suse.com QA Contact: qa-bugs@suse.de CC: kubic-bugs@opensuse.org Found By: --- Blocker: --- On current Kubic installations Velum starts, but when bootstrapping the cluster no pending nodes are ever found Steps to Reproduce: Install Admin Node Wait for Velum to Start Create account and login Use autoyast URL in bootstrap wizard to install 3x nodes via the network Wait for all 3 nodes to be installed Click Next (to the Node selection screen) Wait Expectation: 3 Nodes should appear on the Velum node selection screen Actual results: Node selection screen remains empty -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1087891 http://bugzilla.opensuse.org/show_bug.cgi?id=1087891#c1 Maximilian Meister <mmeister@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmeister@suse.com --- Comment #1 from Maximilian Meister <mmeister@suse.com> --- it seems to be "only" a connection problem between velum and the salt-api which is also shown via a flash message in /setup/discovery because, after booting node(s) via autoyast, the keys correctly appear to the salt-master in the state unaccepted
linux-g3qd:~ # docker exec -it $(docker ps | grep "salt-master_velum" | awk '{print $1}') salt-key Accepted Keys: admin ca Denied Keys: Unaccepted Keys: 3f4ecbb2c3474654bed2bacf786e2c22 7dccc505586c4c2c92f2533097f6b931 Rejected Keys:
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1087891 http://bugzilla.opensuse.org/show_bug.cgi?id=1087891#c2 Rafael Fernández López <rfernandezlopez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rfernandezlopez@suse.com --- Comment #2 from Rafael Fernández López <rfernandezlopez@suse.com> --- It looks like the mysql python library is not properly loaded by salt: https://build.opensuse.org/package/view_file/devel:CaaSP:kubic-container/kub... This is including `python-PyMySQL`, whereas we were including `python-MySQL-python` in IBS. Looks like salt just tries to load `MySQLdb`: https://github.com/saltstack/salt/blob/2016.11/salt/returners/mysql.py#L157-... Looks like PyMySQL has some compatibility layer with MySQLdb, but it doesn't export `MySQLdb` in any case so salt cannot load it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1087891 http://bugzilla.opensuse.org/show_bug.cgi?id=1087891#c3 --- Comment #3 from Maximilian Meister <mmeister@suse.com> --- (In reply to Rafael Fernández López from comment #2)
It looks like the mysql python library is not properly loaded by salt:
https://build.opensuse.org/package/view_file/devel:CaaSP:kubic-container/ kubic-salt-master-image/kubic-salt-master-image.kiwi?expand=1
This is including `python-PyMySQL`, whereas we were including `python-MySQL-python` in IBS. Looks like salt just tries to load `MySQLdb`: https://github.com/saltstack/salt/blob/2016.11/salt/returners/mysql.py#L157- L173
Looks like PyMySQL has some compatibility layer with MySQLdb, but it doesn't export `MySQLdb` in any case so salt cannot load it.
thanks for looking into it. i wonder why we use such an old and out of maintenance library, the (probably literally) last release was Jan 2014 any idea what we need to do if we'd like to port our salt master to PyMySQL? would we need to patch the salt version, or is that something we need to propose to upstream salt? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1087891 http://bugzilla.opensuse.org/show_bug.cgi?id=1087891#c18 --- Comment #18 from Maximilian Meister <mmeister@suse.com> --- (In reply to Thorsten Kukuk from comment #17)
I build a new kubic-salt-master-image with it, and still get the error messages: 08:42:06,273 [ERROR ] Could not store return for event(s) - returner 'mysql.event_return' not found. 08:42:06,277 [ERROR ] Could not store return for event(s) - returner 'mysql.event_return' not found.
thanks for testing, have you installed PyMySQL? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1087891 http://bugzilla.opensuse.org/show_bug.cgi?id=1087891#c19 --- Comment #19 from Maximilian Meister <mmeister@suse.com> --- Thorsten, i also found out there are some more places upstream besides returners and modules that didnt have the drop in replacement mechanism yet. e.g. salt/pillar/mysql.py or salt/auth/mysql.py i updated the patch in https://build.opensuse.org/package/show/home:m_meister:branches:systemsmanag... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1087891 http://bugzilla.opensuse.org/show_bug.cgi?id=1087891#c22 --- Comment #22 from Klaus Kämpf <kkaempf@suse.com> --- (In reply to Maximilian Meister from comment #19)
Thorsten, i also found out there are some more places upstream besides returners and modules that didnt have the drop in replacement mechanism yet. e.g. salt/pillar/mysql.py or salt/auth/mysql.py
i updated the patch in https://build.opensuse.org/package/show/home:m_meister:branches: systemsmanagement:saltstack/salt
Awaiting your pull request at https://github.com/openSUSE/salt ;-) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com