Bug 1465490 - pagure with mysql gives sqlalchemy error
pagure with mysql gives sqlalchemy error
Product: Fedora
Classification: Fedora
Component: pagure (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Pierre-YvesChibon
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-06-27 10:11 EDT by Paul Jakma
Modified: 2017-12-12 05:31 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-12 05:31:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Jakma 2017-06-27 10:11:09 EDT
Description of problem:

Trying to run createdb with MySQL gives an error about an incompatible 'client_encoding' argument.

Version-Release number of selected component (if applicable):

Both in the current F25 package, pagure-2.3.4-1.fc25.noarch, and the latest package on koji,  pagure-2.11-1.fc25.noarch.

How reproducible:


Steps to Reproduce:
1. Install pagure from RPM (bearing bug #1465475 in mind)
2. Specify DB_URL in pagure.cfg as something like: DB_URL='mysql://pagure:blah@localhost/pagure'
3. Run PAGURE_CONFIG=/etc/pagure/pagure.cfg  python /usr/share/pagure/pagure_createdb.py

Actual results:

$ PAGURE_CONFIG=/etc/pagure/pagure.cfg  python /usr/share/pagure/pagure_createdb.py
Traceback (most recent call last):
  File "/usr/share/pagure/pagure_createdb.py", line 7, in <module>
    from pagure import APP
  File "/usr/lib/python2.7/site-packages/pagure/__init__.py", line 173, in <module>
    SESSION = pagure.lib.create_session(APP.config['DB_URL'])
  File "/usr/lib/python2.7/site-packages/pagure/lib/__init__.py", line 111, in create_session
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/__init__.py", line 386, in create_engine
    return strategy.create(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/strategies.py", line 144, in create
TypeError: Invalid argument(s) 'client_encoding' sent to create_engine(), using configuration MySQLDialect_mysqldb/QueuePool/Engine.  Please check that the keyword arguments are appropriate for this combination of components.

Expected results:

Not sure what to expect, but I didn't expect an 'Invalid argument' in create_engine().

Additional info:
Comment 1 Fedora End Of Life 2017-11-16 13:51:33 EST
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 2 Fedora End Of Life 2017-12-12 05:31:23 EST
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.