We had a problem when the nova connection string included parameters on the
query string like charset encoding.
Note that the connection string necessarly needs to be RFC1738 compliant as
per Sqlalchemy rules, so it's totally safe to just unquote what the SQLA
helper method gives us as a result.
Also removed a tested connection string since it wasn't RFC1738 compatible.
Change-Id: I45fe9b92e8d93a0099d33bb0070e9d4e540595ac
Closes-Bug: #1696001
(cherry picked from commit 9a33092fa9b0c65b37b9fdc860f5a571908d7a69)
Reviewed: https:/ /review. openstack. org/471790 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=6041572a4c9 5428f6b13a8d756 9090b315a3abd1
Committed: https:/
Submitter: Jenkins
Branch: stable/ocata
commit 6041572a4c95428 f6b13a8d7569090 b315a3abd1
Author: Sylvain Bauza <email address hidden>
Date: Tue Jun 6 23:28:59 2017 +0200
Fix cell0 naming when QS params on the connection
We had a problem when the nova connection string included parameters on the
query string like charset encoding.
Note that the connection string necessarly needs to be RFC1738 compliant as
per Sqlalchemy rules, so it's totally safe to just unquote what the SQLA
helper method gives us as a result.
Also removed a tested connection string since it wasn't RFC1738 compatible.
Change-Id: I45fe9b92e8d93a 0099d33bb0070e9 d4e540595ac b37b9fdc860f5a5 71908d7a69)
Closes-Bug: #1696001
(cherry picked from commit 9a33092fa9b0c65