You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think this ever worked. EIO didn't want to give us a cross-org token that would allow actions in the k3s-io/k3srepo to run things in the rancher/system-agent-installer-k3s repo. Note that we use "${PAT_USERNAME}:${PAT_TOKEN}" to send the dispatch - this token is only valid for repos in the k3s-io org.
The error is a 404 but I think the actual problem is lack of access.
@caroline-suse-rancher Rancher EIO provided us a new token in GH from Rancher org, for now I doing some tests with it to make sure everything is working as expected. Hope this week close this one 🙏
Describe the bug:
Dispatch CI step is failing to create system-agent-installer tag
Steps To Reproduce:
when cutting a new release the dispatch drone step should do two things:
https://github.com/k3s-io/k3s/blob/master/scripts/dispatch#L13-L19
Expected behavior:
dispatch to work properly
Actual behavior:
k3s-upgrade dispatch works however system-agent-installer dispatch reports not_found, example:
https://drone-publish.k3s.io/k3s-io/k3s/1344/7/2
Additional context / logs:
The text was updated successfully, but these errors were encountered: