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

Travis CI is failing with Kubernetes 1.16 #963

Closed
roycaihw opened this issue Sep 23, 2019 · 4 comments · Fixed by #966
Closed

Travis CI is failing with Kubernetes 1.16 #963

roycaihw opened this issue Sep 23, 2019 · 4 comments · Fixed by #966
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@roycaihw
Copy link
Member

e.g.

  1. dynamic client is failing with the following error, we should specify the version (v1beta1) in the test
ResourceNotUniqueError: Multiple matches found for {'kind': 'CustomResourceDefinition'}: [<Resource(apiextensions.k8s.io/v1beta1/customresourcedefinitions)>, <Resource(apiextensions.k8s.io/v1/customresourcedefinitions)>]
  1. utils test is failing creating apps/extensions APIs with the following error, but I haven't seen upstream API change that could cause this
FailToCreateError: Error from server (Not Found): {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}
@roycaihw roycaihw added the kind/bug Categorizes issue or PR as related to a bug. label Sep 23, 2019
@roycaihw
Copy link
Member Author

/assign @fabianvf @micw523

@k8s-ci-robot
Copy link
Contributor

@roycaihw: GitHub didn't allow me to assign the following users: fabianvf.

Note that only kubernetes-client members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @fabianvf @micw523

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.

@micw523
Copy link
Contributor

micw523 commented Sep 24, 2019

It’s looking like apps/v1beta1 is also gone in k8s v1.16. The CI failure first appeared when the exit code test was added and the master branch build failed, since minikube got updated to v1.4 which corresponds to k8s v1.16.

There are a bunch of things to be fixed in the tests - I’ll try churn them out. I may have to fix the k8s version to v1.15 when I prepare the patches and change the version back, since the automatically generated client still contains extensions/v1beta1 and apps/v1beta1.

@roycaihw
Copy link
Member Author

roycaihw commented Sep 24, 2019

apps/v1beta1 is also gone in k8s v1.16

could you link to the upstream change? I checked the openapi spec and didn't see that

Ref kubernetes/kubernetes#70672

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants