Error: missing provider provider["registry.terraform.io/hashicorp/oci"].home

[raoul29]

I am getting the error below when running terraform validate or terraform apply

[raoul@auto terraform-oci-oke]$ terraform init
Initializing modules...

Initializing the backend...

Initializing provider plugins...

• Reusing previous version of hashicorp/time from the dependency lock file
• Reusing previous version of hashicorp/local from the dependency lock file
• Reusing previous version of hashicorp/oci from the dependency lock file
• Reusing previous version of hashicorp/cloudinit from the dependency lock file
• Reusing previous version of hashicorp/null from the dependency lock file
• Using previously-installed hashicorp/time v0.7.2
• Using previously-installed hashicorp/local v2.1.0
• Using previously-installed hashicorp/oci v4.62.0
• Using previously-installed hashicorp/cloudinit v2.2.0
• Using previously-installed hashicorp/null v3.1.0

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
[raoul@auto terraform-oci-oke]$ terraform validate
╷
│ Error: missing provider provider["registry.terraform.io/hashicorp/oci"].home
│

[Matthew-Beckett]

I am also experiencing this issue when invoking this module via Terragrunt.

│ Error: missing provider provider["registry.terraform.io/oracle/oci"].home

[sajeevnambidi]

Getting same error,
Error: missing provider provider["registry.terraform.io/oracle/oci"].home

[Matthew-Beckett]

@sajeevnambidi and @raoul29 if my experience of using Oracle Cloud, opening issues, talking to their support directly, trying to deploy their Kubernetes offering on OCI and the lack of triage or reply on this issue is anything to go by may I suggest you patch this yourself and move on. It's fairly evident Oracle do not care.

[scoter-oracle]

Please, check if this issue can be reproduced with latest code release.