conductor-oss / conductor-oss/conductor

[BUG] flyway.postgresql.transactional.lock didn't find in flyway

Open
#123 5 comments 2 reactions 1 assignee Claimed by @jeffbulltech View on GitHub
bug help wanted question
Dominant language
Java
Stars
32.2k
Forks
1k
Avg merge
2d 5h
Merged PRs (30d)
41

Description

**Describe the bug**
After getting a new version of conductor, I've got an error while spring boot app is starting.

As far as I researched, flyway does not find prop `flyway.postgresql.transactional.lock`

**Details**
Conductor version:
implementation "org.conductoross:conductor-common:3.18.0"
implementation "org.conductoross:conductor-postgres-persistence:3.18.0"
implementation "org.conductoross:conductor-core:3.18.0"
implementation "org.conductoross:conductor-rest:3.18.0"

**To Reproduce**
Steps to reproduce the behavior:
1. start Spring boot app
4. See error in logs:
`Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayForPrimaryDb' defined in class path resource [com/netflix/conductor/postgres/config/PostgresConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.flywaydb.core.Flyway]: Factory method 'flywayForPrimaryDb' threw exception; nested exception is org.flywaydb.core.api.FlywayException: Unknown configuration property: flyway.postgresql.transactional.lock
`

**Expected behavior**
Spring boot app with conductor runs as expected

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.