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-cloud-provider-gcp] Provider does not support InstanceGroups #124748

Open
Vyom-Yadav opened this issue May 8, 2024 · 6 comments
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider.

Comments

@Vyom-Yadav
Copy link
Member

Which jobs are failing?

master-informing:

Which tests are failing?

  • Kubernetes e2e suite.[It] [sig-autoscaling] DNS horizontal autoscaling [Serial] [Slow] [KubeUp] kube-dns-autoscaler should scale kube-dns pods when cluster size changed
  • Kubernetes e2e suite.[It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to add nodes
  • Kubernetes e2e suite.[It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to delete nodes
  • Kubernetes e2e suite.[It] [sig-cloud-provider-gcp] [Disruptive] NodeLease NodeLease deletion node lease should be deleted when corresponding node is deleted

Since when has it been failing?

After #124519

Testgrid link

https://testgrid.k8s.io/sig-release-master-informing#gce-cos-master-serial

Reason for failure (if possible)

provider does not support InstanceGroups

Anything else we need to know?

Support for gce instance groups was removed, so these tests need to be either updated (To test some other functionality) or removed.

Relevant SIG(s)

/sig cloud-provider-gcp

@Vyom-Yadav Vyom-Yadav added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label May 8, 2024
@k8s-ci-robot
Copy link
Contributor

@Vyom-Yadav: The label(s) sig/cloud-provider-gcp cannot be applied, because the repository doesn't have them.

In response to this:

Which jobs are failing?

master-informing:

Which tests are failing?

  • Kubernetes e2e suite.[It] [sig-autoscaling] DNS horizontal autoscaling [Serial] [Slow] [KubeUp] kube-dns-autoscaler should scale kube-dns pods when cluster size changed
  • Kubernetes e2e suite.[It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to add nodes
  • Kubernetes e2e suite.[It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to delete nodes
  • Kubernetes e2e suite.[It] [sig-cloud-provider-gcp] [Disruptive] NodeLease NodeLease deletion node lease should be deleted when corresponding node is deleted

Since when has it been failing?

After #124519

Testgrid link

https://testgrid.k8s.io/sig-release-master-informing#gce-cos-master-serial

Reason for failure (if possible)

provider does not support InstanceGroups

Anything else we need to know?

Support for gce instance groups was removed, so these tests need to be either updated (To test some other functionality) or removed.

Relevant SIG(s)

/sig cloud-provider-gcp

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 8, 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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label May 8, 2024
@Vyom-Yadav
Copy link
Member Author

/sig cloud-provider

@k8s-ci-robot k8s-ci-robot added sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 8, 2024
@aojea
Copy link
Member

aojea commented May 9, 2024

/cc @BenTheElder @aojea

@pacoxu
Copy link
Member

pacoxu commented May 14, 2024

After #124519

@dims @carlory

@aojea
Copy link
Member

aojea commented May 14, 2024

These tests has to be refactored or migrated

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. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider.
Projects
Development

No branches or pull requests

4 participants