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

[BUG] - Azure NoRegisteredProviderFound Error #2374

Closed
Adam-D-Lewis opened this issue Apr 1, 2024 · 0 comments · Fixed by #2370
Closed

[BUG] - Azure NoRegisteredProviderFound Error #2374

Adam-D-Lewis opened this issue Apr 1, 2024 · 0 comments · Fixed by #2370
Assignees
Labels
type: bug 🐛 Something isn't working
Milestone

Comments

@Adam-D-Lewis
Copy link
Member

Describe the bug

Azurerm was throwing the following error on deployment in eastus2 region when updating a cluster from 2024.1.1 to 2024.3.3.

Error: retrieving Cluster: (Managed Cluster Name "nebari-dev" / Resource Group "my-resourcegroup"): 
containerservice.ManagedClustersClient#Get: Failure respond ing to request: StatusCode=400 -- 
Original Error: autorest/azure: Service returned an error. Status=400 Code="NoRegisteredProviderFound" 
Message="No registered resource provider found for location 'eastus2' and API version '2022-03-02-preview' for type 'managedClusters'.

Updating azurerm provider fixed the issue. Fixed by #2370

Expected behavior

no error

OS and architecture in which you are running Nebari

Linux 2023.3.3

How to Reproduce the problem?

See above

Command output

No response

Versions and dependencies used.

No response

Compute environment

None

Integrations

No response

Anything else?

No response

@Adam-D-Lewis Adam-D-Lewis added type: bug 🐛 Something isn't working needs: triage 🚦 Someone needs to have a look at this issue and triage labels Apr 1, 2024
@Adam-D-Lewis Adam-D-Lewis changed the title [BUG] - <title> [BUG] - Azure NoRegisteredProviderFound Error Apr 1, 2024
@Adam-D-Lewis Adam-D-Lewis self-assigned this Apr 1, 2024
@Adam-D-Lewis Adam-D-Lewis removed the needs: triage 🚦 Someone needs to have a look at this issue and triage label Apr 1, 2024
@Adam-D-Lewis Adam-D-Lewis mentioned this issue Apr 1, 2024
10 tasks
@marcelovilla marcelovilla added this to the Next release milestone Apr 1, 2024
@github-project-automation github-project-automation bot moved this from New 🚦 to Done 💪🏾 in 🪴 Nebari Project Management Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug 🐛 Something isn't working
Projects
Development

Successfully merging a pull request may close this issue.

2 participants