Skip to content

Failing test(s): TestAccContainer*_withInvalid* #17383

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

Closed

Comments

@melinath
Copy link
Collaborator

melinath commented Feb 23, 2024

Failure rates

  • 100% since 2024-02-21

Impacted tests

  • TestAccContainerCluster_withInvalidAutoscalingProfile
  • TestAccContainerCluster_withInvalidReleaseChannel
  • TestAccContainerNodePool_withInvalidKubeletCpuManagerPolicy

Affected Resource(s)

  • google_container_cluster
  • google_container_node_pool

Nightly build test history

Message(s)

Error: expected cluster_autoscaling.0.autoscaling_profile to be one of ["BALANCED" "OPTIMIZE_UTILIZATION"], got AS_CHEAP_AS_POSSIBLE
Error: expected release_channel.0.channel to be one of ["UNSPECIFIED" "RAPID" "REGULAR" "STABLE"], got CANARY
Error: expected node_config.0.kubelet_config.0.cpu_manager_policy to be one of ["static" "none" ""], got dontexist

GKE changed its error output format - the regexes in these tests need to be updated similar to GoogleCloudPlatform/magic-modules#10034

b/326649670

Copy link

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 Apr 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.