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

Fix tang test (part 2) #510

Merged
merged 2 commits into from
Mar 20, 2024
Merged

Fix tang test (part 2) #510

merged 2 commits into from
Mar 20, 2024

Conversation

jepio
Copy link
Member

@jepio jepio commented Mar 20, 2024

Fix the tang test by moving the tang listener into the qemu network namespace.

Also an attempt to speed up container build so the second commit will be pushed after the first build completes.

@jepio jepio force-pushed the fix-tang-test-part2 branch from e2e16a1 to 94bccea Compare March 20, 2024 09:29
@jepio jepio force-pushed the fix-tang-test-part2 branch from 94bccea to 4256012 Compare March 20, 2024 09:31
@jepio jepio requested a review from a team March 20, 2024 10:43
@@ -93,6 +93,20 @@ func (lc *LocalCluster) GetOmahaHostPort() (string, error) {
return net.JoinHostPort(lc.hostIP(), port), nil
}

func (lc *LocalCluster) NewTangListener() (*net.Listener, error) {
Copy link
Member

Choose a reason for hiding this comment

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

This does not seem to be specific at all to Tang, so maybe name it NewListenerInsideClusterNS?

Copy link
Member Author

Choose a reason for hiding this comment

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

makes sense - pushed the change

The current version of the test creates a host socket which is affected by host
iptables settings. This is why both tang tests are currently failing on our
hosted infra. Rework the test to create a listener in the network namespace of
the kola flight, which avoids host networking issues. We still have to
dynamically find a port to avoid test case port collision, because kola runs
all (qemu) tests inside the same network namespace.

Signed-off-by: Jeremi Piotrowski <[email protected]>
@jepio jepio force-pushed the fix-tang-test-part2 branch from 3a1c7dc to 41c9bf9 Compare March 20, 2024 12:12
@jepio
Copy link
Member Author

jepio commented Mar 20, 2024

I ran a test with this PRs container image here: http://jenkins.infra.kinvolk.io:8080/job/container/job/test/20754/console

@krnowak
Copy link
Member

krnowak commented Mar 20, 2024

I ran a test with this PRs container image here: http://jenkins.infra.kinvolk.io:8080/job/container/job/test/20754/console

Are they still failing?

[2024-03-20T10:54:32.376Z] Failed tests:
[2024-03-20T10:54:32.376Z] cl.tang.root
[2024-03-20T10:54:32.376Z] cl.tpm.root

@jepio
Copy link
Member Author

jepio commented Mar 20, 2024

Yes, it still fails because we're missing this fix (WIP): flatcar/bootengine#90. That will come later.

@jepio jepio merged commit dd7518a into flatcar-master Mar 20, 2024
2 checks passed
@jepio jepio deleted the fix-tang-test-part2 branch March 20, 2024 13:50
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.

2 participants