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

remote: kube: publish containerPort by default #23470

Closed
edsantiago opened this issue Aug 1, 2024 · 1 comment · Fixed by #23533
Closed

remote: kube: publish containerPort by default #23470

edsantiago opened this issue Aug 1, 2024 · 1 comment · Fixed by #23533
Assignees
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote

Comments

@edsantiago
Copy link
Member

Looks like a bug in the tests themselves, port conflict on 80, multiple tests running at once:

Podman kube play
           [It] podman play kube should not publish containerPort by default
...
           # podman-remote [options] kube play /tmp/CI_Xnh8/podman-e2e-1779494458/subtest-50866493/kube.yaml
           time="2024-07-11T15:49:19-05:00" level=warning msg="IdleTracker: StateClosed transition by connection marked un-managed" X-Reference-Id=0xc00019d720
           Pod:
           892f3d313fcf456f4ba1dfca9515256317dffc537ca7ec1a678ae99ca4027078
           Container:
           a0daf3d19882360f456ee4769fd5fe534eba8e3addd324b7a799f1d2efae610b
         

           [FAILED] Expected
               <string>: podman rulez
           to equal
               <string>: connection refused

or, in other cases:

           [FAILED] Expected
               <string>: Get "http://localhost:80": read tcp 127.0.0.1:56764->127.0.0.1:80: read: connection reset by peer
           to contain substring
               <string>: connection refused

What troubles me is that Expect(ExitCleanly()) is not catching this.

Filing as a placeholder. I'll take a look when time allows, unless anyone else feels like tackling it.

  • debian-13 : int remote debian-13 root host sqlite [remote]
    • 07-31 13:56 in Podman kube play podman play kube should not publish containerPort by default
    • 07-22 15:38 in Podman kube play podman play kube should not publish containerPort by default
  • fedora-40 : int remote fedora-40 root host sqlite [remote]
    • 07-31 23:04 in Podman kube play podman play kube should not publish containerPort by default
    • 07-31 11:17 in Podman kube play podman play kube should not publish containerPort by default
    • 07-31 11:17 in Podman kube play podman play kube should not publish containerPort by default
    • 07-11 16:53 in Podman kube play podman play kube should not publish containerPort by default
x x x x x x
int(6) remote(6) fedora-40(4) root(6) host(6) sqlite(6)
debian-13(2)
@edsantiago edsantiago added flakes Flakes from Continuous Integration remote Problem is in podman-remote labels Aug 1, 2024
@edsantiago edsantiago self-assigned this Aug 1, 2024
@edsantiago
Copy link
Member Author

This one, too, is flaking daily. What I don't understand is where this one has come from, why it's new.

  • debian-13 : int podman debian-13 root host sqlite
    • 08-06 11:34 in Podman kube play podman play kube should not publish containerPort by default
  • debian-13 : int remote debian-13 root host sqlite [remote]
    • 08-06 12:37 in Podman kube play podman play kube should not publish containerPort by default
    • 08-06 11:33 in Podman kube play podman play kube should not publish containerPort by default
    • 08-05 18:33 in Podman kube play podman play kube should not publish containerPort by default
    • 08-05 07:44 in Podman kube play podman play kube should not publish containerPort by default
    • 08-04 16:19 in Podman kube play podman play kube should not publish containerPort by default
    • 08-01 09:26 in Podman kube play podman play kube should not publish containerPort by default
    • 08-01 08:10 in Podman kube play podman play kube should not publish containerPort by default
    • 07-31 13:56 in Podman kube play podman play kube should not publish containerPort by default
  • fedora-39 : int remote fedora-39 root host boltdb [remote]
    • 08-06 11:34 in Podman kube play podman play kube should not publish containerPort by default
  • fedora-40 : int remote fedora-40 root host sqlite [remote]
    • 08-04 16:22 in Podman kube play podman play kube should not publish containerPort by default
    • 08-04 09:42 in Podman kube play podman play kube should not publish containerPort by default
    • 07-31 23:04 in Podman kube play podman play kube should not publish containerPort by default
    • 07-31 11:17 in Podman kube play podman play kube should not publish containerPort by default
    • 07-31 11:17 in Podman kube play podman play kube should not publish containerPort by default
  • rawhide : int remote rawhide root host sqlite [remote]
    • 08-05 07:47 in Podman kube play podman play kube should not publish containerPort by default
x x x x x x
int(16) remote(15) debian-13(9) root(16) host(16) sqlite(15)
podman(1) fedora-40(5) boltdb(1)
fedora-39(1)
rawhide(1)

@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Nov 7, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Nov 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant