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

Pin Admiral to v0.13.1 #2032

Merged
merged 1 commit into from
Sep 21, 2022
Merged

Pin Admiral to v0.13.1 #2032

merged 1 commit into from
Sep 21, 2022

Conversation

submariner-bot
Copy link
Contributor

Pin Admiral to v0.13.1

@submariner-bot
Copy link
Contributor Author

🤖 I see this PR is using the local branch workflow, ignoring it on my side, have fun!
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

@submariner-bot submariner-bot enabled auto-merge (squash) September 21, 2022 14:06
@mkolesnik mkolesnik added the ready-to-test When a PR is ready for full E2E testing label Sep 21, 2022
dfarrell07 added a commit to dfarrell07/releases that referenced this pull request Sep 21, 2022
After submariner-io#470, the release GitHub Action workflow is failing to add labels
to PRs.

```
gh pr edit --add-label e2e-all-k8s \
submariner-io/submariner#2032
GraphQL: Your token has not been granted the required scopes to execute
this query. The 'login' field requires one of the following scopes:
['read:org'], but your token has only been granted the:
['admin:repo_hook', 'delete:packages', 'notifications', 'repo',
'workflow', 'write:discussion', 'write:packages'] scopes. Please modify
your token's scopes at: https://github.com/settings/tokens.
INFO: Didn't label 'e2e-all-k8s', continuing without it.
```

The only explination I can find of that permisson is:

> read:org Read org and team membership, read org projects

I can also see that permission is a subset of admin:org. It seems to be
different than `read:project Read access of projects` somehow.

It's not clear which GITHUB_TOKEN permisison we can set relates to those
token permissions.

docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs

It doesn't seem possible set all permissions to read and only some to
write, as setting any specific permission overrides read-all.

For now, trying the only permission that seems even vaguely related.

Signed-off-by: Daniel Farrell <[email protected]>
@skitt
Copy link
Member

skitt commented Sep 21, 2022

This is failing because Shipyard 0.13.1 runs go mod tidy without -compat=1.17 :-(.

Signed-off-by: Automated Release <[email protected]>
@tpantelis
Copy link
Contributor

This is failing because Shipyard 0.13.1 runs go mod tidy without -compat=1.17 :-(.

I fixed it up manually (I hope 😄 ).

skitt pushed a commit to submariner-io/releases that referenced this pull request Sep 21, 2022
After #470, the release GitHub Action workflow is failing to add labels
to PRs.

```
gh pr edit --add-label e2e-all-k8s \
submariner-io/submariner#2032
GraphQL: Your token has not been granted the required scopes to execute
this query. The 'login' field requires one of the following scopes:
['read:org'], but your token has only been granted the:
['admin:repo_hook', 'delete:packages', 'notifications', 'repo',
'workflow', 'write:discussion', 'write:packages'] scopes. Please modify
your token's scopes at: https://github.com/settings/tokens.
INFO: Didn't label 'e2e-all-k8s', continuing without it.
```

The only explination I can find of that permisson is:

> read:org Read org and team membership, read org projects

I can also see that permission is a subset of admin:org. It seems to be
different than `read:project Read access of projects` somehow.

It's not clear which GITHUB_TOKEN permisison we can set relates to those
token permissions.

docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs

It doesn't seem possible set all permissions to read and only some to
write, as setting any specific permission overrides read-all.

For now, trying the only permission that seems even vaguely related.

Signed-off-by: Daniel Farrell <[email protected]>
Copy link
Member

@dfarrell07 dfarrell07 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't disable auto-merge, so trying to vote no since E2E is failing.

@dfarrell07
Copy link
Member

[cluster2] Failed to install kind with OVN

Copy link
Member

@dfarrell07 dfarrell07 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently it's expected for these jobs to be failing on 0.13, or at least they also failed for the Shipyard bump and we're continuing the release.

@submariner-bot submariner-bot merged commit 896697e into release-0.13 Sep 21, 2022
@mkolesnik mkolesnik deleted the pin_admiral branch November 8, 2022 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated ready-to-test When a PR is ready for full E2E testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants