-
Notifications
You must be signed in to change notification settings - Fork 41
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
Error on commit #34
Comments
What version of JUNOS are you running, and what platform are you on? |
I'm on an SRX 300 using firmware |
Thanks, I'll dig into it and figure out what's up. |
Let me know if I can provide any further detail. Its worth noting that the change does actually get committed, so it seems that its just a result response that is not parsing correctly. I'm not sure if there is a way in go to allow one of two keys in the response, but maybe you can teach me a clever trick. Thanks for looking. |
Is this a single SRX? Or a cluster? |
This is just a single SRX. |
The problem is somewhat larger:
But, (I tests only MX80 and MX204) responds: |
Trying to commit now I get:
Is this perhaps something upstream? I see that we are looking for
commit-results
in the XML, so perhaps this is a change on newer firmware?The text was updated successfully, but these errors were encountered: