azurerm_redhat_openshift_cluster - upgrade API version from 2023-09-04 to 2025-07-25

[teowa]

Community Note

• Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
• Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review

Description

azurerm_redhat_openshift_cluster - upgrade API version from 2023-09-04 to 2025-07-25

PR Checklist

• I have followed the guidelines in our Contributing Documentation.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
• I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
• I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
  For example: “resource_name_here - description of change e.g. adding property new_property_name_here”

Changes to existing Resource / Data Source

• I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
• I have written new tests for my resource or datasource changes & updated any relevant documentation.
• I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
• (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

Testing

• My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

• azurerm_redhat_openshift_cluster - upgrade API version from 2023-09-04 to 2025-07-25 property [GH-00000]

This is a (please select all that apply):

• Bug Fix
• New Feature (ie adding a service, resource, or data source)
• Enhancement
• Breaking Change

Related Issue(s)

Fixes #0000

AI Assistance Disclosure

• AI Assisted - This contribution was made by, or with the assistance of, AI/LLMs

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the provider.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

Note

If this PR changes meaningfully during the course of review please update the title and description as required.

[mstroob]

/test

[hc-github-team-tf-azure]

Build: 640341
PR: #32029

Total: 9
Passed: 3
Failed: 6

Test Details

Status	Test Name	Duration
❌ FAIL	TestAccOpenShiftCluster_update	1189.42s
❌ FAIL	TestAccOpenShiftCluster_userDefinedRouting	1190.22s
❌ FAIL	TestAccOpenShiftCluster_private	1191.92s
❌ FAIL	TestAccOpenShiftCluster_requiresImport	1268.28s
❌ FAIL	TestAccOpenShiftCluster_basicResourceGroupName	1268.92s
❌ FAIL	TestAccOpenShiftCluster_basicWithFipsEnabled	1277.06s
✅ PASS	TestAccOpenShiftCluster_basic	3513.49s
✅ PASS	TestAccOpenShiftCluster_preconfiguredNetworkSecurityGroup	3704.49s
✅ PASS	TestAccOpenShiftCluster_encryptionAtHost	4061.28s

[mstroob]

Hi @teowa I ran the tests in the comment above, and see a lot of failures with

CreateOrUpdate: polling failed: the Azure API returned the following error: Status: "Failed" Code: "InternalServerError" Message: "Internal server error." Activity Id: ""
can you please have a look at that

[teowa]

I have reported this to the service team and am waiting for their response.

[0kashi]

I believe that the underlying issue is not related to the module update but rather something unrelated to this that is currently being worked on. Is it possible to accept this based on the facts related to module updates only?