Tests fails on PostgreSQL 14
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.db |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
From a recent gate test:
=======
Failed 1 tests - output below:
=======
oslo_db.
-------
Captured traceback:
~~~~~~~~~~~~~~~~~~~
Traceback (most recent call last):
File "/home/
self.
File "/home/
self.
File "/home/
self.
File "/home/
self.
File "/home/
raise mismatch_error
testtools.
reference = '''\
fatal: database "non_existent_
'''
actual = '''\
connection to server at "localhost" (::1), port 5432 failed: fatal: database "non_existent_
'''
Changed in oslo.db: | |
status: | New → In Progress |
Reviewed: https:/ /review. opendev. org/c/openstack /oslo.db/ +/856836 /opendev. org/openstack/ oslo.db/ commit/ 437a19703d63801 997f2ccece516a2 790d438cee
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 437a19703d63801 997f2ccece516a2 790d438cee
Author: Stephen Finucane <email address hidden>
Date: Fri Sep 9 17:34:40 2022 +0100
tests: Fix compatibility with PostgreSQL 14+
It seems postgres-client has changed the format of error messages.
Previously we saw messages like:
fatal: database "non_existent_ database" does not exist
These are now prefixed. For example:
connection to server at "localhost" (::1), port 5432 failed: fatal: database" does not exist
database "non_existent_
You can see this in the docs. Compare the "Client Connection Problems"
section for Postgres 13 [1] to Postgres 14 [2].
[1] https:/ /www.postgresql .org/docs/ 13/server- start.html /www.postgresql .org/docs/ 14/server- start.html
[2] https:/
Change-Id: Id2c8eec202d128 d142b8a8a8f904f cc14b6f52d7
Signed-off-by: Stephen Finucane <email address hidden>
Closes-bug: #1989208