質問: info ssh: ssh not up: #<vagrant::errors::sshauthenticationfailed: ssh authentication failed! this is typically caused by the public/private keypair for the ssh user not being properly set on the guest vm. please verify that the guest vm is setup with the proper public key, and that the private key path for vagrant is setup properly as well.> error warden: error occurred: guest-specific operations were attempted on a machine that is not ready for guest communication. this should not happen and a bug should be reported. ... info warden: beginning recovery process... info warden: recovery complete. error warden: error occurred: guest-specific operations were attempted on a machine that is not ready for guest communication. this should not happen and a bug should be reported. info warden: beginning recovery process... info warden: recovery complete. error warden: error occurred: guest-specific operations were attempted on a machine that is not ready for guest communication. this should not happen and a bug should be reported. info warden: beginning recovery process... info warden: calling recover: #<vagrant::action::builtin::call:0x000001014851a0> info warden: beginning recovery process... info warden: recovery complete. info warden: recovery complete. info warden: beginning recovery process... info warden: recovery complete. info warden: beginning recovery process... info warden: recovery complete. info warden: beginning recovery process... info warden: recovery complete. info warden: beginning recovery process... info warden: recovery complete. info warden: beginning recovery process... info warden: recovery complete. info environment: released process lock: machine-action-8d4f93c9bedf41af432adedf7b959248 info environment: running hook: environment_unload info runner: preparing hooks for middleware sequence... info runner: 2 hooks defined. info runner: running action: #<vagrant::action::builder:0x000001025849b0> error vagrant: vagrant experienced an error! details: error vagrant: #<vagrant::errors::machineguestnotready: guest-specific operations were attempted on a machine that is not ready for guest communication. this should not happen and a bug should be reported.> error vagrant: guest-specific operations were attempted on a machine that is not ready for guest communication. this should not happen and a bug should be reported. error vagrant: /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/machine.rb:231:in `guest' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/synced_folders/rsync/synced_folder.rb:31:in `enable' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builtin/synced_folders.rb:90:in `block in call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builtin/synced_folders.rb:87:in `each' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builtin/synced_folders.rb:87:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /users/antkong/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.1/lib/berkshelf/vagrant/action/upload.rb:24:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /users/antkong/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.1/lib/berkshelf/vagrant/action/install.rb:35:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /users/antkong/.vagrant.d/gems/gems/vagrant-omnibus-1.4.1/lib/vagrant-omnibus/action/install_chef.rb:38:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builtin/provision.rb:80:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:95:in `block in finalize_action' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builder.rb:116:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/runner.rb:66:in `block in run' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/util/busy.rb:19:in `busy' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/runner.rb:66:in `run' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builtin/call.rb:53:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /users/antkong/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.1/lib/berkshelf/vagrant/action/configure_chef.rb:22:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /users/antkong/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.1/lib/berkshelf/vagrant/action/load_shelf.rb:27:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /users/antkong/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.1/lib/berkshelf/vagrant/action/set_ui.rb:11:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builtin/env_set.rb:19:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builder.rb:116:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/runner.rb:66:in `block in run' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/util/busy.rb:19:in `busy' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/runner.rb:66:in `run' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/machine.rb:196:in `action_raw' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/machine.rb:173:in `block in action' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment.rb:474:in `lock' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/machine.rb:161:in `call' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/machine.rb:161:in `action' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/provision/command.rb:30:in `block in execute' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/v2/command.rb:226:in `block in with_target_vms' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/v2/command.rb:220:in `each' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/v2/command.rb:220:in `with_target_vms' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/provision/command.rb:29:in `execute' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/cli.rb:42:in `execute' /applications/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment.rb:292:in `cli' /applications/vagrant/bin/../embedded/gems/gems/vagrant-1.6.5/bin/vagrant:174:in `<main>' info interface: error: guest-specific operations were attempted on a machine that is not ready for guest communication. this should not happen and a bug should be reported. guest-specific operations were attempted on a machine that is not ready for guest communication. this should not happen and a bug should be reported. info interface: machine: error-exit ["vagrant::errors::machineguestnotready", "guest-specific operations were attempted on a machine that is not\nready for guest communication. this should not happen and a bug\nshould be reported."]
回答: 私の環境にはlaravelで動作するhomesteadがありますが、vagrant boxを使用しているため、この問題が発生します。私が見つけた解決策は次のとおりです。私のために働く:vagrant reload --provisionhomesteadフォルダー内。