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

[Failing Test] [sig-api-machinery] ResourceQuota [Feature:CrossNamespacePodAffinity] [alpha] should verify ResourceQuota with cross namespace pod affinity scope using scope-selectors #99820

Closed
thejoycekung opened this issue Mar 5, 2021 · 9 comments
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/windows Categorizes an issue or PR as relevant to SIG Windows. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@thejoycekung
Copy link
Contributor

Which jobs are failing:

ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd

Which test(s) are failing:

[sig-api-machinery] ResourceQuota [Feature:CrossNamespacePodAffinity] [alpha] should verify ResourceQuota with cross namespace pod affinity scope using scope-selectors

Since when has it been failing:

da9ea2e...f63cac6

Looks to be related to #98582

Testgrid link:

https://testgrid.k8s.io/sig-release-master-informing#aks-engine-azure-windows-master-containerd

Reason for failure:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/resource_quota.go:1426
Mar  5 01:22:20.463: Unexpected error:
    <*errors.StatusError | 0xc002bd57c0>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {
                SelfLink: "",
                ResourceVersion: "",
                Continue: "",
                RemainingItemCount: nil,
            },
            Status: "Failure",
            Message: "ResourceQuota \"quota-cross-namespace-pod-affinity\" is invalid: spec.scopeSelector.matchExpressions.scopeName: Invalid value: \"CrossNamespacePodAffinity\": unsupported scope",
            Reason: "Invalid",
            Details: {
                Name: "quota-cross-namespace-pod-affinity",
                Group: "",
                Kind: "ResourceQuota",
                UID: "",
                Causes: [
                    {
                        Type: "FieldValueInvalid",
                        Message: "Invalid value: \"CrossNamespacePodAffinity\": unsupported scope",
                        Field: "spec.scopeSelector.matchExpressions.scopeName",
                    },
                ],
                RetryAfterSeconds: 0,
            },
            Code: 422,
        },
    }
    ResourceQuota "quota-cross-namespace-pod-affinity" is invalid: spec.scopeSelector.matchExpressions.scopeName: Invalid value: "CrossNamespacePodAffinity": unsupported scope
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/resource_quota.go:1430

Anything else we need to know:

Example in Spyglass: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd/1367634562754023424

/sig api-machinery
/cc @ahg-g

@thejoycekung thejoycekung added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Mar 5, 2021
@k8s-ci-robot k8s-ci-robot added 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 Mar 5, 2021
@thejoycekung thejoycekung added this to New (no response yet) in CI Signal team (SIG Release) Mar 5, 2021
@ahg-g
Copy link
Member

ahg-g commented Mar 5, 2021

Any idea where are the yamls files for this test is? This is an alpha feature, and the test shouldn't be running it unless the feature is enabled.

@thejoycekung
Copy link
Contributor Author

thejoycekung commented Mar 5, 2021

I think the YAML for this job should be here - SIG Windows technically owns it.

https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes-sigs/sig-windows/sig-windows-config.yaml#L612

@thejoycekung thejoycekung moved this from New (no response yet) to Under investigation (prioritized) in CI Signal team (SIG Release) Mar 5, 2021
@ahg-g
Copy link
Member

ahg-g commented Mar 5, 2021

@jsturtevant any idea if this test enables alpha features? If not, then it should skip [Alpha] tagged tests here: https://github.com/kubernetes/test-infra/blob/8f06baa82fab226a0f4bb41a3d1d9a640695a228/config/jobs/kubernetes-sigs/sig-windows/sig-windows-config.yaml#L657

@jsturtevant
Copy link
Contributor

Thanks we opened a PR to fix this yesterday: kubernetes/test-infra#21156.

@jsturtevant
Copy link
Contributor

/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 Mar 5, 2021
@jsturtevant
Copy link
Contributor

/sig windows

@k8s-ci-robot k8s-ci-robot added the sig/windows Categorizes an issue or PR as relevant to SIG Windows. label Mar 5, 2021
@jsturtevant
Copy link
Contributor

@jsturtevant
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@jsturtevant: Closing this issue.

In response to this:

/close

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.

CI Signal team (SIG Release) automation moved this from Under investigation (prioritized) to Observing (observe test failure/flake before marking as resolved) Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/windows Categorizes an issue or PR as relevant to SIG Windows. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
CI Signal team (SIG Release)
  
Observing (observe test failure/flake...
Development

No branches or pull requests

4 participants