-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
4.17.z
-
Critical
-
None
-
False
-
-
Update IBM Cloud Terraform provider to pick up fix for CIS API changes.
-
Bug Fix
-
In Progress
Description of problem:
the CIS "plugin did not respond" blocked the public install
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2025-03-14-195326
How reproducible:
Always
Steps to Reproduce:
1.create public ipi cluster on IBMCloud platform
2.
3.
Actual results:
level=info msg=Creating infrastructure resources...
msg=Error: Plugin did not respond
...
msg=panic: runtime error: invalid memory address or nil pointer dereference
msg=[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x24046dc]256level=error257level=error msg=goroutine 2090 [running]:258level=error msg=github.com/IBM-Cloud/terraform-provider-ibm/ibm/service/cis.ResourceIBMCISDnsRecordRead(0xc003573900, {0x4ed2fa0?, 0xc00380c008?})
Expected results:
create cluster succeed.
Additional info:
https://github.com/IBM-Cloud/terraform-provider-ibm/issues/6066 ibm_cis_dns_record leads to plugin crash
Due to conflicts with golang versions and the upstream TF provider not being versioned for multiple golang versions, cherry-picking fixes to older releases will not follow the normal process, as we cannot bump the TF provider version to the same in all OCP releases.
PR's will be created and managed based on the golang version for OCP and the designated TF provider release.
- depends on
-
-
- Verified
-
- duplicates
-
-
- Verified
-
