Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

juniper_junos_command - lxml.etree.XMLSyntaxError: StartTag: invalid element name #580

Closed
dineshbaburam91 opened this issue Jan 18, 2024 · 2 comments

Comments

@dineshbaburam91
Copy link

The issue is from ncclient module. Kindly check this GitHub ticket for more details.

Juniper/ansible-junos-stdlib#528

@einarnn
Copy link
Contributor

einarnn commented Feb 17, 2024

@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 &lt; and > should be encoded as &gt;.

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?

Cheers,

Einar

@einarnn
Copy link
Contributor

einarnn commented Apr 9, 2024

No feedback on examples requested. Closing for now.

@einarnn einarnn closed this as completed Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants