You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@dineshbaburam91, having read the thread it's not clear to me why this is an ncclient issue, but I may have missed something. For example, if an XML payload contains text such as:
set policy-options prefix-list ntp-servers apply-path "system ntp server <*>
...then the payload does not conform to the encoding rules. < should be encoded as < and > should be encoded as >.
Can you please go into more details here as to why you think ncclient or the lxml parser is at fault? Specifically, can you show payloads that both conform to the NETCONF encoding rules for XML documents (W3C.REC-xml-20001006) and which trigger a defect in ncclient?
The issue is from ncclient module. Kindly check this GitHub ticket for more details.
Juniper/ansible-junos-stdlib#528
The text was updated successfully, but these errors were encountered: