conductor icon indicating copy to clipboard operation
conductor copied to clipboard
verified publisher icon Netflix

docker-compose up server failed to execute workflow because of "XContentType" class is not found

Open dingliu1 opened this issue 2 years ago • 13 comments

Describe the bug docker-compose up server failed to execute workflow because of "XContentType" class is not found.

Details Conductor version: v3.15.0 or the latest Persistence implementation: Cassandra, Postgres, MySQL, Dynomite etc: Postgres Queue implementation: Postgres, MySQL, Dynoqueues etc Lock: Redis or Zookeeper? Workflow definition: Task definition: Event handler definition:

To Reproduce Steps to reproduce the behavior:

  1. Go to conductor-3.15.0\docker or the latest version\docker
  2. Execute below command docker-compose -f docker-compose-postgres.yaml build docker-compose -f docker-compose-postgres.yaml up
  3. Create some sample workflow definition and execute "Definition" -> "New Workflow Definition" -> set sample "uri" e.g. uri": "https://datausa.io/api/data?drilldowns=Nation&measures=Population",drilldowns=Nation&measures=Population", Save the definition -> Go to "Workbench" -> choose just created workflow name -> click execute Now the conductor server logs report: "org.springframework.web.util.NestedServletException: Handler dispatch failed; nested exception is java.lang.NoClassDefFoundError: org/elasticsearch/common/xcontent/XContentType"
  4. The root cause seems that: The Dockerfile packaged "conductor-server.jar\BOOT-INF\lib" I can see elasticsearch-x-content-7.17.13.jar, the "XContentType" class is re-packaged. https://stackoverflow.com/questions/72428790/xcontenttype-is-removed-from-elasticsearch-ver-7-17-3

Expected behavior docker-compose inside docker/server folder should work at any time

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

dingliu1 avatar Nov 28 '23 13:11 dingliu1

Can confirm we're facing the exact same issue.

Nostras avatar Nov 28 '23 16:11 Nostras

Same issue

gforce81 avatar Nov 29 '23 03:11 gforce81

Strangely the same issue has surfaced on our side too

kyandaks avatar Nov 29 '23 15:11 kyandaks

Me too. Is there any workaround?

tianxie avatar Dec 01 '23 10:12 tianxie

Me too. Is there any workaround?

Seems to be due to some changes in the conductor-community repo. A temporary work-around could be to use an older commit of the conductor community repo in the docker/server/Dockerfile.

solomonmetta avatar Dec 02 '23 17:12 solomonmetta

same here !

nadaHilal1 avatar Dec 02 '23 20:12 nadaHilal1

any update regarding this issue, is this fixed ?please reply

gajendrangnanasekaran avatar Dec 03 '23 09:12 gajendrangnanasekaran

we also facing the same issue exactly

gajendrangnanasekaran avatar Dec 03 '23 09:12 gajendrangnanasekaran

Hi @gajendrangnanasekaran , The issue is fixed in PR https://github.com/Netflix/conductor-community/pull/303. It will be released in the next release.

manan164 avatar Dec 05 '23 08:12 manan164

Specifically, add RUN git reset --hard 7e1b9122477ae0647b61d1206e49be87f0ae65d1 to line 39 in the Dockerfile https://github.com/Netflix/conductor/blob/main/docker/server/Dockerfile until v1r3n has made a new community release.

Nostras avatar Dec 05 '23 09:12 Nostras

Thanks lot when it will get released?

gajendrangnanasekaran avatar Dec 05 '23 16:12 gajendrangnanasekaran

Thanks lot when it will get released?

Just apply my fix for now, the community version can then release when they're ready.

Nostras avatar Dec 05 '23 16:12 Nostras

Now its working fine as per @Nostras inputs, thanks lot @Nostras and @manan164

gajendrangnanasekaran avatar Dec 07 '23 10:12 gajendrangnanasekaran