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

Cluster with IPv6 leads to agent crash when stealing #2788

Open
aviramha opened this issue Sep 30, 2024 · 4 comments · Fixed by #2791
Open

Cluster with IPv6 leads to agent crash when stealing #2788

aviramha opened this issue Sep 30, 2024 · 4 comments · Fixed by #2791
Assignees

Comments

@aviramha
Copy link
Member

Originally from here
#2728 (comment)

2024-09-30T10:02:38.653317Z TRACE handle_agent_message{Close("Background task `Stealer` failed with `IPTables failed with `code: 2, msg: iptables v1.8.9 (legacy): host/network `fc00:1000::fa24' not found\nTry `iptables -h' or 'iptables --help' for more information.\n``")}: mirrord_intproxy: return=Err(AgentFailed("Background task `Stealer` failed with `IPTables failed with `code: 2, msg: iptables v1.8.9 (legacy): host/network `fc00:1000::fa24' not found\nTry `iptables -h' or 'iptables --help' for more information.\n``"))
Copy link

linear bot commented Sep 30, 2024

@aviramha
Copy link
Member Author

@sahityacodes does your pod have both ipv6/ipv4 or only ipv6? because if only ipv6 this will be harder to fix.

@sahityacodes
Copy link

Our pod is deployed with istio proxy container. The main application itself contains IPV4 only, however when deployed in a cluster that supports dual stack configurations, istio proxy can work with both IPv4 and IPv6 I suppose. So, I guess it has both IPv4 and IPv6

@aviramha
Copy link
Member Author

Ok so I believe my fix would work for your case :)

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

Successfully merging a pull request may close this issue.

2 participants