thank you Wai for the response, yes, i checked confd configuration file and found that rollback is set to true and rollback files are generated at the specified directory.
May I know how those rollback files might have been deleted ? Does confd automatically purge them at certain condition?
Actually, I am still checking with client to know more details and the history related to onset of this incident. Client was able to see the outputs properly but faced this discrepancy after just upgrading the software of our product (which internally uses conf-api-6.3.jar). I’ve already enquired if similar limitation was observed in previous upgrades or not.
About ConfD log files: We’ve not enabled confd and developer logs, below is an example.
An upgrade may invalidate the rollback files generated prior to the upgrade. For example, there may be mandatory leaf nodes without default values that have been added in the upgraded YANG models missing in the old rollback files. Even if the rollback files are there for those cases, they can’t be used. Check to see if the rollback files may have been intentionally removed during the upgrade.