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

Netavark userns test: give aardvark time to come up #18342

Merged

Conversation

edsantiago
Copy link
Member

Nasty test flake, "bad address nc-server.dns.podman"

Cause: "There is absolutely no guarantee that aardvark-dns
is ready before the container is started." (source: Paul).

"Solution" (not really): wait before doing a host lookup.

Closes: #16272 (I hope)

Signed-off-by: Ed Santiago [email protected]

None

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 25, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: edsantiago

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 25, 2023
Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

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

Yeah that is a very unfortunate thing but I don't see us fixing this any time soon so this LGTM.

@edsantiago
Copy link
Member Author

OOPS! Re-pushed because I looked at flake logs and realized that this is flaking in the non-Netavark test also.

@Luap99
Copy link
Member

Luap99 commented Apr 25, 2023

OOPS! Re-pushed because I looked at flake logs and realized that this is flaking in the non-Netavark test also.

Oh good I really need to clean these duplicates up, so many pointless skipIfCNI/Netavark stuff in there. These tests are equivalent, we don't need two tests for the same thing.

@edsantiago
Copy link
Member Author

edsantiago commented Apr 25, 2023

Good point. This is the ONLY diff between those two tests:

--- test/e2e/aaa        2023-04-25 09:32:09.641689452 -0600
+++ test/e2e/bbb        2023-04-25 09:32:23.550742868 -0600
@@ -1,5 +1,6 @@
-       It("podman network works across user ns", func() {
-               netName := stringid.GenerateRandomID()
+       It("podman Netavark network works across user ns", func() {
+               SkipIfCNI(podmanTest)
+               netName := createNetworkName("")
                create := podmanTest.Podman([]string{"network", "create", netName})
                create.WaitWithDefaultTimeout()
                Expect(create).Should(Exit(0))

@Luap99 I'm happy to compress those two into one, in this PR, but I don't know if there's a valid important difference between a network named by GenerateRandomIO() and one generated by createNetworkName(). My ignorant guess is that there is no difference, and the createNetworkName version is more readable and should be kept. Without the skip and without Netavark in the test name. Any objection to my doing that?

@Luap99
Copy link
Member

Luap99 commented Apr 25, 2023

Any objection to my doing that?

No if you want feel free to do that, I am also fine merging it like that.

Nasty test flake, "bad address nc-server.dns.podman"

Cause: "There is absolutely no guarantee that aardvark-dns
is ready before the container is started." (source: Paul).

Workaround (not a real solution): wait before doing a host lookup.

Also: remove a 99%-duplicate test.

Closes: containers#16272   (I hope)

Signed-off-by: Ed Santiago <[email protected]>
@edsantiago
Copy link
Member Author

Cleanup is one of life's little joys, and I would like some joy today. Repushed with duplication removed and with updated commit message. Thanks again for your feedback.

@Luap99
Copy link
Member

Luap99 commented Apr 25, 2023

Understandable, LGTM

@baude
Copy link
Member

baude commented Apr 26, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 26, 2023
@openshift-merge-robot openshift-merge-robot merged commit 846e7aa into containers:main Apr 26, 2023
@edsantiago edsantiago deleted the aardvarks_are_slow branch April 26, 2023 13:35
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Aug 26, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note-none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Netavark: userns: nc: bad address 'nc-server.dns.podman'
4 participants