Ignoring nokogiri-1.10.4 because its extensions are not built. Try: gem pristine nokogiri --version 1.10.4

lmilbaum commented 4 years ago

Vagrant version

2.2.7

Host operating system

OSX 10.15.3

Actual behavior

zapata) ➜ zapata git:(master) vagrant destroy -f     
Ignoring nokogiri-1.10.4 because its extensions are not built.  Try: gem pristine nokogiri --version 1.10.4
Ignoring ovirt-engine-sdk-4.3.0 because its extensions are not built.  Try: gem pristine ovirt-engine-sdk --version 4.3.0
==> default: VM not created. Moving on...

jbonhag commented 4 years ago

Hi there, and thanks for opening an issue with Vagrant!

Unfortunately, there isn't quite enough information here to recommend a solution. If you'd be willing to create a debug log (vagrant destroy -f --debug) then we can investigate further.

If you can mention which Vagrant plugins you have installed (vagrant plugin list), that would be helpful as well.

Thanks!

bryansoto commented 4 years ago

Not the original reporter but this seems of interest.

ERROR manager: Failed to load plugin `vagrant-vmware-desktop` with default require. - LoadError: The RubyEncoder loader is not installed. Please visit the http://www.rubyencoder.com/loaders/ RubyEncoder site to download the required loader for 'darwin' and unpack it into '/opt/vagrant/embedded/rgloader' directory to run this protected script.

lmilbaum commented 4 years ago

I have uninstalled all plugins and those messages didn't appear.

apollograce commented 4 years ago

I'm getting this same issue for the first time after upgrading from Vagrant 2.2.6 to 2.2.7.

Here's my vagrant plugin list:

vagrant-parallels (2.0.1, global)
  - Version Constraint: > 0

I'm not willing to "vagrant destroy".

pokono commented 4 years ago

Typing vagrant global-status trigger the same message. Doesn't seem to be plugin dependant.

$ vagrant global-status 
Ignoring nokogiri-1.10.4 because its extensions are not built.  Try: gem pristine nokogiri --version 1.10.4
id       name           provider  state     directory                                                          
---------------------------------------------------------------------------------------------------------------

zigsphere commented 4 years ago

Im seeing this exact issue on vagrant 2.2.7:

$ vagrant plugin list
vagrant-aws (0.7.2, global)
  - Version Constraint: > 0
vagrant-share (1.1.9, global)
  - Version Constraint: > 0
vagrant-useradd (0.0.1, global)
  - Version Constraint: > 0
vagrant-vbguest (0.20.0, global)
vagrant-vbox-snapshot (0.0.10, global)
  - Version Constraint: > 0

$ vagrant global-status
Ignoring nokogiri-1.10.4 because its extensions are not built.  Try: gem pristine nokogiri --version 1.10.4
Ignoring ovirt-engine-sdk-4.3.0 because its extensions are not built.  Try: gem pristine ovirt-engine-sdk --version 4.3.0
id       name                                         provider   state   directory
----------------------------------------------------------------------------------------------------------------------------------------------------

Also seeing it with ovirt-engine-sdk rather than just nokogiri. Having the issue with both.

zigsphere commented 4 years ago

Here is a gist of mine. It Errors at the bottom because there are no nodes to destroy on my machine, but here is the remaining output: https://gist.github.com/zigsphere/7828c1a3633a6e881a850b06b5fe3d8f

chrisroberts commented 4 years ago

It appears the extensions did not get correctly built. If you remove and re-install the plugins, do you still see the same issue? Easy method for re-installing plugins:

vagrant plugin expunge --reinstall

zigsphere commented 4 years ago

Hello @chrisroberts ,

This seemed to do the trick for me. Thank you:

○ → vagrant plugin expunge --reinstall

This command permanently deletes all currently installed user plugins. It
should only be used when a repair command is unable to properly fix the
system.

Continue? [N]: Y

All user installed plugins have been removed from this Vagrant environment!

Vagrant will now attempt to reinstall user plugins that were removed.
Installing the 'vagrant-aws' plugin. This can take a few minutes...
Fetching: iniparse-1.4.4.gem (100%)
Fetching: xmlrpc-0.3.0.gem (100%)
Fetching: formatador-0.2.5.gem (100%)
Fetching: excon-0.72.0.gem (100%)
Fetching: fog-core-1.45.0.gem (100%)
Fetching: mini_portile2-2.4.0.gem (100%)
Fetching: nokogiri-1.10.7.gem (100%)
Building native extensions.  This could take a while...
Fetching: fog-xml-0.1.3.gem (100%)
Fetching: fog-xenserver-1.0.0.gem (100%)
Fetching: optimist-3.0.0.gem (100%)
Fetching: rbvmomi-2.3.0.gem (100%)
Fetching: fog-vsphere-3.2.3.gem (100%)
Fetching: fog-voxel-0.1.0.gem (100%)
Fetching: CFPropertyList-2.3.6.gem (100%)
Fetching: fission-0.5.0.gem (100%)
Fetching: fog-vmfusion-0.1.0.gem (100%)
Fetching: fog-terremark-0.1.0.gem (100%)
Fetching: fog-json-1.2.0.gem (100%)
Fetching: fog-storm_on_demand-0.1.1.gem (100%)
Fetching: fog-softlayer-1.1.4.gem (100%)
Fetching: fog-serverlove-0.1.2.gem (100%)
Fetching: fog-sakuracloud-1.7.5.gem (100%)
Fetching: fog-riakcs-0.1.0.gem (100%)
Fetching: fog-radosgw-0.0.5.gem (100%)
Fetching: ipaddress-0.8.3.gem (100%)
Fetching: fog-rackspace-0.1.6.gem (100%)
Fetching: fog-profitbricks-4.1.1.gem (100%)
Fetching: fog-powerdns-0.2.0.gem (100%)
Fetching: rbovirt-0.1.7.gem (100%)
Fetching: ovirt-engine-sdk-4.3.0.gem (100%)
Building native extensions.  This could take a while...
Fetching: fog-ovirt-1.2.4.gem (100%)
Fetching: fog-openstack-0.3.10.gem (100%)
Fetching: fog-local-0.6.0.gem (100%)
Fetching: fog-joyent-0.0.1.gem (100%)
Fetching: fog-internet-archive-0.0.1.gem (100%)
Fetching: fog-google-0.1.0.gem (100%)
Fetching: fog-ecloud-0.3.0.gem (100%)
Fetching: fog-dynect-0.0.3.gem (100%)
Fetching: fog-dnsimple-1.0.0.gem (100%)
Fetching: fog-digitalocean-0.4.0.gem (100%)
Fetching: fog-cloudatcost-0.1.2.gem (100%)
Fetching: dry-inflector-0.2.0.gem (100%)
Fetching: fog-brightbox-0.16.1.gem (100%)
Fetching: fog-aws-2.0.1.gem (100%)
Fetching: fog-atmos-0.1.0.gem (100%)
Fetching: xml-simple-1.1.5.gem (100%)
Fetching: fog-aliyun-0.3.5.gem (100%)
Fetching: fog-1.42.1.gem (100%)
------------------------------
Thank you for installing fog!

IMPORTANT NOTICE:
If there's a metagem available for your cloud provider, e.g. `fog-aws`,
you should be using it instead of requiring the full fog collection to avoid
unnecessary dependencies.

'fog' should be required explicitly only if:
- The provider you use doesn't yet have a metagem available.
- You require Ruby 1.9.3 support.
------------------------------
Fetching: vagrant-aws-0.7.2.gem (100%)
Fetching: vagrant-share-1.1.9.gem (100%)
Fetching: vagrant-useradd-0.0.1.gem (100%)
Fetching: micromachine-3.0.0.gem (100%)
Fetching: vagrant-vbguest-0.23.0.gem (100%)
Fetching: vagrant-vbox-snapshot-0.0.10.gem (100%)
Vagrant failed to properly resolve required dependencies. These
errors can commonly be caused by misconfigured plugin installations
or transient network issues. The reported error is:

Unable to resolve dependency: user requested 'vagrant-vbguest (= 0.20.0)'

I got the error above, but then I also ran vagrant plugin update, which fixed that issue.

○ → vagrant global-status
id       name   provider state  directory
--------------------------------------------------------------------
There are no active Vagrant environments on this computer! Or,
you haven't destroyed and recreated Vagrant environments that were
started with an older version of Vagrant.

Thanks for your help

pokono commented 4 years ago

Thank you @chrisroberts ! Reinstalling plugins fixed it for me as well!

chrisroberts commented 4 years ago

Great, glad that fixed things up. If anyone is still experiencing this issue after re-installing plugins, please open a new issue. Cheers!

ghost commented 4 years ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

hashicorp / vagrant