jbauer opened 1 year ago
|
|||||
As a workaround I have manually restored the backup taken by the upgrade procedure and modified the configuration file to only contain the current primary postgres server. This must only be a temporary solution given that it disables database high availability. Then I restarted the OneDev docker container and the upgrade did restart and succeeded. |
|||||
OneDev changed state to 'Closed' 1 year ago
|
|||||
State changed as code fixing the issue is committed |
|||||
OneDev changed state to 'Released' 1 year ago
|
|||||
State changed as build #3266 is successful |
Type |
Bug
|
Priority |
Critical
|
Assignee | |
Affected Versions |
Not Found
|
Issue Votes (0)
During upgrade I get the exception below. In OneDev hibernate configuration file I take advantage of Postgres JDBC driver feature to support multiple servers in the connection string. This is useful if you have a primary / secondary postgres cluster because the Postgres JDBC driver will then automatically connect to the primary read/write server (
targetServerType=master
option in connection string). This used to work in OneDev 7.7.2 and now parsing of configuration file fails since the port of the first server contains the second server, see exception.Exception