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

Error on commit #34

Open
zachfi opened this issue Jul 7, 2018 · 7 comments
Open

Error on commit #34

zachfi opened this issue Jul 7, 2018 · 7 comments

Comments

@zachfi
Copy link
Contributor

zachfi commented Jul 7, 2018

Trying to commit now I get:

expected element type <commit-results> but have <ok>

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?

@scottdware
Copy link
Owner

scottdware commented Jul 9, 2018

What version of JUNOS are you running, and what platform are you on?

@zachfi
Copy link
Contributor Author

zachfi commented Jul 11, 2018

I'm on an SRX 300 using firmware15.1X49-D130.6 currently.

@scottdware
Copy link
Owner

Thanks, I'll dig into it and figure out what's up.

@zachfi
Copy link
Contributor Author

zachfi commented Jul 12, 2018

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.

@daemus
Copy link
Contributor

daemus commented Dec 6, 2018

Is this a single SRX? Or a cluster?

@zachfi
Copy link
Contributor Author

zachfi commented Dec 21, 2018

This is just a single SRX.

@abaluta
Copy link

abaluta commented Jun 26, 2019

The problem is somewhat larger:
MX960 responds:

<commit-results>
<routing-engine junos:style="show-name">
<name>re0</name>
<commit-check-success/>
</routing-engine>
<routing-engine junos:style="show-name">
<name>re1</name>
<commit-check-success/>
</routing-engine>
</commit-results>
<ok/>

But, (I tests only MX80 and MX204) responds:
<ok/>

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

4 participants