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

Reconcile Broad permissions for eallred #91

Closed
mattmoor opened this issue Feb 11, 2020 · 11 comments · Fixed by #425
Closed

Reconcile Broad permissions for eallred #91

mattmoor opened this issue Feb 11, 2020 · 11 comments · Fixed by #425

Comments

@mattmoor
Copy link
Member

Currently Eric and Paul are members of Knative Admin, but don't hold an official role on the Project.

We are trying to align levels of access with project roles, and this is an instance where we've likely uncovered folks implicitly performing important functions: https://docs.google.com/document/d/1pCLzTfNP5-_Z9taNK0W5hntyKbP4E5DI4-6n16GpyeU/edit#

@mattmoor mattmoor created this issue from a note in Steering Committee backlog (Backlog) Feb 11, 2020
@mattmoor
Copy link
Member Author

I've created a temporary "team" for Eric and Paul under Knative Admins here: https://github.com/orgs/knative/teams/tbd-admins

@vaikas
Copy link
Contributor

vaikas commented Jan 29, 2021

@eallred-google
@paulrossman

Are there any reasons for y'all to still have this level of access? I'd like to make headway on this old issue and this feels like this is no longer necessary. Could you please lmk if this is the case?

@vaikas vaikas moved this from Backlog to In progress in Steering Committee backlog Jan 29, 2021
@vaikas
Copy link
Contributor

vaikas commented Jan 29, 2021

And actually I hit send a little bit too soon. The group only contains @eallred-google.

@vaikas vaikas changed the title Reconcile Broad permissions for eallred and paulrossman Reconcile Broad permissions for eallred Jan 29, 2021
@eallred-google
Copy link

eallred-google commented Feb 1, 2021 via email

@mattmoor
Copy link
Member Author

mattmoor commented Feb 1, 2021

Thanks, @eallred-google

@mattmoor
Copy link
Member Author

mattmoor commented Feb 1, 2021

I sent a (linked) PR for @vaikas to stamp dropping the group and the admins: entry.

@vaikas
Copy link
Contributor

vaikas commented Feb 1, 2021

Thanks @eallred-google PR has been stamped.

Steering Committee backlog automation moved this from In progress to Complete Feb 1, 2021
@vaikas
Copy link
Contributor

vaikas commented Feb 3, 2021

Is something not working correctly or am I just holding things wrong?
I still see this group here in github:
https://github.com/orgs/knative/teams/tbd-admins

And @eallred-google is still a member and tbd-admins is still a member of knative-admin:
https://github.com/orgs/knative/teams/knative-admin/teams

@mattmoor hold up, wait a minute, something ain't right? Or is it?

@vaikas vaikas reopened this Feb 3, 2021
@vaikas vaikas moved this from Complete to In progress in Steering Committee backlog Feb 3, 2021
@mattmoor
Copy link
Member Author

mattmoor commented Feb 3, 2021

Maybe Peribolos doesn't delete teams? 🤔

/assign @chizhg @evankanderson

@vaikas
Copy link
Contributor

vaikas commented Feb 4, 2021

Ok, so looks like this might be an issue. Went looking for the peribolos jobs logs here:
https://prow.knative.dev/view/gs/knative-prow/logs/post-knative-peribolos/1357247051569565696

{"component":"unset","file":"prow/flagutil/github.go:75","func":"k8s.io/test-infra/prow/flagutil.(*GitHubOptions).Validate","level":"warning","msg":"It doesn't look like you are using ghproxy to cache API calls to GitHub! This has become a required component of Prow and other components will soon be allowed to add features that may rapidly consume API ratelimit without caching. Starting May 1, 2020 use Prow components without ghproxy at your own risk! https://github.com/kubernetes/test-infra/tree/master/ghproxy#ghproxy","severity":"warning","time":"2021-02-04T08:38:13Z"}
{"client":"github","component":"unset","file":"prow/github/client.go:594","func":"k8s.io/test-infra/prow/github.(*client).log","level":"info","msg":"Throttle(1200, 100)","severity":"info","time":"2021-02-04T08:38:13Z"}
{"client":"github","component":"unset","file":"prow/github/client.go:594","func":"k8s.io/test-infra/prow/github.(*client).log","level":"info","msg":"GetOrg(knative)","severity":"info","time":"2021-02-04T08:38:13Z"}
{"client":"github","component":"unset","file":"prow/github/client.go:594","func":"k8s.io/test-infra/prow/github.(*client).log","level":"info","msg":"ListOrgInvitations(knative)","severity":"info","time":"2021-02-04T08:38:13Z"}
{"client":"github","component":"unset","file":"prow/github/client.go:594","func":"k8s.io/test-infra/prow/github.(*client).log","level":"info","msg":"User()","severity":"info","time":"2021-02-04T08:38:13Z"}
{"client":"github","component":"unset","file":"prow/github/client.go:594","func":"k8s.io/test-infra/prow/github.(*client).log","level":"info","msg":"ListOrgMembers(knative, admin)","severity":"info","time":"2021-02-04T08:38:13Z"}
{"client":"github","component":"unset","file":"prow/github/client.go:594","func":"k8s.io/test-infra/prow/github.(*client).log","level":"info","msg":"ListOrgMembers(knative, member)","severity":"info","time":"2021-02-04T08:38:13Z"}
{"component":"unset","file":"prow/cmd/peribolos/main.go:202","func":"main.main","level":"fatal","msg":"Configuration failed: failed to configure knative members: all team members/maintainers must also be org members: eallred-google","severity":"fatal","time":"2021-02-04T08:38:16Z"}

@vaikas
Copy link
Contributor

vaikas commented Feb 4, 2021

Ok, after digging at this, peribolos was silently failing, created an issue for that in test-infra.
Verified that this team has now been removed:
https://github.com/orgs/knative/teams/tbd-admins

@vaikas vaikas closed this as completed Feb 4, 2021
Steering Committee backlog automation moved this from In progress to Complete Feb 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

5 participants