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

«jool_siit --eamt» failing with «Error code: 3»; entries missing from output #249

Closed
toreanderson opened this Issue Aug 25, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@toreanderson
Contributor

toreanderson commented Aug 25, 2017

I know for a fact that there is an EAMT entry for 87.238.60.1/32 2a02:c0:400:17::2/128 installed on this Jool node. It is working fine too, I can ping 87.238.60.1 through the Jool node without issues and so on.

However it doesn't show up in output from jool_siit --eamt. Plenty of other EAMs does show up in its output though. So either it is only 87.238.60.1/32 2a02:c0:400:17::2/128 that is missing, or if there are others, it's not many.

root@sdbr1-osl2:~# jool_siit --eamt | egrep '(87.238.60.1|2a02:c0:400:17::2)/'
Jool Error: 
(Error code: 3)

This trips up our provisioning systems since it compares the output from jool_siit --eamt with its database, trying to add/remove EAMs to make the former match the latter. Essentially it ends up trying to do this, which fails:

root@sdbr1-osl2:~# jool_siit --eamt --add 87.238.60.1 2a02:c0:400:17::2
Jool Error: The requested entry already exists.

(Error code: 17)

I see this on two Jool nodes running 21b97b1 as well as one running v3.5.2. Identical config on all three.

@toreanderson toreanderson changed the title from `jool_siit --eamt` failing with `Error code: 3`; entries missing from output to «jool_siit --eamt» failing with «Error code: 3»; entries missing from output Aug 25, 2017

@ydahhrk

This comment has been minimized.

Show comment
Hide comment
@ydahhrk

ydahhrk Aug 25, 2017

Member

Is this two bugs in one? You said that some entries are showing up, but the output you posted is a flat error.

I managed to reproduce the "flat error" part by trying to print a very large EAMT, but I'm still trying to reproduce the entry skipping-part.

Edit: Never mind; found it.

Member

ydahhrk commented Aug 25, 2017

Is this two bugs in one? You said that some entries are showing up, but the output you posted is a flat error.

I managed to reproduce the "flat error" part by trying to print a very large EAMT, but I'm still trying to reproduce the entry skipping-part.

Edit: Never mind; found it.

@ydahhrk ydahhrk added this to the 3.5.5 milestone Aug 25, 2017

ydahhrk added a commit that referenced this issue Aug 25, 2017

Fix foreach during --eamt --display
Was foreaching on the wrong tree.

Likely fixes #249.

ydahhrk added a commit that referenced this issue Aug 25, 2017

Fix foreach during --eamt --display
Was foreaching on the wrong tree.

Applies #249 solution to master.
@ydahhrk

This comment has been minimized.

Show comment
Hide comment
@ydahhrk

ydahhrk Aug 25, 2017

Member

Fix ready, I believe. Please test.

e6afbda patches the version you're using. e9a3991 patches Jool 3.5.4.

Member

ydahhrk commented Aug 25, 2017

Fix ready, I believe. Please test.

e6afbda patches the version you're using. e9a3991 patches Jool 3.5.4.

@toreanderson

This comment has been minimized.

Show comment
Hide comment
@toreanderson

toreanderson Aug 25, 2017

Contributor

Confirmed; e9a3991 doesn't exhibit the problem. Thank you!

Contributor

toreanderson commented Aug 25, 2017

Confirmed; e9a3991 doesn't exhibit the problem. Thank you!

@ydahhrk

This comment has been minimized.

Show comment
Hide comment
@ydahhrk

ydahhrk Nov 24, 2017

Member

3.5.5 released; closing.

Member

ydahhrk commented Nov 24, 2017

3.5.5 released; closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment