Disable iptables/ip6tables in two tests to remove conflict#48642
Merged
thaJeztah merged 1 commit intomoby:masterfrom Oct 11, 2024
Merged
Disable iptables/ip6tables in two tests to remove conflict#48642thaJeztah merged 1 commit intomoby:masterfrom
thaJeztah merged 1 commit intomoby:masterfrom
Conversation
TestAttachDisconnectLeak starts its own daemon with iptables disabled, but disabling ip6tables was missed when we enabled ip6tables by default. TestNetworkStateCleanupOnDaemonStart also starts its own daemon, with iptables and ip6tables both enabled. It isn't trying to test anything iptables related. These tests run in parallel, so they both modify ip6tables in the host namespace - and could break each other by adding/removing chains at awkward moments. Disable iptables and ip6tables in both tests. Signed-off-by: Rob Murray <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
- What I did
Fix a flaky test ...
TestAttachDisconnectLeakstarts its own daemon with iptables disabled, but disabling ip6tables was missed when we enabled ip6tables by default.TestNetworkStateCleanupOnDaemonStartalso starts its own daemon, with iptables and ip6tables both enabled. It isn't trying to test anything iptables related.These tests run in parallel, so they both modify ip6tables in the host namespace - and could break each other by adding/removing chains at awkward moments.
From a CI run ...
- How I did it
Disable iptables and ip6tables in both tests.
- How to verify it
n/a
- Description for the changelog