Skip to content

failing jobs: ci-kubernetes-build-deprecated (and release-branch variants) #103647

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Closed
spiffxp opened this issue Jul 12, 2021 · 7 comments · Fixed by kubernetes/test-infra#22864
Closed

failing jobs: ci-kubernetes-build-deprecated (and release-branch variants) #103647

spiffxp opened this issue Jul 12, 2021 · 7 comments · Fixed by kubernetes/test-infra#22864
Assignees
@spiffxp
Labels
area/test 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/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
v1.22

Comments

@spiffxp
Copy link
Member

spiffxp commented Jul 12, 2021

Which jobs are failing:

  • ci-kubernetes-build-deprecated
  • ci-kubernetes-build-deprecated-1-21
  • ci-kubernetes-build-1-20-deprecated
  • ci-kubernetes-build-1-19-deprecated

Which test(s) are failing:

n/a

Since when has it been failing:

Testgrid link:

Reason for failure:

TBD but likely related to the merge of kubernetes/test-infra#22840 or its followup PR's

Anything else we need to know:

/sig testing
/sig release
/priority critical-urgent
/area test
/milestone v1.22
/assign
@spiffxp spiffxp added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Jul 12, 2021
@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/release Categorizes an issue or PR as relevant to SIG Release. labels Jul 12, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.22 milestone Jul 12, 2021
@k8s-ci-robot k8s-ci-robot added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. area/test needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 12, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Jul 12, 2021

/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 Jul 12, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Jul 12, 2021 

$ curl https://storage.googleapis.com/kubernetes-jenkins/logs/ci-kubernetes-build-deprecated/1413607604885655552/podinfo.json | jq -r '.pod.status.containerStatuses[0].state.terminated.message'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 21308  100 21308    0     0   630k      0 --:--:-- --:--:-- --:--:--  630k
fetching https://github.com/kubernetes/test-infra
origin/HEAD set to master
From https://github.com/kubernetes/test-infra
 * branch                  master     -> FETCH_HEAD
   0f9c540d1e..5168b645e7  master     -> origin/master
HEAD is now at 5168b645e7 Merge pull request #22840 from spiffxp/jobs-use-k8s-release-dev
Docker in Docker enabled, initializing...
================================================================================
Starting Docker: docker.
Waiting for docker to be ready, sleeping for 1 seconds.
================================================================================
Done setting up docker in docker.
Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
fatal: not a git repository (or any of the parent directories): .git
+ WRAPPED_COMMAND_PID=199
+ wait 199
+ ./test-infra/jenkins/bootstrap.py --job=ci-kubernetes-build-deprecated --service-account=/etc/service-account/service-account.json --upload=gs://kubernetes-jenkins/logs --repo=k8s.io/kubernetes --repo=k8s.io/release --root=/go/src --timeout=240 --scenario=kubernetes_build --release=kubernetes-release-dev -- --allow-dup --extra-version-markers=k8s-master --registry=gcr.io/kubernetes-ci-images
usage: bootstrap.py [-h] [--root ROOT] [--timeout TIMEOUT] [--compress]
                    [--repo REPO] [--bare] --job JOB [--upload UPLOAD]
                    [--service-account SERVICE_ACCOUNT] [--ssh SSH]
                    [--git-cache GIT_CACHE] [--clean] [--scenario SCENARIO]
bootstrap.py: error: unrecognized arguments: --release=kubernetes-release-dev
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
+ EXIT_VALUE=2
+ set +o xtrace
Stopping Docker: docker.
================================================================================
Done cleaning up after docker in docker

Looks like maybe the --release needs to be moved to get picked up by whatever bootstrap.py is invoking. Also, having a total lack of logs when bootstrap's default entrypoint fails is a fun failure mode. Ever more reason to stop using it (ref: kubernetes/test-infra#20760)

@spiffxp spiffxp mentioned this issue Jul 12, 2021
Merged
@spiffxp
Copy link
Member Author

spiffxp commented Jul 12, 2021

kubernetes/test-infra#22864 should resolve, will hold open until we see successful job runs post-merge

@spiffxp spiffxp mentioned this issue Jul 12, 2021
Merged
@spiffxp
Copy link
Member Author

spiffxp commented Jul 13, 2021

/reopen
I could have sworn I didn't use an auto-closing keyword...

@k8s-ci-robot
Copy link
Contributor

@spiffxp: Reopened this issue.

In response to this:

/reopen
I could have sworn I didn't use an auto-closing keyword...

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 reopened this Jul 13, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Jul 13, 2021

/close
...aaand closing again, I see green runs for all of the affected builds:

@k8s-ci-robot
Copy link
Contributor

@spiffxp: Closing this issue.

In response to this:

/close
...aaand closing again, I see green runs for all of the affected builds:

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.

This was referenced Jul 13, 2021
Merged
Closed
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@spiffxp spiffxp

Labels
area/test 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/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
v1.22
Development

Successfully merging a pull request may close this issue.

config/jobs: fix kubernetes deprecated build jobs spiffxp/test-infra
2 participants
@spiffxp @k8s-ci-robot