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

Kusto authentication failures #1951

Closed
3 tasks
riarenas opened this issue Feb 5, 2024 · 5 comments
Closed
3 tasks

Kusto authentication failures #1951

riarenas opened this issue Feb 5, 2024 · 5 comments

Comments

@riarenas
Copy link
Member

riarenas commented Feb 5, 2024

We are seeing some errors related to Kusto authentication.

Kusto client failed to perform AAD application authentication. This is not a Kusto service error. Please review your application credentials.

Release Note Category

  • Feature changes/additions
  • Bug fixes
  • Internal Infrastructure Improvements

Release Note Description

@riarenas
Copy link
Member Author

riarenas commented Feb 5, 2024

This was caused by a mistake while rotating a client secret for the Nethelix Entra application which has already been fixed. I'll use this issue as the root cause for any related failures and to monitor recovery.

@riarenas
Copy link
Member Author

riarenas commented Feb 5, 2024

Helix jobs sent while this was ongoing resulted in HTTP 500s when posting the job, with a log similar to:

Microsoft.DotNet.Helix\Sdk\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(68,5): error : RestApiException`1: The response contained an invalid status code 500 Internal Server Error 

@riarenas
Copy link
Member Author

riarenas commented Feb 5, 2024

I'm still seeing these issues. Checking.

@riarenas
Copy link
Member Author

riarenas commented Feb 5, 2024

A couple of secrets that depended on the secret that was cycled incorrectly were broken as part of this as well. We have a backlog of older messages that need to be processed first, but I'm starting to see recovery.

@riarenas riarenas self-assigned this Feb 5, 2024
@riarenas
Copy link
Member Author

riarenas commented Feb 6, 2024

All the fallout from this seems to have been fixed. Closing

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

No branches or pull requests

1 participant