Exception encountered during context initialization - cancelling refresh attempt: org.flywaydb.core.api.FlywayException: Found non-empty schema(s) "public" but no schema history table

[gterseglav]

When executing docker-compose up -d && docker-compose logs -f on tag 2.0.0 exception is thrown:

stellio-search-service  |  2023-02-05 18:27:33,442 [           main] WARN  onfigReactiveWebServerApplicationContext - refresh - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Found non-empty schema(s) "public" but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table.
stellio-search-service  |  2023-02-05 18:27:33,504 [           main] INFO  ConditionEvaluationReportLoggingListener - logMessage - 
stellio-search-service  | 
stellio-search-service  | Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
stellio-search-service  |  2023-02-05 18:27:33,536 [           main] ERROR o.s.boot.SpringApplication               - reportFailure - Application run failed
stellio-search-service  |  org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Found non-empty schema(s) "public" but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table.
stellio-search-service  | 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1804)
...
stellio-subscription-service exited with code 1

Same error repeats several times in the further output.

Steps to reproduce:

$ git checkout 2.0.0
HEAD is now at 2fb5f43d conf: update version to 2.0.0
$ git status
HEAD detached at 2.0.0
nothing to commit, working tree clean
$ docker-compose up -d && docker-compose logs -f

[gterseglav]

Error is not reproducable on the develop branch:

$ git checkout develop
$ git pull origin develop
$ git status
On branch develop
Your branch is up to date with 'origin/develop'.

nothing to commit, working tree clean
$ docker-compose up -d && docker-compose logs -f
...
stellio-search-service  |  2023-02-05 18:59:29,951 [ntainer#0-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - observations: partitions assigned: []
stellio-search-service  |  2023-02-05 18:59:30,004 [ntainer#1-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - search-iam: partitions assigned: [cim.iam-0]
stellio-search-service  |  2023-02-05 18:59:30,005 [ntainer#3-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - search_service_notification: partitions assigned: [cim.notification-0]
stellio-search-service  |  2023-02-05 18:59:30,005 [ntainer#2-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - search_service_subscription: partitions assigned: [cim.subscription-0]
stellio-subscription-service |  2023-02-05 18:59:30,006 [ntainer#0-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - context_subscription: partitions assigned: [cim.entity._CatchAll-0]

[gterseglav]

If docker-compose execution is done according to instructions on page https://stellio.readthedocs.io/en/latest/API_walkthrough.html, no error is thrown:

$ docker-compose -f docker-compose.yml up -d && docker-compose -f docker-compose.yml logs -f
...
stellio-search-service  |  2023-02-05 19:19:19,432 [ntainer#0-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - context_search: partitions assigned: [cim.entity._CatchAll-0]
stellio-search-service  |  2023-02-05 19:19:19,432 [ntainer#3-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - search-iam-replay: partitions assigned: [cim.iam.replay-0]
stellio-search-service  |  2023-02-05 19:19:19,432 [ntainer#1-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - search-iam: partitions assigned: [cim.iam-0]
stellio-search-service  |  2023-02-05 19:19:19,433 [ntainer#4-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - search_service_subscription: partitions assigned: [cim.subscription-0]
stellio-search-service  |  2023-02-05 19:19:19,434 [ntainer#5-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - search_service_notification: partitions assigned: [cim.notification-0]
stellio-search-service  |  2023-02-05 19:19:19,433 [ntainer#2-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - search-iam-rights: partitions assigned: [cim.iam.rights-0]
stellio-kafka           | [2023-02-05 19:19:19,865] INFO [GroupCoordinator 1]: Stabilized group context_subscription generation 3 (__consumer_offsets-7) with 1 members (kafka.coordinator.group.GroupCoordinator)
stellio-kafka           | [2023-02-05 19:19:19,880] INFO [GroupCoordinator 1]: Assignment received from leader consumer-context_subscription-1-c3f0ca24-41dd-40b6-8a81-b54466334a89 for group context_subscription for generation 3. The group has 1 members, 0 of which are static. (kafka.coordinator.group.GroupCoordinator)
stellio-subscription-service |  2023-02-05 19:19:19,917 [ntainer#0-0-C-1] INFO  o.s.k.l.KafkaMessageListenerContainer    - info - context_subscription: partitions assigned: [cim.entity._CatchAll-0]

Maybe instructions on README page on https://github.com/stellio-hub/stellio-context-broker could be synced with instructions on page https://stellio.readthedocs.io/en/latest/API_walkthrough.html.

[bobeal]

This is weird since the 2 commands are the same: docker-compose -f docker-compose.yml up -d and docker-compose -up -d do actually the same thing since docker-compose.yml is the default docker compose file searched by docker compose.

The problem you encountered has been fixed in b4a8fe2 and is normally fixed on develop and in the 2.0.0 version ...