Skip to content

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

@pohly

Description

@pohly

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.kind/flakeCategorizes issue or PR as related to a flaky test.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.

    Type

    No type

    Projects

    Status

    FLAKY

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions