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

[Failing Test] Uses kubeadm/kinder to run kubeadm-e2e and e2e tests #79668

Closed
soggiest opened this issue Jul 2, 2019 · 5 comments
Closed

[Failing Test] Uses kubeadm/kinder to run kubeadm-e2e and e2e tests #79668

soggiest opened this issue Jul 2, 2019 · 5 comments
Assignees
@neolit123 @justaugustus
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Milestone
v1.16

Comments

@soggiest
Copy link

soggiest commented Jul 2, 2019

Which jobs are failing:
ci-kubernetes-e2e-kubeadm-kinder-upgrade-stable-master

Which test(s) are failing:
task-01-add-kubernetes-versions
task-11-reset
task-12-delete

Since when has it been failing:
07/02/2019

Testgrid link:
https://testgrid.k8s.io/sig-release-master-informing#kubeadm-kinder-upgrade-stable-master

Reason for failure:

ime="15:40:04" level=debug msg="Running: /usr/bin/docker [docker ps -q -a --no-trunc --filter label=io.k8s.sigs.kind.cluster --format {{.Names}}\\t{{.Label \"io.k8s.sigs.kind.cluster\"}}]"
Error: unknown cluster "kinder-upgrade"
 completed!
 # task-11-reset
kinder do kubeadm-reset --name=kinder-upgrade
 Error: a cluster with the name "kinder-upgrade" does not exists
 exit status 1
 # task-12-delete
kinder delete cluster --name=kinder-upgrade
 Error: unknown cluster "kinder-upgrade"
 exit status 1
 Ran 5 of 13 tasks in 0.000 seconds
FAIL! -- 2 tasks Passed | 3 Failed | 8 Skipped
 see junit-runner.xml and task logs files for more details

Anything else we need to know:
6d8dd21...a807cb6

/cc @kubernetes/sig-cluster-lifecycle
/milestone v1.16
/priority critical-urgent
/kind failing-test
/cc @Verolop @jimangel @soggiest @alenkacz
@soggiest soggiest added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Jul 2, 2019
@k8s-ci-robot k8s-ci-robot added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Jul 2, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.16 milestone Jul 2, 2019
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jul 2, 2019
@soggiest
Copy link
Author

soggiest commented Jul 2, 2019

/sig cluster-lifecycle

@k8s-ci-robot k8s-ci-robot added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jul 2, 2019
@soggiest soggiest mentioned this issue Jul 2, 2019
Closed
@neolit123
Copy link
Member

caused by missing files in GCS buckets:
https://kubernetes.slack.com/archives/C09QZ4DQB/p1562077303458500

/sig testing
/assign

@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Jul 2, 2019
@neolit123
Copy link
Member

after this merged the CI should stabilize:
kubernetes/release#814
please check again tomorrow.

@justaugustus justaugustus mentioned this issue Jul 4, 2019
Closed
8 tasks
@justaugustus
Copy link
Member

This was caused by changes to the build/release tooling, which have since been reverted (kubernetes/release#814).

Here is the first green run of the tests since the k/release revert:

Closing this out, but continued discussion on tooling/process improvement is happening here: kubernetes/release#816
/close
/assign
/sig release

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Closing this issue.

In response to this:

This was caused by changes to the build/release tooling, which have since been reverted (kubernetes/release#814).

Here is the first green run of the tests since the k/release revert:

Closing this out, but continued discussion on tooling/process improvement is happening here: kubernetes/release#816
/close
/assign
/sig release

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.

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@neolit123 neolit123

@justaugustus justaugustus

Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
v1.16
Development

No branches or pull requests
4 participants
@neolit123 @justaugustus @soggiest @k8s-ci-robot