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

azurerm_kubernetes_cluster - maintenance_window_auto_upgrade is not refreshing #26895

Closed
1 task done
clarkperkins opened this issue Jul 31, 2024 · 1 comment · Fixed by #26915
Closed
1 task done

Comments

@clarkperkins
Copy link

clarkperkins commented Jul 31, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", 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.7.1

AzureRM Provider Version

3.111.0

Affected Resource(s)/Data Source(s)

azurerm_kubernetes_cluster

Terraform Configuration Files

resource "azurerm_kubernetes_cluster" "cluster" {
  name = var.cluster_name

  resource_group_name = var.resource_group.name
  location            = var.resource_group.location

  sku_tier = "Standard"

  maintenance_window_auto_upgrade {
    frequency   = "Weekly"
    interval    = 1
    duration    = 4
    day_of_week = "Sunday"
    start_time  = "07:00"
    utc_offset  = "+00:00"
  }

  maintenance_window_node_os {
    frequency   = "Weekly"
    interval    = 1
    duration    = 4
    day_of_week = "Sunday"
    start_time  = "07:00"
    utc_offset  = "+00:00"
  }
}

Debug Output/Panic Output

From the terraform plan debug output:

2024-07-31T17:10:37.633-0500 [DEBUG] provider.terraform-provider-azurerm_v3.111.0_x5: AzureRM Response for https://management.azure.com/subscriptions/<sub>/resourceGroups/<rg>/providers/Microsoft.          ContainerService/managedClusters/<cluster>/maintenanceConfigurations/aksManagedAutoUpgradeSchedule?api-version=2023-09-02-preview:
HTTP/2.0 404 Not Found^M
Content-Length: 424^M
Cache-Control: no-cache^M
Content-Type: application/json^M
Date: Wed, 31 Jul 2024 22:10:36 GMT^M
Expires: -1^M
Pragma: no-cache^M
Strict-Transport-Security: max-age=31536000; includeSubDomains^M
X-Cache: CONFIG_NOCACHE^M
X-Content-Type-Options: nosniff^M
X-Ms-Correlation-Request-Id: <redacted>^M
X-Ms-Ratelimit-Remaining-Subscription-Global-Reads: 3747^M
X-Ms-Ratelimit-Remaining-Subscription-Reads: 247^M
X-Ms-Request-Id: <redacted>^M
X-Ms-Routing-Request-Id: EASTUS2:<redacted>^M
X-Msedge-Ref: Ref A: <redacted> Ref B: <redacted> Ref C: <redacted>^M
^M
{
  "code": "NotFound",
  "details": [
   {
    "code": "Unspecified",
    "message": "rpc error: code = NotFound desc = Maintenance configuration not found"
   }
  ],
  "message": "Could not find the maintenance configuration: aksManagedAutoUpgradeSchedule in subscription: <sub>, resourceGroup: <rg>, resourceName: <cluster>.",
  "subcode": "GetMaintenanceConfiguration_NotFound"
 }: timestamp=2024-07-31T17:10:37.632-0500

Expected Behaviour

A terraform apply should replace maintenance window configurations that were manually removed.

Actual Behaviour

Terraform is not replacing removed maintenance window configurations.

Steps to Reproduce

  1. terraform apply
  2. Manually remove the maintenance_window_auto_upgrade configuration in the azure portal
  3. terraform plan shows no changes

Important Factoids

Azure eastus2

References

No response

Copy link

github-actions bot commented Dec 1, 2024

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.