4linux / 516 Goto Github PK

Olá,
Não achei nenhuma forma de contato pelo curso, por isso estou postando o problema aqui.

Estou com um erro ao executar o vagrant up em ambiente Windows.

vagrant.exe up
Bringing machine 'webserver-audit' up with 'virtualbox' provider...
Bringing machine 'graylog-audit' up with 'virtualbox' provider...
Bringing machine 'kibana-audit' up with 'virtualbox' provider...
==> webserver-audit: Box 'trombik/ansible-centos-7.3-x86_64' could not be found.
Attempting to find and install...
webserver-audit: Box Provider: virtualbox
webserver-audit: Box Version: >= 0
The box 'trombik/ansible-centos-7.3-x86_64' 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/trombik/ansible-centos-7.3-x86_64"]
Error: schannel: next InitializeSecurityContext failed: Unknown error (0x8009201
2) - A fun��o de revoga��o n�o p�de verificar a revoga��o do certificado.

Tentei mudar o box mas sempre da a mesma mensagem.

Problem

When trying to provision the VMs in this repository by running the vagrant up command, I encountered the following error:

 Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable

This is due to a repository codename change. In order to avoid this error, the --allow-releaseinfo-change flag must be used when installing/updating packages.

Solution

Since there currently is no way in the documentation to force --allow-releaseinfo-change through the ansible apt module, a workaround is to add this step beforehand:

  - name: Allow release-info to change for APT repositories
   command: apt-get update -y --allow-releaseinfo-change

Reference: ansible/ansible#48352 (comment)