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

[Flake] [sig-cli] Kubectl client Simple pod should return command exit codes should support port-forward #124470

Open
aojea opened this issue Apr 23, 2024 · 3 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/cli Categorizes an issue or PR as relevant to SIG CLI.

Comments

@aojea
Copy link
Member

aojea commented Apr 23, 2024

See this once in https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/124467/pull-kubernetes-e2e-kind-ipv6/1782694702064078848 but the error does not look right

{ failed [FAILED] Container port output missing expected value. Wanted:'It works!', got: Client sent an HTTP request to an HTTPS server.
In [It] at: k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:554 @ 04/23/24 09:14:34.283
}

how can port forward send this to an https server?

STEP: forwarding the container port to a local port - k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:542 @ 04/23/24 09:14:34.071
I0423 09:14:34.071990 69210 portforward.go:180] starting port-forward command and streaming output
I0423 09:14:34.072086 69210 util.go:585] Asynchronously running '/home/prow/go/src/k8s.io/kubernetes/_output/bin/kubectl kubectl --server=https://[::1]:34783 --kubeconfig=/root/.kube/kind-test-config --namespace=kubectl-6707 port-forward --namespace=kubectl-6707 httpd :80'
I0423 09:14:34.072534 69210 portforward.go:189] reading from `kubectl port-forward` command's stdout
STEP: curling local port output - k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:546 @ 04/23/24 09:14:34.276
I0423 09:14:34.277776 69210 kubectl.go:549] got: Client sent an HTTP request to an HTTPS server.

[FAILED] Container port output missing expected value. Wanted:'It works!', got: Client sent an HTTP request to an HTTPS server.

are we. leaking connections or not redirecting it correctly and the upgreadware proxy fails?

/cc @liggitt @seans3

/kind flake

@k8s-ci-robot k8s-ci-robot added kind/flake Categorizes issue or PR as related to a flaky test. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 23, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@neolit123
Copy link
Member

/sig cli

@k8s-ci-robot k8s-ci-robot added sig/cli Categorizes an issue or PR as relevant to SIG CLI. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 24, 2024
@eddiezane
Copy link
Member

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/cli Categorizes an issue or PR as relevant to SIG CLI.
Projects
Status: Needs Triage
Development

No branches or pull requests

4 participants