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

[BUG] 1.2 Release Accidently deleted #795

Closed
1 task done
vipinvkmenon opened this issue May 3, 2024 · 9 comments
Closed
1 task done

[BUG] 1.2 Release Accidently deleted #795

vipinvkmenon opened this issue May 3, 2024 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@vipinvkmenon
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

What version of the Terraform provider are you using?

1.2.0

What version of the Terraform CLI are you using?

1.8.0

What type of issue are you facing

bug report

Describe the bug

The release was accidently deleted

Expected Behavior

Should not have deleted.

Steps To Reproduce

No response

User's Role Collections

No response

Add screenshots to help explain your problem

No response

Additional context

No response

@vipinvkmenon vipinvkmenon added bug Something isn't working needs-triage For new issues labels May 3, 2024
@alxsap
Copy link

alxsap commented May 3, 2024

terraform/tofu init now fails with:

[2024-05-03T07:05:38.519Z] 2024-05-03T07:05:38.311Z [DEBUG] GET https://registry.opentofu.org/v1/providers/sap/btp/1.2.0/download/linux/amd64
[2024-05-03T07:05:38.519Z] 2024-05-03T07:05:38.311Z [TRACE] HTTP client GET request to https://registry.opentofu.org/v1/providers/sap/btp/1.2.0/download/linux/amd64
[2024-05-03T07:05:38.519Z] 2024-05-03T07:05:38.433Z [DEBUG] GET https://github.com/SAP/terraform-provider-btp/releases/download/v1.2.0/terraform-provider-btp_1.2.0_SHA256SUMS
[2024-05-03T07:05:38.519Z] 2024-05-03T07:05:38.434Z [TRACE] HTTP client GET request to https://github.com/SAP/terraform-provider-btp/releases/download/v1.2.0/terraform-provider-btp_1.2.0_SHA256SUMS
[2024-05-03T07:05:38.779Z] ╷
[2024-05-03T07:05:38.779Z] │ Error: Failed to install provider
[2024-05-03T07:05:38.779Z] │ 
[2024-05-03T07:05:38.779Z] │ Error while installing sap/btp v1.2.0: could not query provider registry
[2024-05-03T07:05:38.779Z] │ for registry.opentofu.org/sap/btp: failed to retrieve authentication
[2024-05-03T07:05:38.779Z] │ checksums for provider: 404 Not Found returned from github.com

@alxsap
Copy link

alxsap commented May 3, 2024

@vipinvkmenon I saw you recreated the release. Thanks for that.
I guess you are aware of it, now it fails due to differing checksums of the binaries.
Not sure if you fixed this for terraform already, but the checksums in the OpenTofu registry still differ.

  • Installing sap/btp v1.2.0...
    Error: Failed to install provider
    Error while installing sap/btp v1.2.0: checksum list has unexpected SHA-256 hash 5d10880449a85b48a4ef3324809a40f9d182f21fc9744c4bf6054cc865281959 (expected 5a1d9ea9fbb98a554f00d49132a8dca830c61f32f2008757b9e73d42961c7bc8)

@lechnerc77 lechnerc77 removed the needs-triage For new issues label May 3, 2024
@lechnerc77
Copy link
Member

@alxsap We are working on re-synchronizing the release with the Terraform registry. However there needs to be stuff done on Hashicorp side, so this might take a bit

@lechnerc77
Copy link
Member

Temporal Workaround: Use version 1.1.0 in the meantime

@lechnerc77
Copy link
Member

As we are still sorting things out with Hashicorp, you can as of today also use the provider version 1.3.0 that we just published

@vipinvkmenon
Copy link
Member Author

Version 1.2.0 with the newer shasum is restored. However, we would recommend updating to the newer release 1.3.0.

@vipinvkmenon vipinvkmenon self-assigned this May 13, 2024
@lechnerc77
Copy link
Member

@vipinvkmenon I just re-tested and the error with 1.2.0 still exists on my end:

image

Works fine with 1.1.0 and 1.3.0, so it seems that the checksums have not been rehydrated until now

@lechnerc77 lechnerc77 reopened this May 13, 2024
@lechnerc77
Copy link
Member

Retested today, now it works also on my end ... seems like there is some regional caching in place for the registry

@lechnerc77
Copy link
Member

Closing the issue as resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants