EDC 0.7.3 → DEBUG Message DataPlaneInstance is now in state AVAILABLE → Every Minute on end

[jerzy-wachowiak]

During deployment data-plane is restarted

$ kc get po -w
NAME                                                              READY   STATUS    RESTARTS   AGE
dtr050-digital-twin-registry-5bcc797b6b-pg6dz                     1/1     Running   0          177m
edc073-tractusx-connector-azure-vault-controlplane-7f77b74tn4qh   0/1     Running   0          1s
edc073-tractusx-connector-azure-vault-dataplane-f9cd7c7d4-txmpk   0/1     Running   0          1s
edc073-tractusx-connector-azure-vault-controlplane-7f77b74tn4qh   1/1     Running   0          40s
edc073-tractusx-connector-azure-vault-dataplane-f9cd7c7d4-txmpk   0/1     Running   1 (1s ago)   91s
edc073-tractusx-connector-azure-vault-dataplane-f9cd7c7d4-txmpk   1/1     Running   1 (40s ago)   2m10s

due to

Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  2m36s                default-scheduler  Successfully assigned bpnl000000000nph-stg44/edc073-tractusx-connector-azure-vault-dataplane-f9cd7c7d4-txmpk to aks-agentpool-31089915-vmss00000g
  Normal   Pulled     67s (x2 over 2m37s)  kubelet            Container image "tractusx/edc-dataplane-azure-vault:0.7.3" already present on machine
  Normal   Created    67s (x2 over 2m37s)  kubelet            Created container tractusx-connector-azure-vault
  Warning  Unhealthy  67s (x8 over 117s)   kubelet            Readiness probe failed: HTTP probe failed with statuscode: 503
  Warning  Unhealthy  67s (x6 over 117s)   kubelet            Liveness probe failed: HTTP probe failed with statuscode: 503
  Normal   Killing    67s                  kubelet            Container tractusx-connector-azure-vault failed liveness probe, will be restarted
  Normal   Started    66s (x2 over 2m36s)  kubelet            Started container tractusx-connector-azure-vault

after this Debug logs are thrown every minute on end

INFO 2024-08-02T12:03:01.613766671 Runtime edc073-tractusx-connector-azure-vault-controlplane ready
DEBUG 2024-08-02T12:04:45.236498637 [DataPlaneSelectorManagerImpl] DataPlaneInstance edc073-tractusx-connector-azure-vault-dataplane is now in state UNAVAILABLE
DEBUG 2024-08-02T12:05:45.324061335 [DataPlaneSelectorManagerImpl] DataPlaneInstance edc073-tractusx-connector-azure-vault-dataplane is now in state AVAILABLE
DEBUG 2024-08-02T12:06:45.38564909 [DataPlaneSelectorManagerImpl] DataPlaneInstance edc073-tractusx-connector-azure-vault-dataplane is now in state AVAILABLE
DEBUG 2024-08-02T12:07:45.440055655 [DataPlaneSelectorManagerImpl] DataPlaneInstance edc073-tractusx-connector-azure-vault-dataplane is now in state AVAILABLE
DEBUG 2024-08-02T12:08:45.489983729 [DataPlaneSelectorManagerImpl] DataPlaneInstance edc073-tractusx-connector-azure-vault-dataplane is now in state AVAILABLE
DEBUG 2024-08-02T12:09:45.534195069 [DataPlaneSelectorManagerImpl] DataPlaneInstance edc073-tractusx-connector-azure-vault-dataplane is now in state AVAILABLE
DEBUG 2024-08-02T12:10:45.581373155 [DataPlaneSelectorManagerImpl] DataPlaneInstance edc073-tractusx-connector-azure-vault-dataplane is now in state AVAILABLE
DEBUG 2024-08-02T12:11:45.629833481 [DataPlaneSelectorManagerImpl] DataPlaneInstance edc073-tractusx-connector-azure-vault-dataplane is now in state AVAILABLE
DEBUG 2024-08-02T12:12:45.669354558 [DataPlaneSelectorManagerImpl] DataPlaneInstance edc073-tractusx-connector-azure-vault-dataplane is now in state AVAILABLE

How can this be stopped?

[ndr-brt]

it is a DEBUG message, to stop it just put the log level to INFO. not a bug.

[jerzy-wachowiak]

Default chart settings are used with .level=INFO : control plane: https://github.com/eclipse-tractusx/tractusx-edc/blob/bdaa97347f76c977cb22aa5419558c80403e147b/charts/tractusx-connector-azure-vault/values.yaml#L303-L309 data plane: https://github.com/eclipse-tractusx/tractusx-edc/blob/bdaa97347f76c977cb22aa5419558c80403e147b/charts/tractusx-connector-azure-vault/values.yaml#L548-L554

Where the log level should be set?

[ndr-brt]

good catch, looks like default level cannot be changed. Opened an issue upstream: https://github.com/eclipse-edc/Connector/issues/4392

[github-actions[bot]]

This issue is stale because it has been open for 2 weeks with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 7 days since being marked as stale.