Ohai,
it seems we currently can't reach vagrantcloud.com from machines provisioned by Duffy:
$ vagrant init centos/7 $ vagrant up … The box 'centos/7' could not be found or could not be accessed in the remote catalog. If this is a private box on HashiCorp's Vagrant Cloud, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://vagrantcloud.com/centos/7"] Error: The requested URL returned error: 403 Forbidden
Example jobs failing: https://ci.centos.org/job/foreman-pipeline-pulpcore-3.7-centos7-pulpcore/125/console https://ci.centos.org/job/foreman-pipeline-pulpcore-3.7-centos8-pulpcore/125/console
Feel free to re-trigger one of these to test.
Hi,
There is no network limitation from CI vlan to outside, so either it's a temporary network issue with Hashicorp (out of our support scope obviously), or maybe they have rate-limit implemented. Does it work from outside that env ?
Metadata Update from @arrfab: - Issue tagged with: centos-ci-infra, need-more-info
Yes, works like a charm from my private connection here at home and from machines in RDU2.
as server (out of our infra) answers 403, worth verifying with hashicorp ? So let's keep this open for now but waiting on external feedback (in case other projects in CI are also using vagrant)
Metadata Update from @arrfab: - Issue priority set to: Waiting on External (was: Needs Review) - Issue tagged with: groomed
Just a note for everyone stumbling over this ticket: It seems the issue that vagrantcloud.com is now being routed via Amazon CloudFront and that for some reason doesn't know how to properly redirect the client to the right place. I've opened a ticket with Vagrant to look into this.
And if that helps anyone, if you force vagrantcloud.com to resolve to 52.55.225.227 (Heroku, instead of Cloudfront), it works like a charm again.
Closing as it seems to be fixed now
Metadata Update from @evgeni: - Issue close_status updated to: Wrong tracker - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.