v3 Azure rack - Unsupported TF module argument causing Azure Rack deploy to fail

[SonOfBytes]

Installing a new Azure rack from CLI or Console results in a terraform fail.

terraform/fluentd/elasticsearch/main.tf does not have resolver argument which is referred to by terraform/api/azure/main.tf

Error: Unsupported argument

on .terraform/modules/system/terraform/api/azure/main.tf line 40, in module "fluentd":
40: resolver = var.resolver

[beastawakens]

We're actually looking into Azure installation issues right now! 😊

[SonOfBytes]

I just noticed another error in the logs - similar but different module

Error: Missing required argument

on .terraform/modules/system/terraform/api/azure/main.tf line 44, in module "k8s":
44: module "k8s" {

The argument "resolver" is required, but no definition was found.

[tito0224]

Hi, I'm hitting this issue as well when trying to deploy a rack on azure via the web console.

When I try to deploy locally I get this:

Error: Incompatible provider version

Provider registry.terraform.io/hashicorp/azuread v0.11.0 does not have a package available for your current platform, darwin_arm64.

Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other versions of this provider may have
different platforms supported.


Error: Incompatible provider version

Provider registry.terraform.io/hashicorp/template v2.2.0 does not have a package available for your current platform, darwin_arm64.

Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other versions of this provider may have
different platforms supported.

Does the cli support Apple arm64?

Thanks

[SonOfBytes]

I does this have a resolution time - this is basically unusable in Azure as I can't deploy any racks.

[heronrs]

Hello, thanks for all the input on this.
We were able to fix all the tf related issues but there's another problem we need to fix first.
Azure only supports k8s clusters with the containerd runtime but our current rack implementation is based on docker so we are working on a docker -> containerd migration first
We'll keep you updated when we have more news around fixing the Azure install.