azurerm_maintenance_configuration fails when assigning more than one maintenance configuration: Confirm API version

[A1lard]

Is there an existing issue for this?

• [X] I have searched the existing issues

Community Note

• Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

1.6.3

AzureRM Provider Version

3.79.0

Affected Resource(s)/Data Source(s)

maintenance configuration assignment

Terraform Configuration Files

resource "azurerm_maintenance_configuration" "definition_updates" {
  name                      = "Definition_Updates"
  resource_group_name       = module.resource_group.output_resource_group[0].name
  location                  = module.resource_group.output_resource_group[0].location
  scope                     = "InGuestPatch"
  in_guest_user_patch_mode  = "User"

  window {
    start_date_time         = "2022-10-25 01:00"
    duration                = "03:00"
    time_zone               = "W. Europe Standard Time"
    recur_every             = "6Hour"
  }

  install_patches {
    reboot = "IfRequired"

    windows {
      classifications_to_include = ["Definition"]
    }
  }
}

resource "azurerm_maintenance_assignment_virtual_machine" "patch_window" {
  location                     = var.location
  maintenance_configuration_id = (
    var.maintenance_configuration == "Ring_0" ? module.variables.azurerm_maintenance_configuration_patch_window_ring_0_id : 
      (var.maintenance_configuration == "Ring_1" ? module.variables.azurerm_maintenance_configuration_patch_window_ring_1_id : 
        (var.maintenance_configuration == "Ring_2" ? module.variables.azurerm_maintenance_configuration_patch_window_ring_2_id : ""
        )
      )
    )
  virtual_machine_id           = azurerm_windows_virtual_machine.virtual_machine.id
}
resource "azurerm_maintenance_assignment_virtual_machine" "Definition_Updates" {
  location                     = var.location
  maintenance_configuration_id = module.variables.azurerm_maintenance_configuration_definition_updates
  virtual_machine_id           = azurerm_windows_virtual_machine.virtual_machine.id
}

Debug Output/Panic Output

Plan: 2 to add, 0 to change, 0 to destroy.
module.virtualmachine2.azurerm_maintenance_assignment_virtual_machine.definition_updates: Creating...
module.virtualmachine.azurerm_maintenance_assignment_virtual_machine.definition_updates: Creating...
╷
│ Error: checking for presence of existing Scoped Configuration Assignment (Scope: "/subscriptions/*ID*/resourceGroups/*resourcegroup*/providers/Microsoft.Compute/virtualMachines/*VM*"

│ Configuration Assignment Name: "Definition_Updates"): configurationassignments.ConfigurationAssignmentsClient#Get: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="InvalidResource" Message="Invalid configurationAssignmentName: Definition_Updates. Confirm api version."
│ 
│   with module.virtualmachine.azurerm_maintenance_assignment_virtual_machine.definition_updates,
│   on ../../modules/virtual_machine/maintenance_assignment.tf line 15, in resource "azurerm_maintenance_assignment_virtual_machine" "definition_updates":
│   15: resource "azurerm_maintenance_assignment_virtual_machine" "definition_updates" {
│

Expected Behaviour

The expected behaviour is that the maintenance configuration named "Definition_Updates" is assigned to the vm's.

Actual Behaviour

Error during the plan stage mentioning: Confirm API version while checking the presence of an existing scope.

Steps to Reproduce

When I manually remove the vm from the maintenance assignment on the tenant and run our main code I get the error "Confirm API version"

The issue occurs when trying to add 2 different maintenance configurations on 1 vm. When I remark one of the two maintenance assignments I dont get the code but when I want to add both of our maintenance assignments I get the error: Confirm API version.

Things I tried to fix this issue:

• Use an older version of azurerm and azapi.
• Rename the maintenance configuration
• Create a new maintenace config
• Upper/lower cases in the names and variables

Important Factoids

No response

References

No response

[rob31231232]

Same issue here

[rob31231232]

Looks like the same issue as #20397 but now with an other error message. @ziyeqf last time you solved this issue. Maybe you know why this happends?

[tiwonl]

Same issue here!

[ziyeqf]

Hi @A1lard, thanks for reporting.

I can reproduce your issue. We are reaching out to maintenance team to diagnostic. Will update here once we get a solution.

Thanks

[Kockieee]

Any update on this?

[ziyeqf]

Any update on this?

It's will be updated on the service side, and it's still in progress.

[ppiorkow]

Any update on this?

Ps. I have same issue with terraform v1.6.1, hashicorp/azurerm v3.88.0.

[ziyeqf]

Any update on this?

Ps. I have same issue with terraform v1.6.1, hashicorp/azurerm v3.88.0.

Hi @ppiorkow, sorry for the inconvenience, the fix has not been released on the service yet, have push the service team to release that.

[RemiHG]

Hi, If that can help to escalade, I also have the same issue. Terraform v1.2.4, hashicorp/azurerm v3.67.0 Thanks to have a look. Rémi

[A1lard]

@ziyeqf Is it possible to tell when this fix will be released?

[ziyeqf]

Hi @A1lard, per our testing the issue has been fixed. Could you please give it another try? And if the issue is fixed please close this GIthub issue.

Thanks!

[r-anis]

https://discuss.hashicorp.com/t/assigning-maintenance-configuration-to-multiple-existing-virtual-machines/66397 seems resolved the issue.