Skip to content

Tekton resource creation fails intermittently - trying to create resources twice? #6952

Description

@ocofaigh

I think this is a long standing issue, but I’m seeing the creation of tekton properties and triggers failing with the errors:

  • The field ''name'' must be unique.
  • CreateTektonPipelinePropertiesWithContext failed: Property of the same name

My guess is that terraform is creating these resources, but perhaps the provider timed out waiting for them to create and retried? And then the retry fails as these resources were actually created?

I understand that without debug logs, this cannot be proven, but reproducing this with debug logs enabled is tricky, as it doesn’t happen all the time. Wondering if someone could take a look at the log in the provider to see if my theory could be valid?

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 "+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
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform IBM Provider Version

v1.13.4

Affected Resource(s)

  • ibm_cd_tekton_pipeline_property
  • ibm_cd_tekton_pipeline_trigger

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please share a link to the ZIP file.

Debug Output

2026/08/11 11:04:25 Terraform apply | Error: ---
 2026/08/11 11:04:25 Terraform apply | id: terraform-17e6f3f1
 2026/08/11 11:04:25 Terraform apply | summary: 'CreateTektonPipelineTriggerWithContext failed: The field ''name'' must be
 2026/08/11 11:04:25 Terraform apply |   unique.'
 2026/08/11 11:04:25 Terraform apply | severity: error
 2026/08/11 11:04:25 Terraform apply | resource: ibm_cd_tekton_pipeline_trigger
 2026/08/11 11:04:25 Terraform apply | operation: create
 2026/08/11 11:04:25 Terraform apply | component:
 2026/08/11 11:04:25 Terraform apply |   name: github.com/IBM-Cloud/terraform-provider-ibm
 2026/08/11 11:04:25 Terraform apply |   version: 2.5.0
 2026/08/11 11:04:25 Terraform apply | ---
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |   with module.workload["ContainerImage-skupper-network-observer-2-2-ubi9"].ibm_cd_tekton_pipeline_trigger.manual_trigger,
 2026/08/11 11:04:25 Terraform apply |   on .terraform/modules/workload/modules/workload-ibm-cloud-onboarding/main.tf line 163, in resource "ibm_cd_tekton_pipeline_trigger" "manual_trigger":
 2026/08/11 11:04:25 Terraform apply |  163: resource "ibm_cd_tekton_pipeline_trigger" "manual_trigger" {
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply | Error: ---
 2026/08/11 11:04:25 Terraform apply | id: terraform-b323781c
 2026/08/11 11:04:25 Terraform apply | summary: 'CreateTektonPipelinePropertiesWithContext failed: Property of the same name
 2026/08/11 11:04:25 Terraform apply |   exists.'
 2026/08/11 11:04:25 Terraform apply | severity: error
 2026/08/11 11:04:25 Terraform apply | resource: ibm_cd_tekton_pipeline_property
 2026/08/11 11:04:25 Terraform apply | operation: create
 2026/08/11 11:04:25 Terraform apply | component:
 2026/08/11 11:04:25 Terraform apply |   name: github.com/IBM-Cloud/terraform-provider-ibm
 2026/08/11 11:04:25 Terraform apply |   version: 2.5.0
 2026/08/11 11:04:25 Terraform apply | ---
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |   with module.workload["ContainerImage-skupper-network-observer-2-2-ubi9"].ibm_cd_tekton_pipeline_property.properties["branch-protection-check"],
 2026/08/11 11:04:25 Terraform apply |   on .terraform/modules/workload/modules/workload-ibm-cloud-onboarding/main.tf line 172, in resource "ibm_cd_tekton_pipeline_property" "properties":
 2026/08/11 11:04:25 Terraform apply |  172: resource "ibm_cd_tekton_pipeline_property" "properties" {
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply | Error: ---
 2026/08/11 11:04:25 Terraform apply | id: terraform-b323781c
 2026/08/11 11:04:25 Terraform apply | summary: 'CreateTektonPipelinePropertiesWithContext failed: Property of the same name
 2026/08/11 11:04:25 Terraform apply |   exists.'
 2026/08/11 11:04:25 Terraform apply | severity: error
 2026/08/11 11:04:25 Terraform apply | resource: ibm_cd_tekton_pipeline_property
 2026/08/11 11:04:25 Terraform apply | operation: create
 2026/08/11 11:04:25 Terraform apply | component:
 2026/08/11 11:04:25 Terraform apply |   name: github.com/IBM-Cloud/terraform-provider-ibm
 2026/08/11 11:04:25 Terraform apply |   version: 2.5.0
 2026/08/11 11:04:25 Terraform apply | ---
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |   with module.workload["ContainerImage-skupper-network-observer-2-2-ubi9"].ibm_cd_tekton_pipeline_property.properties["repository"],
 2026/08/11 11:04:25 Terraform apply |   on .terraform/modules/workload/modules/workload-ibm-cloud-onboarding/main.tf line 172, in resource "ibm_cd_tekton_pipeline_property" "properties":
 2026/08/11 11:04:25 Terraform apply |  172: resource "ibm_cd_tekton_pipeline_property" "properties" {
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply | Error: ---
 2026/08/11 11:04:25 Terraform apply | id: terraform-b323781c
 2026/08/11 11:04:25 Terraform apply | summary: 'CreateTektonPipelinePropertiesWithContext failed: Property of the same name
 2026/08/11 11:04:25 Terraform apply |   exists.'
 2026/08/11 11:04:25 Terraform apply | severity: error
 2026/08/11 11:04:25 Terraform apply | resource: ibm_cd_tekton_pipeline_property
 2026/08/11 11:04:25 Terraform apply | operation: create
 2026/08/11 11:04:25 Terraform apply | component:
 2026/08/11 11:04:25 Terraform apply |   name: github.com/IBM-Cloud/terraform-provider-ibm
 2026/08/11 11:04:25 Terraform apply |   version: 2.5.0
 2026/08/11 11:04:25 Terraform apply | ---
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |
 2026/08/11 11:04:25 Terraform apply |   with module.workload["ContainerImage-skupper-network-observer-2-2-ubi9"].ibm_cd_tekton_pipeline_property.properties["ibmcloud-api-key"],

Panic Output

Expected Behavior

Actual Behavior

Steps to Reproduce

  1. terraform apply

Important Factoids

To work around it, I know I can either import the resources, or delete them and allow TF to re-create. But ideally the root cause should be identified and fixed.

References

  • #0000

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions