DenysChekirda

@hkantare @obai-1 any updates on this? We still seeing errors on updating existing database deployments from `node_*` and `member_*` usage to `group`. Detailed logs here: https://gist.github.com/DenysChekirda/b1d8e92f942c086cc5ba3739d9717147 IBMCloud provider version used:...

@hkantare put plan output and variable output into gist: https://gist.github.com/DenysChekirda/38a0c11ff31499fd575e5a8bb624f7b5

Hi @hkantare as for the local.worker_pools_autoscale - output can be found starting of this line in gist: https://gist.github.com/DenysChekirda/38a0c11ff31499fd575e5a8bb624f7b5#file-plan-tf-L609 This is how we are generating this variable ```hcl worker_pools_autoscale = {...

Hi @hkantare we faced this issue once again on different account. From our terraform modules code perspective - nothing been changed. We are using stable versions for last 7-9 months....

@hkantare Again same problem happen but this time with only one worker pool. Worker pool and worker nodes been created but terraform failed with error: ```hcl Error: Request failed with...

Hi @hkantare , I've been communicating with IBM Support team. By information from them they've already found the bug on Schematics and applied that to Prod but the actual issue...

Hi @lewiseevans here is the most recent error message with incident ID: ``` Error: Request failed with status code: 409, ServerErrorResponse: {"incidentID":"c2c5549c-39cf-4be3-9aae-c0ab62e63e37","code":"E0d39","description":"A worker pool with the same name already exists...