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

bug: return errors when iptables and ip6tables are unusable #712

Merged
merged 1 commit into from
May 4, 2022

Conversation

joejulian
Copy link
Contributor

@joejulian joejulian commented Mar 4, 2022

When a problem occurs accessing both iptables and ip6tables in portmap, return an error that contains the origin errors.

Fixes #711

@joejulian joejulian force-pushed the joe/add_error_output branch 3 times, most recently from 3f6ae79 to 8e8f06d Compare March 4, 2022 04:29
@joejulian joejulian force-pushed the joe/add_error_output branch 2 times, most recently from 77b9503 to f90abab Compare April 1, 2022 17:55
Signed-off-by: Joe Julian <me@joejulian.name>
@dcbw
Copy link
Member

dcbw commented Apr 13, 2022

/lgtm

(I thought about error wrapping, but since both the errors are at the same level, not sure that makes as much sense...)

@joejulian
Copy link
Contributor Author

/lgtm

(I thought about error wrapping, but since both the errors are at the same level, not sure that makes as much sense...)

I considered it, as well, but then thought the same.

Copy link
Member

@mars1024 mars1024 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
(forget about the error wrapping)

@dcbw dcbw merged commit 6a94696 into containernetworking:main May 4, 2022
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 this pull request may close these issues.

If both ipv4 iptables fails and ipv6 tables fail, the failure reason is lost
3 participants