-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Unable to authenticate to HCP using Vagrant #13575
Labels
Comments
I am facing a similar issue, too. My .gitlab-ci.yml logic for pushing Vagrant box to HCP (see https://gitlab.com/alvistack/vagrant-debian/-/blob/develop/.gitlab-ci.yml?ref_type=heads#L128-177):
My GitLab CI pipeline (see https://gitlab.com/alvistack/vagrant-debian/-/jobs/8877821966#L146):
|
hswong3i
added a commit
to alvistack/hashicorp-vagrant
that referenced
this issue
Jan 18, 2025
As <hashicorp#13571 (comment)> mentioned: > After further debug, this looks like a change introduced in HCP > Vagrant Registry after 2025-01-09, that broke Vagrant versions before > 2.4.0. I could confirm that everything works fine with Vagrant 2.4.0 > (and later), but fails to work with Vagrant 2.3.7 (and earlier). The > root cause is that Vagrant 2.3.7 uses the equivalent of curl > --location --verbose -H "Accept: application/json" > <https://vagrantcloud.com/debian/bookworm64> to fetch the box > metadata, but this no longer returns a JSON document. Vagrant 2.4.0 > uses <https://vagrantcloud.com/api/v2/vagrant/debian/bookworm64> > instead. This PR replace most <https://developer.hashicorp.com/vagrant/vagrant-cloud/api/v2> URL from existing <https://app.vagrantup.com> to <https://vagrantcloud.com>. Fixes <hashicorp#13571> Fixes <hashicorp#13574> Fixes <hashicorp#13575> Signed-off-by: Wong Hoi Sing Edison <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following https://developer.hashicorp.com/vagrant/vagrant-cloud/hcp-vagrant/post-migration-guide , I do:
but then, I get:
it worked in December.
This is different from issue 13574 : I try to login to HCP, not Vagrant Cloud.
Reproduction information
Vagrant version
Vagrant 2.4.3
Host operating system
Linux Debian 12
The text was updated successfully, but these errors were encountered: