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.

Sign up for GitHub

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

Jump to bottom

[flake] TestAccPrometheusOperator can conflict with TestRancher in SSA mode #2482

Closed
lblackstone opened this issue Jun 29, 2023 · 0 comments · Fixed by #2515
Closed

[flake] TestAccPrometheusOperator can conflict with TestRancher in SSA mode #2482

lblackstone opened this issue Jun 29, 2023 · 0 comments · Fixed by #2515
Assignees
@lblackstone
Labels
impact/flaky-test A test that is unreliable kind/bug Some behavior is incorrect or out of spec kind/engineering Work that is not visible to an external user resolution/fixed This issue was fixed
Milestone
0.91

Comments

@lblackstone
Copy link
Member

Problem description

Both of these tests install some CRDs that can clash due to parallel test runs.

Errors & Logs

  kubernetes:apiextensions.k8s.io/v1:CustomResourceDefinition (servicemonitors.monitoring.coreos.com):
    error: resource servicemonitors.monitoring.coreos.com was not successfully created by the Kubernetes API server : Server-Side Apply field conflict detected. see https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-conflicts-on-existing-resources for troubleshooting help
    : Apply failed with 1 conflict: conflict with "rancher" using apiextensions.k8s.io/v1: .spec.versions

  kubernetes:apiextensions.k8s.io/v1:CustomResourceDefinition (prometheusrules.monitoring.coreos.com):
    error: resource prometheusrules.monitoring.coreos.com was not successfully created by the Kubernetes API server : Server-Side Apply field conflict detected. see https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-conflicts-on-existing-resources for troubleshooting help
    : Apply failed with 1 conflict: conflict with "rancher" using apiextensions.k8s.io/v1: .spec.versions

  pulumi:pulumi:Stack (prometheus-operator-p-it-fv-az449-4-prometheus-4e7e0fdd):
    error: update failed

  kubernetes:apiextensions.k8s.io/v1:CustomResourceDefinition (alertmanagers.monitoring.coreos.com):
    error: resource alertmanagers.monitoring.coreos.com was not successfully created by the Kubernetes API server : Server-Side Apply field conflict detected. see https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-conflicts-on-existing-resources for troubleshooting help
    : Apply failed with 1 conflict: conflict with "rancher" using apiextensions.k8s.io/v1: .spec.versions

Affected product version(s)

Reproducing the issue

Suggestions for a fix
@lblackstone lblackstone added kind/bug Some behavior is incorrect or out of spec kind/engineering Work that is not visible to an external user impact/flaky-test A test that is unreliable labels Jun 29, 2023
@lblackstone lblackstone mentioned this issue Jul 21, 2023
Merged
@lblackstone lblackstone self-assigned this Jul 21, 2023
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Jul 21, 2023
@mikhailshilkov mikhailshilkov added this to the 0.91 milestone Jul 25, 2023
@lblackstone lblackstone mentioned this issue Aug 7, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lblackstone lblackstone

Labels
impact/flaky-test A test that is unreliable kind/bug Some behavior is incorrect or out of spec kind/engineering Work that is not visible to an external user resolution/fixed This issue was fixed
Projects
None yet
Milestone
0.91
Development

Successfully merging a pull request may close this issue.

[internal] Fix parallel test flake pulumi/pulumi-kubernetes
3 participants
@mikhailshilkov @lblackstone @pulumi-bot