actions-runner-controller: System.InvalidOperationException: Not configured @ ...Configuration.ConfigurationManager.LoadSettings()

I’m seeing the failure seen at the end of log in this problem report: https://github.com/microsoft/azure-pipelines-agent/issues/2632

I installed the helm chart: actions-runner-controller-0.8.0 on 3/11/2021.

I looked on the pod(s) and did not see the credential files. The runners always work fine for awhile but eventually get into this state (after roughly 1-8 hours) where they fail with the log errors in the above problem report.

Do I need a new version of the controller? Your runner docker image? Runner?

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 17 (1 by maintainers)

Most upvoted comments

@jwalters-gpsw Hey! I have literally no expertise on the internals of the runner as I’m not a folk from Azure or GitHub. But a quick look on the linked issue makes me think that your runner is too outdated and itw as unable to auto-update.

That’s what I was thinking. I see I’m on an older version of the helm chart. So I’m going to upgrade that. If I still see the problem (which I doubt) I might see if I can get the --once option to actually terminate the pod. I would rather than a “clean” environment from a pod recreation. Thanks!

I updated the controller/runnerdeployments. I’ll follow up next week with whether the issue is resolved.

jwalters-gpsw on Apr 17, 2021

Also, your helm repo seems to be down.

@jwalters-gpsw The project recently transfered owner, are you still configured for the old owner?

callum-tait-pbx on May 3, 2021

Have not seen issue since updating the components. Closing.

jwalters-gpsw on Apr 21, 2021