Chef Solo – Vagrant Provision – Vagrant could not detect Chef on the guest!

I am having a Chef cookbook (Chef Solo) to configure Vagrant Virtual Machines for development purposes. When the Vagrant VM has provisioned, the process halts in the \`Installing Chef (latest)\` step.

default: /vagrant => /Volumes/Dev/Work/GivingFire/Projects/givingfire
default: /tmp/vagrant-chef/0ae6e634f5cf8da9c53a3b35f2980c7e/cookbooks => /Volumes/Dev/Work/GivingFire/Projects/givingfire-cookbook/berks-cookbooks
==> default: Running provisioner: chef_solo...
default: Installing Chef (latest)...
Vagrant could not detect Chef on the guest! Even after Vagrant
attempted to install Chef, it could still not find Chef on the system.
Please make sure you are connected to the Internet and can access
Chef's package distribution servers. If you already have Chef
installed on this guest, you can disable the automatic Chef detection
by setting the 'install' option in the Chef configuration section of
your Vagrantfile:

chef.install = false

When SSH to the box, I can verify that Chef is installed.

When I update as suggested and run \`vagrant provision, it goes through.

Does anyone have a solution for this issue? It's a fairly new matter that showed up after updating libs.

Additional Details:

* Guest: Ubuntu 20.04, Ubuntu 18.04
* Host: macOS Catalina
* VirtualBox: 6.1

[email protected]:~|⇒ chef --version
Chef Workstation version: 21.5.462
Chef Infra Client version: 17.1.35
Chef InSpec version: 4.37.20
Chef CLI version: 5.1.0
Chef Habitat version: 1.6.319
Test Kitchen version: 2.11.2
Cookstyle version: 7.13.0

Vagrant:

[email protected]:~|⇒ vagrant --version
Vagrant 2.2.16

Leave a Comment