Validation points are not triggered during delete operation on confd 8.0.6 version

YANG
1

Hi Team,

We were on confd 7.4.5 version and trying to upgrade to 8.0.6 version.
On 7.4.5 version we could see validation points were triggered by confd and corresponding callback functions were executed when an entity from list is deleted.
Where as in newer version we don’t see validation point is being considered during delete.
Has something been changed from confd w.r.t delete handling.


list addressContext {
key name;
..
        tailf:callpoint sonusAddressContextTP {
         tailf:transaction-hook subtree;
         EXTENSIONS:autoIndex true;
    }
    tailf:callpoint sonusAddressContextHookCP {
        tailf:transaction-hook subtree;
    }
    tailf:validate sonusAddressContextVP {
        tailf:call-once true;
        tailf:dependency .;
    }

leaf name {
      type TC:SonusName;
      tailf:snmp-oid .1;
      tailf:info "
        The name of the address context.
      ";
    }
..
}

On 7.4.5 version

2023-10-27 02:27:04,562874 EDT INFO USHAV43-ISBC2 confd[10595]: devel-c delete request for callpoint sonusAddressContextTP path /ADDRESS_CONTEXT:addressContext{usha2}
2023-10-27 02:27:04,563250 EDT INFO USHAV43-ISBC2 confd[10595]: devel-c delete succeeded for callpoint sonusAddressContextTP path /ADDRESS_CONTEXT:addressContext{usha2}
2023-10-27 02:27:04,563375 EDT INFO USHAV43-ISBC2 confd[10595]: devel-c delete request for callpoint sonusAddressContextHookCP path /ADDRESS_CONTEXT:addressContext{usha2}
2023-10-27 02:27:04,563680 EDT INFO USHAV43-ISBC2 confd[10595]: devel-c delete succeeded for callpoint sonusAddressContextHookCP path /ADDRESS_CONTEXT:addressContext{usha2}


2023-10-27 02:27:04,568706 EDT INFO USHAV43-ISBC2 confd[10595]: devel-c validate request for path /ADDRESS_CONTEXT:addressContext
2023-10-27 02:27:04,568848 EDT INFO USHAV43-ISBC2 confd[10595]: confd progress usid=81 tid=1952 datastore=running context=cli subsystem=CPX_App invoking sonusAddressContextVP validation point
2023-10-27 02:27:04,571131 EDT INFO USHAV43-ISBC2 confd[10595]: devel-c validate succeeded for path /ADDRESS_CONTEXT:addressContext
2023-10-27 02:27:04,577379 EDT INFO USHAV43-ISBC2 confd[10595]: confd progress usid=81 tid=1952 datastore=running context=cli run validation over the changeset (0.006 s)

On 8.0.6 version:

<DEBUG> 27-Oct-2023::02:25:10.831 standby confd[<0.126.0>]: devel-c delete request for callpoint sonusAddressContextHookCP path /ADDRESS_CONTEXT:addressContext{usha1}
<DEBUG> 27-Oct-2023::02:25:10.831 standby confd[<0.126.0>]: devel-c get_elem request for callpoint sonusAddressContextCP path /EXT:addressContextExt{usha1}/name
<DEBUG> 27-Oct-2023::02:25:10.832 standby confd[<0.1250.0>]: devel-c get_elem succeeded for callpoint sonusAddressContextCP path /EXT:addressContextExt{usha1}/name
<DEBUG> 27-Oct-2023::02:25:10.832 standby confd[<0.7595.0>]: devel-c delete succeeded for callpoint sonusAddressContextHookCP path /ADDRESS_CONTEXT:addressContext{usha1}
<DEBUG> 27-Oct-2023::02:25:10.844 standby confd[<0.126.0>]: confd progress usid=113 tid=840 datastore=running context=cli subsystem=CPX_App validate
<DEBUG> 27-Oct-2023::02:25:10.844 standby confd[<0.126.0>]: devel-c new_validate succeeded daemon id: 0 session id: 840 worker id: 29

We noticed that if child node is being deleted, and if parent node has validation point attached to it, parent’s node validation point is triggered, only child node validation point is being ignored during delete.

We are seeing same behavior for all the tables, Is there any new config or flag to trigger the validation point during delete operation.

Thanks for your help in advance.

Regards,
Usha

2

Hi Usha,
Try changing the dependency to something like:

tailf:dependency ../addressContext;

Regards

3

This solution worked, Thanks.