Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update hashicorp null and random providers to enable darwin/arm64 support #451

Closed
prb112 opened this issue Dec 5, 2022 · 3 comments · Fixed by #452
Closed

Update hashicorp null and random providers to enable darwin/arm64 support #451

prb112 opened this issue Dec 5, 2022 · 3 comments · Fixed by #452
Assignees

Comments

@prb112
Copy link
Contributor

prb112 commented Dec 5, 2022

Background

On darwin/arm64, I cloned and executed a terraform init. I encountered the following.


│ Error: Incompatible provider version

│ Provider registry.terraform.io/hashicorp/random v2.3.1 does not have a package
│ available for your current platform, darwin_arm64.

│ Provider releases are separate from Terraform CLI releases, so not all providers are
│ available for all platforms. Other versions of this provider may have different
│ platforms supported.


│ Error: Incompatible provider version

│ Provider registry.terraform.io/hashicorp/null v2.1.2 does not have a package available
│ for your current platform, darwin_arm64.

│ Provider releases are separate from Terraform CLI releases, so not all providers are
│ available for all platforms. Other versions of this provider may have different
│ platforms supported.

Terraform added support for darwin/arm64. I updated hashicorp null and random providers locally, and it worked.

A composite of the version updates I had to make to pickup darwin/arm64.

terraform {
  required_providers {
    random = {
      source  = "hashicorp/random"
      version = "~> 3.4"
    }
    null = {
      source  = "hashicorp/null"
      version = "~> 3.2"
    }
  }
  required_version = ">= 1.2.0"
}

If you'd like a PR raised, please let me know.

prb112 added a commit to prb112/ocp4-upi-powervs that referenced this issue Dec 6, 2022
@yussufsh
Copy link
Contributor

yussufsh commented Dec 7, 2022

Thanks for creating the issue.

Yes we need to upgrade the providers. Even ignition provider started releasing arm64 payload. We also need to bump up IBM Cloud provider which has some fixes related to power APIs.

@yussufsh yussufsh self-assigned this Dec 7, 2022
@prb112
Copy link
Contributor Author

prb112 commented Dec 7, 2022

Hey Yussuf, great, I created a PR, however I wasn't able to get a successful deployment on MON01 -
I did also set environment variables in openshift-install-power to point to the Branch I created, and it mostly worked until I had some reboot problems in powervs

@yussufsh
Copy link
Contributor

yussufsh commented Dec 7, 2022

@prb112 it is okay to raise that PR for random and null provider. Ignore the infrastructure issues. I will test out IBM Cloud provider changes later.

prb112 added a commit to prb112/ocp4-upi-powervs that referenced this issue Dec 8, 2022
…port ocp-power-automation#451

Updates hashicorp null and random to support darwin/arm64
Resolves issue ocp-power-automation#451

Signed-off-by: Paul Bastide <pbastide@us.ibm.com>
ppc64le-cloud-bot pushed a commit that referenced this issue Dec 20, 2022
Update hashicorp null and random providers to enable darwin/arm64 support #451
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants