Thanks Can you open a issue on GitHub and share a reproducible project?
https://github.com/mitchellh/vagrant Thanks! Alvaro On Sun, Apr 16, 2017 at 2:50 PM, athreyavc <[email protected]> wrote: > I just tried that, > > Removed the renaming part, just left it to "win". to keep it simple. > Still the error is same. > > When I call the winrm using the example you gave before, all works > perfectly. I am so assuming WinRM should be fine. > > However, chef provision fails. > > GuestMemoryBalloon=0 > GuestOSType="Windows81_64" > GuestAdditionsRunLevel=2 > GuestAdditionsVersion="5.0.4 r102546" > GuestAdditionsFacility_VirtualBox Base Driver=50,1492346276243 > GuestAdditionsFacility_VirtualBox System Service=50,1492346293202 > GuestAdditionsFacility_Seamless Mode=0,1492346276241 > GuestAdditionsFacility_Graphics Mode=0,1492346276239 > DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000 > DEBUG subprocess: Exit status: 0 > INFO warden: Recovery complete. > INFO warden: Calling recover: #<Vagrant::Action::Builtin:: > Call:0x000000039cff38> > 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. > ERROR warden: Error occurred: Chef never successfully completed! Any > errors should be visible in the > output above. Please fix your recipes so that they properly 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 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. > ERROR warden: Error occurred: Chef never successfully completed! Any > errors should be visible in the > output above. Please fix your recipes so that they properly 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. > ERROR warden: Error occurred: Chef never successfully completed! Any > errors should be visible in the > output above. Please fix your recipes so that they properly complete. > INFO warden: Beginning recovery process... > INFO warden: Recovery complete. > INFO warden: Beginning recovery process... > INFO warden: Recovery complete. > ERROR warden: Error occurred: Chef never successfully completed! Any > errors should be visible in the > output above. Please fix your recipes so that they properly 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- > 8489c4c1e9cdf8e3c145edc3b65e2671 > INFO environment: Running hook: environment_unload > INFO runner: Preparing hooks for middleware sequence... > INFO runner: 3 hooks defined. > INFO runner: Running action: environment_unload > #<Vagrant::Action::Builder:0x00000002bd38f8> > ERROR vagrant: Vagrant experienced an error! Details: > ERROR vagrant: #<VagrantPlugins::Chef::Provisioner::Base::ChefError: Chef > never successfully completed! Any errors should be visible in the > output above. Please fix your recipes so that they properly complete.> > ERROR vagrant: Chef never successfully completed! Any errors should be > visible in the > output above. Please fix your recipes so that they properly complete. > ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/ > provisioners/chef/provisioner/chef_client.rb:108:in `run_chef_client' > > > ERROR vagrant: Chef never successfully completed! Any errors should be > visible in the > > On Sun, Apr 16, 2017 at 1:21 PM, Alvaro Miranda Aguilera < > [email protected]> wrote: > >> Hello >> >> If you remove the hostname from Vagrant and try to setup it manually or >> with chef, does that work? >> >> As in, are you able to winrm after the hostname has been changed? >> >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "Vagrant" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/vagrant-up/8GClmp8qcnU/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/vagrant-up/CAHqq0ezwqYt7x_xzfa0-BYeo8yw6SF9pMHbGV7k4zkV_ >> N-apWQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezwqYt7x_xzfa0-BYeo8yw6SF9pMHbGV7k4zkV_N-apWQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/CAK-gxkPNMuDrAk9vbR9nrg-tg%3DSGKs4NwGVTbt1Tu6zsa2swHQ% > 40mail.gmail.com > <https://groups.google.com/d/msgid/vagrant-up/CAK-gxkPNMuDrAk9vbR9nrg-tg%3DSGKs4NwGVTbt1Tu6zsa2swHQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Alvaro -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezO6c7ptw0F8b99Dv0kbwJ%2Bq60%2BnnPoNQZF6Z_%2BaE3hrg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
