This article describes the issue wherein the resolve device config is stuck at Loading after a config change at the device level.
Rejecting or Accepting the changes does not work.
Resync the device with the network does not resolve the issue as well.
The resolve device config is stuck at Loading after a config change at the device level.
Once the configuration is fetched from device, SDC needs to filter the unnecessary tags in output.
The config reader looks for the end of the configuration by checking for the </configuration> tag followed immediately by a <cli> tag. It assumes these tags will arrive together in the same chunk for processing.
For certain configuration, the response is split differently, so those two tags arrive in separate chunks. When this happens, the reader doesn’t recognize the correct end and appends leftover XML, resulting in a malformed output.
Hence the issue is seen.
Workaround: committing a dummy non-impacting configuration change to avoid the malformed XML output. For example, adding a description to a policy or rule can help resolve the issue.
This issue will be resolved permanently in 26.2.1 version which is expected to be out later this year.