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

CI tests are failing #828

Closed
jpeach opened this issue Aug 25, 2021 · 6 comments
Closed

CI tests are failing #828

jpeach opened this issue Aug 25, 2021 · 6 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@jpeach
Copy link
Contributor

jpeach commented Aug 25, 2021

What happened:

CI test are failing with this error:

`Error from server (Invalid): error when creating "config/crd/v1alpha2/gateway.networking.k8s.io_gatewayclasses.yaml": CustomResourceDefinition.apiextensions.k8s.io "gatewayclasses.gateway.networking.k8s.io" is invalid: metadata.annotations[api-approved.kubernetes.io]: Required value: protected groups must have approval annotation "api-approved.kubernetes.io", see https://github.com/kubernetes/enhancements/pull/1111

What you expected to happen:

Applying CRDs should succeed.

How to reproduce it (as minimally and precisely as possible):

Run CI for any PR.

Anything else we need to know?:

kubernetes/enhancements#1111

@jpeach jpeach added the kind/bug Categorizes issue or PR as related to a bug. label Aug 25, 2021
@robscott
Copy link
Member

This was a dumb hack by me to workaround this (https://github.com/kubernetes-sigs/gateway-api/blob/master/hack/update-codegen.sh#L63), and the precise version is probably causing the issue with #824 since it bumps the version of that tool.

@robscott
Copy link
Member

@jpeach is there a specific PR where CI is failing due to this?

@robscott robscott changed the title Reserved API group needs an approval annotation CI tests are failing Aug 25, 2021
@robscott
Copy link
Member

It looks like both recent PRs have failed CI for the same reason: #829 and #824. My working theory is that the recent updates to test-infra images these tests run on included an update to go v1.17. If this matches my own local development experience, go 1.17 adds an extra line at the start of these generated files. I'm guessing that running codegen with 1.17 would resolve this issue.

@youngnick
Copy link
Contributor

I just installed 1.17, I'll give that a shot.

/assign

@robscott
Copy link
Member

It looks like #830 fixed this, feel free to reopen if I missed anything.

/close

@k8s-ci-robot
Copy link
Contributor

@robscott: Closing this issue.

In response to this:

It looks like #830 fixed this, feel free to reopen if I missed anything.

/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.

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

No branches or pull requests

4 participants