Bug 1829932

Summary: Can't determine which FROM clause to join from
Product: Red Hat Enterprise Linux 8 Reporter: Joel Capitao <jcapitao>
Component: python36-3.6-moduleAssignee: Python Maintainers <python-maint>
Status: CLOSED ERRATA QA Contact: Lukáš Zachar <lzachar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: cstratak, pviktori
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python36-3.6-8030020200515150628.24f1489c Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 03:09:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joel Capitao 2020-04-30 15:28:40 UTC 
Description of problem:
At RDO, while packaging neutron-dynamic-routing [1] for Ussuri release, we hit an issue during the %check step. The version 1.3.2 of the module SQLAlchemy (currently the version provided by CentOS8 AppStream) is responsible of the issue.
It has been fixed with this commit [2] since release 1.3.3.



[1] https://review.rdoproject.org/r/#/c/26998/
[2] https://github.com/sqlalchemy/sqlalchemy/commit/25a42e93f4ef5ce1a9f9c23fbcdea3e21a7b3f1a

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


How reproducible:
Always


Steps to Reproduce:
git clone https://git.openstack.org/openstack/neutron-dynamic-routing
cd neutron-dynamic-routing/
tox -e py37
.tox/py37/bin/pip install 1.3.2
tox -e py37

Actual results:
tox job py37 fail with error below:
sqlalchemy.exc.InvalidRequestError: Can't determine which FROM clause to join from, there are multiple FROMS which can join to this entity. Try adding an explicit



Expected results:
tox job pass successfully


Additional info:
Comment 3 Petr Viktorin (pviktori) 2020-05-20 12:15:03 UTC 
As a regression fix, this doesn't need a docs update.
Comment 8 errata-xmlrpc 2020-11-04 03:09:36 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (python36:3.6 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4704