Unable to commit on xe device because candidate capability rejected

[bhumong]

Unable to commit on xe device because candidate capability rejected

Issue:

• Push-commit flow issues <lock><target><candidate/></target></lock> (message-id=3) to the xe device and moves the session into PUSH-LOCK.

  cannot commit on xe device
  Jan 23 04:35:48.930413: transaction_notification_handler: pid: 1041 Transaction 2 failed in xe: Device xe in state PUSH-LOCK:protocol invalid-value Unsupported capability :candidate <bad-element>candidate</bad-element>
  Failed
  

• The device immediately replies with <rpc-error> saying “Unsupported capability :candidate” and Clixon logs Transaction 2 failed in xe: Device xe in state PUSH-LOCK:protocol invalid-value Unsupported capability :candidate <bad-element>candidate</bad-element> (Jan 23 04:35:48.930413).

Logs:

Jan 23 04:35:48.921518: xml_cmp:412: protocol protocol eq:0 nr: 0 0 yi: 0 0
Jan 23 04:35:48.921520: xml_cmp:412: identifier identifier eq:0 nr: 0 0 yi: 0 0
Jan 23 04:35:48.921521: xml_cmp:412: name name eq:0 nr: 0 0 yi: 0 0
Jan 23 04:35:48.921523: xml_cmp:412: config config eq:0 nr: 0 0 yi: 0 0
Jan 23 04:35:48.921524: xml_cmp:412: identifier identifier eq:0 nr: 0 0 yi: 0 0
Jan 23 04:35:48.921525: xml_cmp:412: name name eq:0 nr: 0 0 yi: 0 0
Jan 23 04:35:48.921528: device_create_edit_config_diff:443: 
Jan 23 04:35:48.921766: clixon_msg_send:374: Send [xe] 
#116
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="3"><lock><target><candidate/></target></lock></rpc>
##
Jan 23 04:35:48.921799: device_handle_conn_state_set:635: xe: OPEN -> PUSH-LOCK
Jan 23 04:35:48.921803: device_state_timeout_register:609: timeout:60 s
Jan 23 04:35:48.921805: clixon_event_reg_timeout:371: Device xe in state PUSH-LOCK
Jan 23 04:35:48.922014: rpc_callback_call:1556: retval:1
Jan 23 04:35:48.922033: clixon_msg_send:374: Send [s:2 r:controller-commit m:42] 
#120
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><tid xmlns="http://clicon.org/controller">2</tid></rpc-reply>
##