FSx: New failing acceptance tests after AWS SDK for Go v2 migration

[ewbankkit]

After the migration of the FSx resources to AWS SDK for Go v2 (#38343) there are a few new failing acceptance tests:

=== RUN   TestAccFSxLustreFileSystem_metadataConfig_decrease
=== PAUSE TestAccFSxLustreFileSystem_metadataConfig_decrease
=== CONT  TestAccFSxLustreFileSystem_metadataConfig_decrease
    lustre_file_system_test.go:972: Step 3/3 error: Error running apply: exit status 1
        Error: updating FSX for Lustre File System (fs-099adc19dddae0e35): operation error FSx: UpdateFileSystem, https response error StatusCode: 400, RequestID: d1727609-0072-4cd5-9851-773b3b26709e, BadRequest: Requested metadata IOPS must be greater than the currently provisioned metadata IOPS (3000).
          with aws_fsx_lustre_file_system.test,
          on terraform_plugin_test.tf line 44, in resource "aws_fsx_lustre_file_system" "test":
          44: resource "aws_fsx_lustre_file_system" "test" {
--- FAIL: TestAccFSxLustreFileSystem_metadataConfig_decrease (740.88s)

=== RUN   TestAccFSxOpenZFSFileSystem_rootVolume
=== PAUSE TestAccFSxOpenZFSFileSystem_rootVolume
=== CONT  TestAccFSxOpenZFSFileSystem_rootVolume
    openzfs_file_system_test.go:181: Step 5/5 error: Check failed: Check 4/13 error: aws_fsx_openzfs_file_system.test: Attribute 'root_volume_configuration.0.nfs_exports.#' expected "0", got "1"
--- FAIL: TestAccFSxOpenZFSFileSystem_rootVolume (1304.85s)

=== RUN   TestAccFSxONTAPStorageVirtualMachine_activeDirectoryJoin
=== PAUSE TestAccFSxONTAPStorageVirtualMachine_activeDirectoryJoin
=== CONT  TestAccFSxONTAPStorageVirtualMachine_activeDirectoryJoin
    ontap_storage_virtual_machine_test.go:304: Step 2/2 error: Check failed: Check 4/9 error: aws_fsx_ontap_storage_virtual_machine.test: Attribute 'active_directory_configuration.0.netbios_name' expected "tftest-a3moldu", got "TFTEST-A3MOLDU"
--- FAIL: TestAccFSxONTAPStorageVirtualMachine_activeDirectoryJoin (4279.54s)

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.60.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.