-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
BrokerMigration message received is rolling out that might cause a downtime until implementation #186
Comments
Starting from yesterday evening, my self-hosted runners do not pick up the jobs anymore, e.g. see https://github.com/cppfw/opros/actions/runs/9785008298 Could this be related to this breaking change? |
Yes this is indeed possible, but I need the runner log to be certain If this is the case access to an repo of your org would help me, otherwise I'm still waiting beeing affected. I assume all repos of your org has that feature enabled on the backend even if you would create a temporary one for me |
The log might contain a |
My minecraft-linux org also got the update [2024-07-04 09:06:11Z INFO MessageListener] BrokerMigration message received. Polling Broker for messages... However not my self-hosted runners |
For one of my runners, these are the only logs I have for today:
|
Recovering from GitHub Outage might require runner service restart, not shure otherwise |
I restarted the runner service, but it didn't help |
I have no idea what happend on your end. Are newly registred runners also broken for you? The runner has an Registering runners and running jobs is still working on my user and org, so this change mentioned in my original post has not been fully rolled out to me yet |
Maybe the breaking change is not involved here and the problem is something else... I'll try to observe more. |
@igagis FWIW We're seeing the same thing. We only see |
My problem is gone now, perhaps it was some temporary outage of something, not related to this breaking change. |
No such luck here. Fingers crossed it fixes itself for us too. |
Thanks to @igagis this could be solved just before my cron job alert system has been impacted and sent an alert As of one hour ago I see these log entries of v0.8.0, this means this has rolled out to my private test repo a few hours after I finished the update
|
To reliable implement this, I need access to the rollout of the service update.
Found in this behavior change issue: actions/runner#3366 (comment)
The text was updated successfully, but these errors were encountered: