Runner: Action branch names with / broken in 2.273.4?

[j3parker]

As of today if our actions come from a branch on a repo with / in the branch name it fails with errors like this:

Unable to resolve action `Brightspace/third-party-actions@actions/checkout`, repository not found

We do this a lot because we mirror third-party-actions into branches in a central repo in our org (more context available in the README).

We're seeing it fail on v2.273.4 runners, at least.

I see a lot of .Split( '/' ) in here, but I haven't finished investigating: https://github.com/actions/runner/compare/v2.273.3...v2.273.4#diff-488a6cefa4a643b9314f32898b46937eR51

[j3parker]

We're seeing this happen in some repos but not others, all with 2.273.4 🤔

[j3parker]

Current runner version: '2.273.4'
Runner name: 'i-01bea0d66428dd4f2'
Machine name: 'ip-10-0-3-21'
Prepare workflow directory
Prepare all required actions
Getting action download info
Failed to resolve action download info. Error: Unable to resolve action `Brightspace/third-party-actions@actions/checkout`, repository not found
Unable to resolve action `Brightspace/third-party-actions@actions/github-script`, repository not found
Retrying in 21 seconds
Failed to resolve action download info. Error: Unable to resolve action `Brightspace/third-party-actions@actions/checkout`, repository not found
Unable to resolve action `Brightspace/third-party-actions@actions/github-script`, repository not found
Retrying in 26.719 seconds

We're seeing it consistently fail in some repos and not in others. The / appears to be important but I'm double checking that.

[j3parker]

This diff fixes a broken repo:

We've reproduced it failing with /s and changing them to - and it appeared to work.

It seems like the problem is sticky per-repo, even after destroying and recreating the runner VMs. Could this be something on the backend? E.g. related to GITHUB_TOKEN. We're seeing it

• Fail in Brightspace/github-actions-infrasctructure
• Work in Brightspace/bdp-ingestion

(etc... both of these are private repos)

[j3parker]

Similar sounding thing: https://github.community/t/setup-job-action-is-failing-on-certain-repos/135118
(they also have /s in their branch name...)

[j3parker]

Here's a job in a public repo that is _not_ using our self-hosted runners but has started failing: https://github.com/Brightspace/brightspace-integration/runs/1200341852?check_suite_focus=true

[iheanyi]

👋🏾 Hello there from the Actions team, thanks for reporting this! I will take a look and see what I can find.

[bricker]

I can confirm this issue, which just started within the last 2 hours.

• When pointing at bricker/github-actions/setup-gcloud@bcr/202007/creds_path, I get the error mentioned in this issue:

Unable to resolve action `bricker/github-actions@bcr/202007/creds_path`, repository not found

• When pointing at bricker/github-actions/setup-gcloud@BCR-creds_path, the action is loaded and runs normally.

[pjquirk]

Sorry for the trouble, we identified a bug in a change we rolled out to the Actions Service that caused this and rolled it back. The runner is fine to continue using as-is. Thanks again for reporting this and let us know if you continue to see the issue!

[j3parker]

Thanks!! It looks like it cleared up.