I have deployed flowable-ui:latest docker image into AKS (v1.23.12) with our personal Postgres DB (v12.22) connection. Post deployment there is a error occuring with liquid.database changeloglock.
Kindly provide your support on the below error msg.
2023-01-11 10:06:40.574 INFO 1 — [ main] com.zaxxer.hikari.HikariDataSource : flowable-ui - Starting…
2023-01-11 10:06:41.764 INFO 1 — [ main] com.zaxxer.hikari.HikariDataSource : flowable-ui - Start completed.
2023-01-11 10:06:48.385 INFO 1 — [ main] o.f.a.s.SpringAppEngineConfiguration : Executing configure() of class org.flowable.engine.spring.configurator.SpringProcessEngineConfigurator (priority:50000)
2023-01-11 10:06:49.389 INFO 1 — [ main] o.f.engine.impl.ProcessEngineImpl : ProcessEngine default created
2023-01-11 10:06:49.485 INFO 1 — [ main] o.f.e.impl.cmd.ValidateV5EntitiesCmd : Total of v5 deployments found: 0
2023-01-11 10:06:49.496 INFO 1 — [ main] o.f.a.s.SpringAppEngineConfiguration : Executing configure() of class org.flowable.eventregistry.spring.configurator.SpringEventRegistryConfigurator (priority:100000)
2023-01-11 10:06:50.371 INFO 1 — [ main] liquibase.servicelocator : Cannot load service: liquibase.license.LicenseService: Provider liquibase.license.pro.DaticalTrueLicenseService could not be instantiated
2023-01-11 10:06:50.761 INFO 1 — [ main] liquibase.database : Set default schema name to public
2023-01-11 10:06:50.978 INFO 1 — [ main] liquibase.lockservice : Waiting for changelog lock…
2023-01-11 10:07:00.998 INFO 1 — [ main] liquibase.lockservice : Waiting for changelog lock…
2023-01-11 10:07:11.009 INFO 1 — [ main] liquibase.lockservice : Waiting for changelog lock…
Could this be the result of an incomplete / failed initial deployment or start up?
You can try and remove the lock by updating the corresponding *_databasechangelock tables.
I have already tried with the option. But post changing the lock in corresponding table once the k8s pod restarted it again taking the value as “true”.
Is there any AKS compatibility with flowable-ui docker image ?
There are no issues with the Flowable UI image for running on a AKS cluster.
This is most probably caused by the way that it is deployed.
Are you using your own Kubernetes configurations? Or are you using the Flowable Helm chart?
I am using this following yml. Here I have mentioned the DB connection with our own Azure PaaS Postgres Flexible server v 12.22.
I am just applying this yml at AKS via CLI. The same yml is running on another AKS cluster. Only it is throwing the error for a particular AKS Cluster.
Kindly verify the yml and let me know if anything needs to be changed.
No, there is no particular for using helm chart. I can use that as well for installing flowable-ui. Could you please help me with the helm chart link for installing flowable-ui only.
Could you please let me know if we can use our own Azure Postgres PAAS Database connection (v12.22) while installing flowable-ui using Helm 6.8.0 ? We do not want to install another postgres on AKS.
Also kindly let me know if we can set the LoadBalancer spec-type for flowable service at the time of helm installation. We do not want to host it via ingress host DNS.