Stale Target and Config CR readiness persists until data-server restart

[Tanujabais123]

We are observing stale and incorrect readiness states for both Target CRs and Config CRs in the SDC platform. Some Config CRs remain in READY=False with the reason “config not applied”, and the corresponding Target CRs remain “config not ready”, even though the configuration has already been successfully applied to the device.

This stale state persists indefinitely and does not self‑recover through reconciliation. Restarting the data-server pod immediately resolves the issue: all affected Config CRs and Target CRs transition to READY=True with “config applied and target ready”, without any changes to Config CRs, Target CRs, Schema CRs, or Git repositories.

Observed behavior

Config CRs get stuck in:
READY=False
REASON=config not applied

Target CRs get stuck in:
READY=False
REASON=config not ready

Some targets using the same provider/version are READY=True while others are stuck
Deviations sometimes appear missing or ignored during this stale state
Restarting the data-server immediately corrects all statuses
No restart of schema-server, api-server, or controllers is required

[steiler]

Can you provide trace level logs, please.
Add the -t flag to the args of the data-server container.

[Tanujabais123]

sdc-data-server-logs.txt

[steiler]

@Tanujabais123 sorry should be more precise here.
The logs provided are from the controller container in the statefullSet. Can you provide the logs of the data-server container, please!

 kubectl logs -n sdc-system statefulsets/data-server-controller data-server