Can I get some help with this please ?
It seems to be for some reason the powerShell script I am supplying to
change the hostname to FQDN is not working.
Vagrant 1.6.3 + VBox 4.3 + ruby 2.0 => all Works
Vagrant 1.9.3 or anything which is not 1.6.3 + VBox 4.3 + ruby 2.0(any
ruby, tried with 2.2, 2.4) => NOT working
Tried to roll back to 1.6.3 , but vagrant-butcher will not install, some
dependencies will not be met.
Regards,
On Friday, 14 April 2017 13:02:37 UTC+1, athreya vc wrote:
>
> Ok I am made some debugging
>
> with vagrant 1.6.3 ,
>
> if ($LASTEXITCODE) { exit $LASTEXITCODE } else { exit 0 }
> DEBUG winrmshell: Output: {:data=>[], :exitcode=>0}
> INFO guest: Detected: windows!
> DEBUG guest: Searching for cap: change_host_name
> DEBUG guest: Checking in: windows
> DEBUG guest: Found cap: change_host_name in windows
> INFO guest: Execute capability: change_host_name [#<Vagrant::Machine:
> win001 (VagrantPlugins::ProviderVirtualBox::Provider)>, "
> testwin001.homelab.com"] (windows)
> DEBUG winrmshell: cmd executing:
> wmic computersystem where name="%COMPUTERNAME%" call rename name="
> testwin001.homelab.com"
> DEBUG winrmshell: Output: {:data=>[{:stdout=>"Executing
>
> On 1.93,
>
> VagrantPlugins::ProviderVirtualBox::Provider)>, "testwin001.homelab.com"]
> (windows)
> DEBUG winrmshell: Output: {:data=>[], :exitcode=>1}
> DEBUG winrm: powershell executing:
> $computer = Get-WmiObject -Class Win32_ComputerSystem
> $retval = $computer.rename("testwin001.homelab.com
> ").returnvalue
> if ($retval -eq 0) {
> shutdown /r /t 5 /f /d p:4:1 /c "Vagrant Rename Computer"
> }
> exit $retval
>
> DEBUG winrmshell: Output: {:data=>[], :exitcode=>87}
> ERROR warden: Error occurred: Renaming the Windows guest failed. Most
> often this is because you've
>
> Regards,
>
> On Thursday, 13 April 2017 17:32:29 UTC+1, athreya vc wrote:
>>
>> I am now trying to revert to 1.6.3 I am not sure whether winRM is working
>> as expected. However on other machine with 1.6.3 it works without any
>> errors.
>>
>> vagrant plugin install vagrant-butcher --plugin-version 2.0.0 --verbose
>> Installing the 'vagrant-butcher --version '2.0.0'' plugin. This can take
>> a few minutes...
>> Fetching source index from http://gems.hashicorp.com/
>> Fetching gem metadata from https://rubygems.org/...............
>> Fetching additional metadata from https://rubygems.org/..
>> Resolving dependencies...
>> Using public_suffix 2.0.5
>> Using addressable 2.5.1
>> Using builder 3.2.3
>> Using gyoku 1.3.1
>> Using mini_portile 0.6.0
>> Using nokogiri 1.6.2.1
>> Using akami 1.3.1
>> Using buff-extensions 0.5.0
>> Using hashie 3.5.5
>> Using varia_model 0.3.2
>> Using buff-config 0.4.0
>>
>> Gem::InstallError: buff-ignore requires Ruby version >= 2.1.
>> Bundler, the underlying system Vagrant uses to install plugins,
>> reported an error. The error is shown below. These errors are usually
>> caused by misconfigured plugin installations or transient network
>> issues. The error from Bundler is:
>>
>> An error occurred while installing buff-ignore (1.2.0), and Bundler
>> cannot continue.
>> Make sure that `gem install buff-ignore -v '1.2.0'` succeeds before
>> bundling.
>>
>>
>> On Thursday, 13 April 2017 12:25:28 UTC+1, athreya vc wrote:
>>>
>>> I don't know what changed. This whole stuff used to work with vagrant
>>> 1.6.3, Ruby 2.0.0 and Vbox 4.3. Now to rollback things, it is throwing
>>> nokogiri plugin error
>>>
>>> On Wednesday, 12 April 2017 18:17:20 UTC+1, athreya vc wrote:
>>>>
>>>> ==> testwin: Waiting for machine to boot. This may take a few minutes...
>>>> testwin: WinRM address: 127.0.0.1:2202
>>>> testwin: WinRM username: localadmin
>>>> testwin: WinRM execution_time_limit: PT2H
>>>> testwin: WinRM transport: negotiate
>>>> ==> testwin: Machine booted and ready!
>>>> ==> testwin: Checking for guest additions in VM...
>>>> ==> testwin: Setting hostname...
>>>> ==> testwin: Saved client key to
>>>> /home/testlab/testlab/lab/.vagrant/butcher/testwin-client.pem
>>>>
>>>> After this I get the Error
>>>>
>>>> On Wednesday, 12 April 2017 18:04:31 UTC+1, athreya vc wrote:
>>>>>
>>>>> Hi,
>>>>> I am trying setup a vagrant machine windows 2012r2. I am using
>>>>>
>>>>> vagrant -v
>>>>> Vagrant 1.9.3
>>>>>
>>>>> vagrant plugin list
>>>>> vagrant-butcher (2.2.1)
>>>>> vagrant-cachier (1.2.1)
>>>>> vagrant-omnibus (1.5.0)
>>>>> vagrant-share (1.1.7, system)
>>>>> vagrant-vbguest (0.13.0)
>>>>>
>>>>> Virtualbox version is 5.
>>>>>
>>>>> the vagrant up <windows box> fails at
>>>>>
>>>>> "Renaming the Windows guest failed. Most often this is because you've
>>>>> specified a FQDN instead of just a host name."
>>>>>
>>>>> the whole setup is, after the machine is setup it should integrate with
>>>>> chef.
>>>>>
>>>>> I have setup the "winrm" as a communicator.
>>>>>
>>>>> Regards,
>>>>>
>>>>>
--
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/111eafdb-37e4-4545-8ab2-62a5673307ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
