April 2018 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[kubic-bugs] [Bug 1087891] no python3 mysql module available which works with salt.
by bugzilla_noreply＠novell.com 10 Apr '18

10 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 http://bugzilla.suse.com/show_bug.cgi?id=1087891#c31 --- Comment #31 from Bo Maryniuk <bmaryniuk(a)suse.com> --- (In reply to Maximilian Meister from comment #30) > this is not an issue anymore, the issue is: > > > 08:50:08,200 [ERROR ] Could not store events - returner > > 'mysql.event_return' raised exception: module 'pymysql.connections' has no > > attribute 'OperationalError' Sure. It is moved to pymysql.err.OperationalError class. Like we were talking before: it is not 100% compatible and some refactoring is still needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1087891] no python3 mysql module available which works with salt.
by bugzilla_noreply＠novell.com 10 Apr '18

10 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 http://bugzilla.suse.com/show_bug.cgi?id=1087891#c30 --- Comment #30 from Maximilian Meister <mmeister(a)suse.com> --- (In reply to Bo Maryniuk from comment #29) > Well, it says as it says: > > 15:33:51,057 [ERROR ] Exception raised when processing __virtual__ > function for salt.loaded.int.returner.mysql. Module will not be loaded: name > 'HAS_MYSQL' is not defined > > Which means you have somewhere HAS_MYSQL variable that you're accessing like > "if HAS_MYSQL is True" or something like that, but it is not defined prior... this is not an issue anymore, the issue is: > 08:50:08,200 [ERROR ] Could not store events - returner > 'mysql.event_return' raised exception: module 'pymysql.connections' has no > attribute 'OperationalError' the PR upstream [0] has also got some more reviews and changed again, but the issue should still be the same [0] https://github.com/saltstack/salt/pull/46890 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1087891] no python3 mysql module available which works with salt.
by bugzilla_noreply＠novell.com 10 Apr '18

10 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 http://bugzilla.suse.com/show_bug.cgi?id=1087891#c29 Bo Maryniuk <bmaryniuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bmaryniuk(a)suse.com --- Comment #29 from Bo Maryniuk <bmaryniuk(a)suse.com> --- Well, it says as it says: 15:33:51,057 [ERROR ] Exception raised when processing __virtual__ function for salt.loaded.int.returner.mysql. Module will not be loaded: name 'HAS_MYSQL' is not defined Which means you have somewhere HAS_MYSQL variable that you're accessing like "if HAS_MYSQL is True" or something like that, but it is not defined prior... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1087891] no python3 mysql module available which works with salt.
by bugzilla_noreply＠novell.com 10 Apr '18

10 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Velum: Unable to find any |no python3 mysql module |pending nodes |available which works with | |salt. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1087891] Velum: Unable to find any pending nodes
by bugzilla_noreply＠novell.com 10 Apr '18

10 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 http://bugzilla.suse.com/show_bug.cgi?id=1087891#c28 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent Assignee|mmeister(a)suse.com |salt-maintainers(a)suse.de --- Comment #28 from Thorsten Kukuk <kukuk(a)suse.com> --- Re-assigning to salt-maintainers, this is blocking Kubic and CaaSP4 development and goes behind our knowledge. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1088304] New: DVD offer upgrade option
by bugzilla_noreply＠novell.com 09 Apr '18

09 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1088304 Bug ID: 1088304 Summary: DVD offer upgrade option Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The Kubic DVD offers an upgrade option, but this does not exist for Kubic/MicroOS. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1087891] Velum: Unable to find any pending nodes
by bugzilla_noreply＠novell.com 09 Apr '18

09 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 http://bugzilla.suse.com/show_bug.cgi?id=1087891#c27 --- Comment #27 from Klaus Kämpf <kkaempf(a)suse.com> --- (In reply to Maximilian Meister from comment #24) > > klaus, can i also wait for https://github.com/saltstack/salt/pull/46890 to > get merged and backport it to the openSUSE fork This won't happen automagically ;-) If you want it in *our* Salt, create a pull request. >, or what's the usual > workflow? > https://github.com/openSUSE/salt/wiki Reach out to #saltstack on irc.suse.de and ask for help ! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1087891] Velum: Unable to find any pending nodes
by bugzilla_noreply＠novell.com 09 Apr '18

09 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 http://bugzilla.suse.com/show_bug.cgi?id=1087891#c26 --- Comment #26 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Thorsten Kukuk from comment #25) > I will test with 0.8 now. PyMySQL 0.8.0 shows the same error :( -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1087891] Velum: Unable to find any pending nodes
by bugzilla_noreply＠novell.com 09 Apr '18

09 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 http://bugzilla.suse.com/show_bug.cgi?id=1087891#c25 --- Comment #25 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Maximilian Meister from comment #24) > thorsten, can you check which version of PyMySQL is installed? the > OperationalError should get imported here: > https://github.com/PyMySQL/PyMySQL/blob/master/pymysql/connections.py#L25 > > if that doesn't work maybe we need to import the err.py explicitly... but i > am no python expert, to me it looks like it should be loaded already We have 0.7.11, the newest is 0.8, and it looks like this got added to 0.8. I will test with 0.8 now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1087891] Velum: Unable to find any pending nodes
by bugzilla_noreply＠novell.com 09 Apr '18

09 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 http://bugzilla.suse.com/show_bug.cgi?id=1087891#c24 --- Comment #24 from Maximilian Meister <mmeister(a)suse.com> --- (In reply to Klaus Kämpf from comment #22) > (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 ;-) klaus, can i also wait for https://github.com/saltstack/salt/pull/46890 to get merged and backport it to the openSUSE fork, or what's the usual workflow? (In reply to Thorsten Kukuk from comment #23) > Update: I have fixed the patch so that PyMySQL will be loaded now, but of > course the interface is not 100% compatible: > > 08:50:08,200 [ERROR ] Could not store events - returner > 'mysql.event_return' raised exception: module 'pymysql.connections' has no > attribute 'OperationalError' > 08:50:14,489 [CRITICAL] Specified ext_pillar interface velum is unavailable thorsten, can you check which version of PyMySQL is installed? the OperationalError should get imported here: https://github.com/PyMySQL/PyMySQL/blob/master/pymysql/connections.py#L25 if that doesn't work maybe we need to import the err.py explicitly... but i am no python expert, to me it looks like it should be loaded already i have also changed again the patch after some upstream feedback to fix linting issues (the undefined HAS_MYSQLDB and an import statement) -- You are receiving this mail because: You are on the CC list for the bug.

1 0