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

[Bug] Inability to trigger workflow retry mechanism due to permission changes #8565

Closed
3 tasks done
chi3316 opened this issue Aug 20, 2024 · 0 comments · Fixed by #8566
Closed
3 tasks done

[Bug] Inability to trigger workflow retry mechanism due to permission changes #8565

chi3316 opened this issue Aug 20, 2024 · 0 comments · Fixed by #8566

Comments

@chi3316
Copy link
Contributor

chi3316 commented Aug 20, 2024

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

Github Action

RocketMQ version

branch : develop

JDK Version

No response

Describe the Bug

The workflow retry mechanism fails to trigger because of recent changes to the repository's action permissions, which now default to read-only. This prevents the GH_TOKEN from having the necessary actions: write permission to trigger the retry mechanism.

Steps to Reproduce

  1. Push a commit to trigger the workflow.
  2. Allow the workflow to fail.
  3. Observe that the retry mechanism is not triggered.

What Did You Expect to See?

The workflow retry mechanism should trigger after a failure, attempting to rerun the workflow

What Did You See Instead?

The workflow retry mechanism does not trigger because the GH_TOKEN does not have the required actions: write permission.

image

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant