Closed jmajumde closed 7 years ago
To clarify, you are saying the property may be defined and changed in your plan but does not change the state of the resource, and you verify this by checking the same resource in the console?
The state of the resource is also good if you go and check in BM UI console. But the problem is any application which relies session persistent does not work unless from console we do a re-submit of the lbaas backendset even the creation of lbaas backendset is all good from TF
Where as if I create the lbaas backendset with ruby sdk or direct rest API call then thats not the case. Our application works perfectly fine as the session persistent flag takes in effect for lbaas
I tried to repro using a modification of the lb_full.tf example, and session persistence worked correctly for me. See the modifications that I used at https://github.com/oracle/terraform-provider-baremetal/commit/28b02a17c737e5d5f781f084382dfbc673d54b00. When you go to the LB public IP, then it should stick to whichever backend it receives first. Is this different from what you were trying?
Terraform Version
Baremetal Provider Version
Terraform Provider : v1.0.16
Description:
While we are creating lbaas backend sets with session persistent flag enabled then looks like the lbaas session persistent does not honored. Though there is no error while creating lbaas backends but unless we login to web console and do a dummy submit for lbaas backendset, application does not work to handle the persistent request.
But, as a w/r the same backendset creation if I do with ruby-sdk apis or direct lbaas rest call this behavior does not happen.
Terraform Plan