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.

Sign up for GitHub

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

Jump to bottom

Failure cluster [44fa5cdb...]: TestFrontProxyConfig/WithoutUID: #128565

Open
pohly opened this issue Nov 5, 2024 · 6 comments
Open

Failure cluster [44fa5cdb...]: TestFrontProxyConfig/WithoutUID: #128565

pohly opened this issue Nov 5, 2024 · 6 comments
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@pohly
Copy link
Contributor

pohly commented Nov 5, 2024

Failure cluster 44fa5cdb3ee6c1ca81f2

Error text:
Failed;Failed;
=== RUN   TestFrontProxyConfig/WithoutUID
    testserver.go:581: Resolved testserver package path to: "/home/prow/go/src/k8s.io/kubernetes/cmd/kube-apiserver/app/testing"
    testserver.go:401: runtime-config=map[api/all:true]
    testserver.go:402: Starting kube-apiserver on port 42541...
...
    apiserver_test.go:350: expected UID: "24d7c521-dceb-47e4-aa29-ceabe7c6320a", got: ""
    apiserver_test.go:353: expected name: "system:serviceaccount:integration-test-front-proxy-config:wardle-client-sa", got: "system:kube-aggregator"
    apiserver_test.go:356: expected groups: [system:serviceaccounts system:serviceaccounts:integration-test-front-proxy-config system:authenticated], got: [system:authenticated]
    apiserver_test.go:359: expected extra to be map[authentication.kubernetes.io/credential-id:[JTI=97c7bbc2-7a1b-4e58-9f10-ac3d780144ba]], but got map[]
    apiserver_test.go:385: the request is in fact not being tested

Recent failures:

10/28/2024, 12:52:08 AM ci-kubernetes-integration-master
10/23/2024, 12:47:59 PM ci-kubernetes-integration-master

/kind failing-test
/kind flake
/sig api-machinery
@k8s-ci-robot k8s-ci-robot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 5, 2024
@pohly pohly mentioned this issue Nov 5, 2024
Merged
@jamall-mahmoudi-dev
Copy link

According to the logs, the main reason for these errors is the missing apiserver.crt file. This file is essential as a certificate for establishing secure communications between different components of a Kubernetes cluster. Its absence could be due to misconfiguration of tests or incorrect generation of files.

@aojea
Copy link
Member

aojea commented Nov 6, 2024

@jamall-mahmoudi-dev can you paste the log you are referring too?

The job I checked fails because of the following assertions

   apiserver_test.go:938: CA bundle "127.0.0.1-ca@1531467593" [] issuer="<self>" (2018-07-13 06:39:53 +0000 UTC to 2118-06-19 06:39:53 +0000 UTC (now=2024-10-28 00:38:09.507362071 +0000 UTC))
    apiserver_test.go:350: expected UID: "1ce41219-83ee-4638-8563-a7691307c418", got: ""
    apiserver_test.go:353: expected name: "system:serviceaccount:integration-test-front-proxy-config:wardle-client-sa", got: "system:kube-aggregator"
    apiserver_test.go:356: expected groups: [system:serviceaccounts system:serviceaccounts:integration-test-front-proxy-config system:authenticated], got: [system:authenticated]
    apiserver_test.go:359: expected extra to be map[authentication.kubernetes.io/credential-id:[JTI=161da376-19ed-4ed5-b50e-b352150cc260]], but got map[]

@dims
Copy link
Member

dims commented Nov 25, 2024

we see a few hits in new runs .. https://storage.googleapis.com/k8s-triage/index.html?text=the%20request%20is%20in%20fact%20not%20being%20tested

@pohly pohly mentioned this issue Nov 29, 2024
Closed
@wendy-ha18
Copy link
Member

@kubernetes/release-team-release-signal

@sttts sttts mentioned this issue Nov 29, 2024
Closed
@pohly pohly mentioned this issue Nov 29, 2024
Merged
@pacoxu pacoxu mentioned this issue Dec 2, 2024
Closed
@pacoxu
Copy link
Member

pacoxu commented Dec 5, 2024

https://storage.googleapis.com/k8s-triage/index.html?text=PriorityLevelConfiguration
https://storage.googleapis.com/k8s-triage/index.html?text=TestFrontProxyConfig

The test flakes in

  • ci-kubernetes-integration-1-32
  • ci-kubernetes-integration-master

Does this flake indict some bugs(do we confirm that this is not a blocker) or is this just a flake?

@Jefftree
Copy link
Member

/cc @deads2k
/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
CI Signal (SIG Release / Release Team)
Status: FLAKY
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

integration/apiserver: ignore discovery+availability reqs in front-proxy test sttts/kubernetes
8 participants
@pohly @dims @pacoxu @aojea @Jefftree @k8s-ci-robot @wendy-ha18 @jamall-mahmoudi-dev