Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE] connectors is unhealthy when identity is disabled #2302

Open
Tracked by #1
jessesimpson36 opened this issue Sep 5, 2024 · 0 comments
Open
Tracked by #1

[ISSUE] connectors is unhealthy when identity is disabled #2302

jessesimpson36 opened this issue Sep 5, 2024 · 0 comments
Labels
good first issue Good for newcomers kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between platform/aws Issues related to AWS platform/gcp Issues related to GCP

Comments

@jessesimpson36
Copy link
Contributor

jessesimpson36 commented Sep 5, 2024

Describe the issue:

When deploying without identity enabled, connectors fails with the below stacktrace.

I found this in response to testing for this problem but inside the helm repo instead of docker-compose this time.

Actual behavior:

connectors pod log:

2024-09-05T16:30:39.839Z ERROR 1 --- [   scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter    : Failed to import process definitions

java.lang.UnsupportedOperationException: Unable to determine authentication
	at io.camunda.common.auth.DefaultNoopAuthentication.getTokenHeader(DefaultNoopAuthentication.java:31)
	at io.camunda.common.http.DefaultHttpClient.retrieveToken(DefaultHttpClient.java:207)
	at io.camunda.common.http.DefaultHttpClient.post(DefaultHttpClient.java:148)
	at io.camunda.operate.CamundaOperateClient.searchProcessDefinitionResults(CamundaOperateClient.java:46)
	at io.camunda.connector.runtime.inbound.importer.ProcessDefinitionSearch.query(ProcessDefinitionSearch.java:72)
	at io.camunda.connector.runtime.inbound.importer.ProcessDefinitionImporter.scheduleImport(ProcessDefinitionImporter.java:55)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)
	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
	at org.springframework.scheduling.support.ScheduledMethodRunnable.runInternal(ScheduledMethodRunnable.java:130)
	at org.springframework.scheduling.support.ScheduledMethodRunnable.lambda$run$2(ScheduledMethodRunnable.java:124)
	at io.micrometer.observation.Observation.observe(Observation.java:499)
	at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:124)
	at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

The following is my values.yaml that I overlay ontop of my main values.yaml when testing for identity being disabled:

global:
  identity:
    auth:
      enabled: false

identity:
  enabled: false
  keycloak:
    enabled: false
    postgresql:
      enabled: false

zeebe-gateway:
  env:
    - name: ZEEBE_GATEWAY_CLUSTER_SECURITY_AUTHENTICATION_MODE
      value: none

webModeler:
  enabled: false

Expected behavior:

How to reproduce:

Logs:

Environment:

connectors-unhealthy-values.yaml.txt

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

  • Platform:
  • Helm CLI version:
  • Chart version: 10.3.2 and 9.3.9
  • Values file:
@jessesimpson36 jessesimpson36 added the kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between label Sep 5, 2024
@github-actions github-actions bot added platform/aws Issues related to AWS platform/gcp Issues related to GCP labels Sep 5, 2024
@aabouzaid aabouzaid added the good first issue Good for newcomers label Sep 9, 2024
@aabouzaid aabouzaid added this to the 8.7 Release Cycle milestone Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between platform/aws Issues related to AWS platform/gcp Issues related to GCP
Projects
None yet
Development

No branches or pull requests

2 participants