Hi @rymancl,
I know that some folks have encountered problems similar to this, where the automatic upgrade didn’t work, but there haven’t been enough examples yet to see any pattern in the causes, particularly because those with simpler architectures have been happy to use the manual workaround and not investigate further.
Based on what we know so far, I think the following information would be helpful to try to understand better what’s special in your situation that might cause the different behavior:
- Run
terraform init
with the environment variableTF_LOG=trace
and share that log output, e.g. in a gist. (I expect it will be too long to share inline in a forum comment.) - After
terraform init
succeeds, the full directory structure now under.terraform/plugins
, which Terraform should just have populated. (For example, using either thetree
orfind
commands.) - Run whatever command is returning the error you shared also with
TF_LOG=trace
and share that output in a similar way, so we can see how subsequent Terraform commands are understanding the on-disk result fromterraform init
.
It seems like for some reason the legacy provider plugins that Terraform wants to use to support the automatic upgrade can’t be found after installation, so the main thing I want to see here is why that might be. For example, if the installer is failing to put them there in the first place or if something is going wrong scanning the available plugins in later commands.
Thanks in advance if you are able to share these details! I hope it will lead to an explanation and perhaps also a fix.