Error with vagrant 1.9.3 and virtualbox "Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name."
Locked
 
|
Hi,
-- I am trying setup a vagrant machine windows 2012r2. I am using 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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/d57fb571-4a23-4eb7-a314-f87e307f16f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
|
|
==> 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:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/1ee18733-371d-440f-86fe-28685fd5febb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
|
|
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:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/50463cea-401a-4b17-a85f-515fb706d786%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
|
|
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:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/563747a9-ee9c-4706-b5cb-b50162227be2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
|
|
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:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c2283042-6d74-4bcc-aef3-7499b625dbdb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
|
|
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:
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 [hidden email]. 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. |
Re: Error with vagrant 1.9.3 and virtualbox "Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name."
|
|
get into latest vagrant version do vagrant plugin list remove all plugin other than vagrant share do vagrant plugin update try again winrm is not part of core vagrant, so maybe having the old plugin and the new version cause issues Alvaro On Fri, Apr 14, 2017 at 5:58 PM, athreya vc <[hidden email]> wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exnDEKrAgbL0GzHm1kwgc-OiV0vRw9SqENqPKDdD29Auw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
|
|
Hi,
-- Thanks for the Reply. I am wondering with 1.6.3 vagrant is using a different way to communicate to the guest VM and 1.9.3 it has changed, I have now cleaned up all the old plugins. Now I have the latest version vagrant -v Vagrant 1.9.3 With below plugins vagrant plugin list vagrant-butcher (2.2.1) vagrant-share (1.1.7, system) vagrant-vbguest (0.13.0) I have cleared all the Plugins from the Previous. Same error Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name. Ensure the new guest name is properly formatted. Standard names may contain letters (a-z, A-Z), numbers (0-9), and hypens (-), but no spaces or periods (.). The name may not consist entirely of digits. INFO interface: Machine: error-exit ["VagrantPlugins::GuestWindows::Errors::RenameComputerFailed", "Renaming the Windows guest failed. Most often this is because you've\nspecified a FQDN instead of just a host name.\n\nEnsure the new guest name is properly formatted. Standard names may\ncontain letters (a-z, A-Z), numbers (0-9), and hypens (-), but no\nspaces or periods (.). The name may not consist entirely of digits."] In Debug, On Friday, 14 April 2017 20:05:51 UTC+1, Alvaro Miranda Aguilera wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/d5798e61-ac62-44fc-981a-4524c0b47a0d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
|
|
Debug Log DEBUG winrmshell: Output: #<WinRM::Output:0x00000004260ff8 @data=[{:stderr=>"At line:1 char:3\r\n+ if test -r /etc/os-release; then\r\n+ ~\nMissing '(' after 'if' in if statement.\r\n\r\nAt line:2 char:24\r\n+ source /etc/os-release && test 'xlinux' = \"x$ID\" && exit\r\n+ ~~\nThe token '&&' is not a valid statement separator in this version.\r\n\r\nAt line:2 char:50\r\n+ source /etc/os-release && test 'xlinux' = \"x$ID\" && exit\r\n+ ~~\nThe token '&&' is not a valid statement separator in this version.\r\n\r\nAt line:4 char:3\r\n+ if test -x /usr/bin/lsb_release; then\r\n+ ~\nMissing '(' after 'if' in if statement.\r\n\r\nAt line:5 char:56\r\n+ /usr/bin/lsb_release -i 2>/dev/null | grep -qi 'linux' && exit\r\n+ ~~\nThe token '&&' is not a valid statement separator in this version.\r\n\r\nAt line:7 char:3\r\n+ if test -r /etc/issue; then\r\n+ ~\nMissing '(' after 'if' in if statement.\r\n\r\nAt line:8 char:35\r\n+ cat /etc/issue | grep -qi 'linux' && exit\r\n+ ~~\nThe token '&&' is not a valid statement separator in this version.\r\n\r\n\n + CategoryInfo : ParserError: (:) [Invoke-Expression], ParseException\n + FullyQualifiedErrorId : MissingOpenParenthesisInIfStatement,Microsoft.PowerShell.Commands.InvokeExpressionCommand\n"}], @exitcode=0> WARN winrmshell: Detected ParserError, setting exit code to 1 DEBUG guest: Trying: esxi DEBUG guest: Trying: solaris11 DEBUG guest: Trying: bsd DEBUG guest: Trying: windows DEBUG winrmshell: [WinRM] opening remote shell on http://127.0.0.1:55985/wsman DEBUG winrmshell: [WinRM] Waiting for output... DEBUG winrmshell: [WinRM] Processing output DEBUG winrmshell: [WinRM] polling for pipeline state. message: #<WinRM::PSRP::Message:0x00000004139710 @data="\xEF\xBB\xBF<Obj RefId=\"0\"><MS><Version N=\"protocolversion\">2.2</Version><Version N=\"PSVersion\">2.0</Version><Version N=\"SerializationVersion\">1.1.0.1</Version></MS></Obj>", @destination=1, @type=65538, @pipeline_id="00000000-0000-0000-0000-000000000000", @runspace_pool_id="00000000-0000-0000-0000-000000000000"> DEBUG winrmshell: [WinRM] polling for pipeline state. message: #<WinRM::PSRP::Message:0x00000004133bd0 @data="\xEF\xBB\xBF<Obj RefId=\"0\"><MS><Obj N=\"ApplicationPrivateData\" RefId=\"1\"><TN RefId=\"0\"><T>System.Management.Automation.PSPrimitiveDictionary</T><T>System.Collections.Hashtable</T><T>System.Object</T></TN><DCT><En><S N=\"Key\">DebugMode</S><I32 N=\"Value\">1</I32></En><En><S N=\"Key\">DebugStop</S><B N=\"Value\">false</B></En><En><S N=\"Key\">PSVersionTable</S><Obj N=\"Value\" RefId=\"2\"><TNRef RefId=\"0\" /><DCT><En><S N=\"Key\">PSVersion</S><Version N=\"Value\">2.0</Version></En><En><S N=\"Key\">PSCompatibleVersions</S><Obj N=\"Value\" RefId=\"3\"><TN RefId=\"1\"><T>System.Version[]</T><T>System.Array</T><T>System.Object</T></TN><LST><Version>1.0</Version><Version>2.0</Version><Version>3.0</Version><Version>4.0</Version></LST></Obj></En><En><S N=\"Key\">BuildVersion</S><Version N=\"Value\">6.3.9600.16394</Version></En><En><S N=\"Key\">CLRVersion</S><Version N=\"Value\">4.0.30319.42000</Version></En><En><S N=\"Key\">WSManStackVersion</S><Version N=\"Value\">3.0</Version></En><En><S N=\"Key\">PSRemotingProtocolVersion</S><Version N=\"Value\">2.2</Version></En><En><S N=\"Key\">SerializationVersion</S><Version N=\"Value\">1.1.0.1</Version></En></DCT></Obj></En><En><S N=\"Key\">DebugBreakpointCount</S><I32 N=\"Value\">0</I32></En></DCT></Obj></MS></Obj>", @destination=1, @type=135177, @pipeline_id="00000000-0000-0000-0000-000000000000", @runspace_pool_id="00000000-0000-0000-0000-000000000000"> DEBUG winrmshell: [WinRM] Waiting for output... DEBUG winrmshell: [WinRM] Processing output DEBUG winrmshell: [WinRM] polling for pipeline state. message: #<WinRM::PSRP::Message:0x0000000407bd00 @data="\xEF\xBB\xBF<Obj RefId=\"0\"><MS><I32 N=\"RunspaceState\">2</I32></MS></Obj>", @destination=1, @type=135173, @pipeline_id="00000000-0000-0000-0000-000000000000", @runspace_pool_id="00000000-0000-0000-0000-000000000000"> DEBUG winrmshell: [WinRM] remote shell created with shell_id: D5F3BBCD-AB9D-4BC1-A2EF-7058F714A906 DEBUG winrmshell: [WinRM] Command created for $p = "$Env:SystemRoot" if ((Test-Path $p) -and (get-item $p).PSIsContainer) { exit 0 } exit 1 if (!$?) { if($LASTEXITCODE) { exit $LASTEXITCODE } else { exit 1 } } with id: 0F07AD8A-FC5F-4983-AD5C-4E5AE9998CD9 DEBUG winrmshell: [WinRM] creating command_id: 0F07AD8A-FC5F-4983-AD5C-4E5AE9998CD9 on shell_id D5F3BBCD-AB9D-4BC1-A2EF-7058F714A906 DEBUG winrmshell: [WinRM] Waiting for output... DEBUG winrmshell: [WinRM] Processing output DEBUG winrmshell: [WinRM] cleaning up command_id: 0F07AD8A-FC5F-4983-AD5C-4E5AE9998CD9 on shell_id D5F3BBCD-AB9D-4BC1-A2EF-7058F714A906 DEBUG winrmshell: Output: #<WinRM::Output:0x000000033384b8 @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: [WinRM] opening remote shell on http://127.0.0.1:55985/wsman DEBUG winrmshell: [WinRM] Waiting for output... DEBUG winrmshell: [WinRM] Processing output DEBUG winrmshell: [WinRM] polling for pipeline state. message: #<WinRM::PSRP::Message:0x0000000330b2b0 @data="\xEF\xBB\xBF<Obj RefId=\"0\"><MS><Version N=\"protocolversion\">2.2</Version><Version N=\"PSVersion\">2.0</Version><Version N=\"SerializationVersion\">1.1.0.1</Version></MS></Obj>", @destination=1, @type=65538, @pipeline_id="00000000-0000-0000-0000-000000000000", @runspace_pool_id="00000000-0000-0000-0000-000000000000"> DEBUG winrmshell: [WinRM] polling for pipeline state. message: #<WinRM::PSRP::Message:0x00000003308f60 @data="\xEF\xBB\xBF<Obj RefId=\"0\"><MS><Obj N=\"ApplicationPrivateData\" RefId=\"1\"><TN RefId=\"0\"><T>System.Management.Automation.PSPrimitiveDictionary</T><T>System.Collections.Hashtable</T><T>System.Object</T></TN><DCT><En><S N=\"Key\">DebugMode</S><I32 N=\"Value\">1</I32></En><En><S N=\"Key\">DebugStop</S><B N=\"Value\">false</B></En><En><S N=\"Key\">PSVersionTable</S><Obj N=\"Value\" RefId=\"2\"><TNRef RefId=\"0\" /><DCT><En><S N=\"Key\">PSVersion</S><Version N=\"Value\">2.0</Version></En><En><S N=\"Key\">PSCompatibleVersions</S><Obj N=\"Value\" RefId=\"3\"><TN RefId=\"1\"><T>System.Version[]</T><T>System.Array</T><T>System.Object</T></TN><LST><Version>1.0</Version><Version>2.0</Version><Version>3.0</Version><Version>4.0</Version></LST></Obj></En><En><S N=\"Key\">BuildVersion</S><Version N=\"Value\">6.3.9600.16394</Version></En><En><S N=\"Key\">CLRVersion</S><Version N=\"Value\">4.0.30319.42000</Version></En><En><S N=\"Key\">WSManStackVersion</S><Version N=\"Value\">3.0</Version></En><En><S N=\"Key\">PSRemotingProtocolVersion</S><Version N=\"Value\">2.2</Version></En><En><S N=\"Key\">SerializationVersion</S><Version N=\"Value\">1.1.0.1</Version></En></DCT></Obj></En><En><S N=\"Key\">DebugBreakpointCount</S><I32 N=\"Value\">0</I32></En></DCT></Obj></MS></Obj>", @destination=1, @type=135177, @pipeline_id="00000000-0000-0000-0000-000000000000", @runspace_pool_id="00000000-0000-0000-0000-000000000000"> DEBUG winrmshell: [WinRM] Waiting for output... DEBUG winrmshell: [WinRM] Processing output DEBUG winrmshell: [WinRM] polling for pipeline state. message: #<WinRM::PSRP::Message:0x00000002eacc00 @data="\xEF\xBB\xBF<Obj RefId=\"0\"><MS><I32 N=\"RunspaceState\">2</I32></MS></Obj>", @destination=1, @type=135173, @pipeline_id="00000000-0000-0000-0000-000000000000", @runspace_pool_id="00000000-0000-0000-0000-000000000000"> DEBUG winrmshell: [WinRM] remote shell created with shell_id: BCAB89AB-0027-473D-8ED4-62B7CD799241 DEBUG winrmshell: [WinRM] Command created for if ([System.Net.Dns]::GetHostName() -eq 'testwin001.homelab.com') { exit 0 } exit 1 if (!$?) { if($LASTEXITCODE) { exit $LASTEXITCODE } else { exit 1 } } with id: 92242FAE-9D8F-47BD-A5A9-0B8BC1B7443F DEBUG winrmshell: [WinRM] creating command_id: 92242FAE-9D8F-47BD-A5A9-0B8BC1B7443F on shell_id BCAB89AB-0027-473D-8ED4-62B7CD799241 DEBUG winrmshell: [WinRM] Waiting for output... DEBUG winrmshell: [WinRM] Processing output DEBUG winrmshell: [WinRM] cleaning up command_id: 92242FAE-9D8F-47BD-A5A9-0B8BC1B7443F on shell_id BCAB89AB-0027-473D-8ED4-62B7CD799241 DEBUG winrmshell: Output: #<WinRM::Output:0x000000040c68a0 @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: [WinRM] opening remote shell on http://127.0.0.1:55985/wsman DEBUG winrmshell: [WinRM] Waiting for output... DEBUG winrmshell: [WinRM] Processing output DEBUG winrmshell: [WinRM] polling for pipeline state. message: #<WinRM::PSRP::Message:0x000000040bb4c8 @data="\xEF\xBB\xBF<Obj RefId=\"0\"><MS><Version N=\"protocolversion\">2.2</Version><Version N=\"PSVersion\">2.0</Version><Version N=\"SerializationVersion\">1.1.0.1</Version></MS></Obj>", @destination=1, @type=65538, @pipeline_id="00000000-0000-0000-0000-000000000000", @runspace_pool_id="00000000-0000-0000-0000-000000000000"> DEBUG winrmshell: [WinRM] polling for pipeline state. message: #<WinRM::PSRP::Message:0x000000040ba258 @data="\xEF\xBB\xBF<Obj RefId=\"0\"><MS><Obj N=\"ApplicationPrivateData\" RefId=\"1\"><TN RefId=\"0\"><T>System.Management.Automation.PSPrimitiveDictionary</T><T>System.Collections.Hashtable</T><T>System.Object</T></TN><DCT><En><S N=\"Key\">DebugMode</S><I32 N=\"Value\">1</I32></En><En><S N=\"Key\">DebugStop</S><B N=\"Value\">false</B></En><En><S N=\"Key\">PSVersionTable</S><Obj N=\"Value\" RefId=\"2\"><TNRef RefId=\"0\" /><DCT><En><S N=\"Key\">PSVersion</S><Version N=\"Value\">2.0</Version></En><En><S N=\"Key\">PSCompatibleVersions</S><Obj N=\"Value\" RefId=\"3\"><TN RefId=\"1\"><T>System.Version[]</T><T>System.Array</T><T>System.Object</T></TN><LST><Version>1.0</Version><Version>2.0</Version><Version>3.0</Version><Version>4.0</Version></LST></Obj></En><En><S N=\"Key\">BuildVersion</S><Version N=\"Value\">6.3.9600.16394</Version></En><En><S N=\"Key\">CLRVersion</S><Version N=\"Value\">4.0.30319.42000</Version></En><En><S N=\"Key\">WSManStackVersion</S><Version N=\"Value\">3.0</Version></En><En><S N=\"Key\">PSRemotingProtocolVersion</S><Version N=\"Value\">2.2</Version></En><En><S N=\"Key\">SerializationVersion</S><Version N=\"Value\">1.1.0.1</Version></En></DCT></Obj></En><En><S N=\"Key\">DebugBreakpointCount</S><I32 N=\"Value\">0</I32></En></DCT></Obj></MS></Obj>", @destination=1, @type=135177, @pipeline_id="00000000-0000-0000-0000-000000000000", @runspace_pool_id="00000000-0000-0000-0000-000000000000"> DEBUG winrmshell: [WinRM] Waiting for output... DEBUG winrmshell: [WinRM] Processing output DEBUG winrmshell: [WinRM] polling for pipeline state. message: #<WinRM::PSRP::Message:0x0000000442a410 @data="\xEF\xBB\xBF<Obj RefId=\"0\"><MS><I32 N=\"RunspaceState\">2</I32></MS></Obj>", @destination=1, @type=135173, @pipeline_id="00000000-0000-0000-0000-000000000000", @runspace_pool_id="00000000-0000-0000-0000-000000000000"> DEBUG winrmshell: [WinRM] remote shell created with shell_id: A7F93B3D-C2D6-44EA-A8AB-B221A0C1ABD6 DEBUG winrmshell: [WinRM] Command created for $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 if (!$?) { if($LASTEXITCODE) { exit $LASTEXITCODE } else { exit 1 } } with id: 051C1478-DC21-4CD7-AE99-AAEEB279E7CE DEBUG winrmshell: [WinRM] creating command_id: 051C1478-DC21-4CD7-AE99-AAEEB279E7CE on shell_id A7F93B3D-C2D6-44EA-A8AB-B221A0C1ABD6 DEBUG winrmshell: [WinRM] Waiting for output... DEBUG winrmshell: [WinRM] Processing output DEBUG winrmshell: [WinRM] cleaning up command_id: 051C1478-DC21-4CD7-AE99-AAEEB279E7CE on shell_id A7F93B3D-C2D6-44EA-A8AB-B221A0C1ABD6 DEBUG winrmshell: Output: #<WinRM::Output:0x0000000321dba0 @data=[], @exitcode=87> ERROR warden: Error occurred: Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name. On Saturday, 15 April 2017 04:23:44 UTC+1, athreya vc wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/8d9055f6-85d5-4066-8f6e-0a251a36e6ca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
Re: Error with vagrant 1.9.3 and virtualbox "Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name."
|
|
In reply to this post by athreyavc
Hello When I wrote my previous mail i dd a typo, sorry winrm is NOW part of vagrant core, that changed so in old version and some plugins the wayt you setup stuff may be different this works for me Vagrant.configure("2") do |config| config.vm.box = "ferventcoder/win2008r2-x64-nocm" config.winrm.username = "vagrant" config.winrm.password = "vagrant" config.vm.communicator = "winrm" config.vm.guest = :windows config.vm.network :forwarded_port, guest: 3389, host: 3389, id: "rdp", auto_correct: true config.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct: true config.vm.provision "shell", inline: "Write-Host Hello World" config.vm.provision "shell", inline: "(Get-UICulture).Calendar | ConvertTo-Json" end 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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyFaTCTSKEZvf6smCN%3DmQVGmPSZxOEvQ83%3DMojCFYti1w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
|
|
Hi,
-- For me I keep getting this ==> win001: Starting Chef Client, version 12.10.24 INFO interface: info: [2017-04-15T16:33:21+01:00] INFO: *** Chef 12.10.24 *** INFO interface: info: ==> win001: [2017-04-15T16:33:21+01:00] INFO: *** Chef 12.10.24 *** ==> win001: [2017-04-15T16:33:21+01:00] INFO: *** Chef 12.10.24 *** INFO interface: info: [2017-04-15T16:33:21+01:00] INFO: Platform: i386-mingw32 INFO interface: info: ==> win001: [2017-04-15T16:33:21+01:00] INFO: Platform: i386-mingw32 ==> win001: [2017-04-15T16:33:21+01:00] INFO: Platform: i386-mingw32 INFO interface: info: [2017-04-15T16:33:21+01:00] INFO: Chef-client pid: 2240 INFO interface: info: ==> win001: [2017-04-15T16:33:21+01:00] INFO: Chef-client pid: 2240 ==> win001: [2017-04-15T16:33:21+01:00] INFO: Chef-client pid: 2240 DEBUG winrmshell: [WinRM] Waiting for output... It seems to me winrm is not working at all. I am trying some more. Regards, On Saturday, 15 April 2017 10:56:14 UTC+1, Alvaro Miranda Aguilera wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/05821761-03b1-40c2-8597-e06b44723fbb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
Re: Error with vagrant 1.9.3 and virtualbox "Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name."
|
|
did you try my example? On Sat, Apr 15, 2017 at 5:35 PM, athreya vc <[hidden email]> wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ey0MsaftLxLCOb1Y%3D%3DVdRqACX5KrfVjw4PDgOf2%3DskTAA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
|
|
Thanks for helping me out here.
-- Yes I did and it did work with this. "win001" works. If I have to make it "win001.homelab.com" it fails. Vagrant.configure("2") do |config| config.vm.box = "livedrive-vagrantlab-win2012r2-v6" config.winrm.username = "Administrator" config.vm.hostname = "win001" # If I put win001.homelab.com it will fail config.winrm.password = "Liverp00l" config.vm.communicator = "winrm" config.vm.guest = :windows config.vm.network :forwarded_port, guest: 3389, host: 3389, id: "rdp", auto_correct: true config.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct: true config.vm.provision "shell", inline: "Write-Host Hello World" config.vm.provision "shell", inline: "(Get-UICulture).Calendar | ConvertTo-Json" end Now I am confused :(. My setup is, there is a PowerShell script which renames the VM. AFter renaming Chef Provisioning takes place, and I see client.pem is also not getting copied. On Saturday, 15 April 2017 17:37:49 UTC+1, Alvaro Miranda Aguilera wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/aa880bca-c99f-401b-b5a0-f2dc26594be5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
Re: Error with vagrant 1.9.3 and virtualbox "Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name."
|
|
try disabling the firewall and try again On Sat, Apr 15, 2017 at 9:28 PM, athreya vc <[hidden email]> wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ey8XKpYTpnyTi4BEC0FvfCdfVwZ0r-1jQ_F_xEqoJy3OA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
|
|
Hi,
-- This is my Vagrantfile. Your example works, however with this I get Error #$chef_server_url = "https://api.chef.io/organizations/test-lab-athreya" #$chef.validation_client_name = "test-lab-athreya-validator" #$chef.client_key_path = "/etc/chef/client.pem" #$chef.validation_key_path = "/home/learn/Downloads/validation.pem" $env_domain = 'homelab.com' guests = { :ubuntu => { :singleton => true, :box => 'hashicorp/precise64', :public_network => { :bridge => 'wlp3s0', :ip => '192.168.1.12', :netmask => '255.255.255.0', :gw => '192.168.1.254' }, :chef_recipes => ["motd"], :vb_memory => 1024 }, :win => { :singleton => true, :box => 'kensykora/windows_2012_r2_standard', :public_network => { :bridge => 'wlp3s0', :ip => '192.168.1.14', :netmask => '255.255.255.0', :gw => '192.168.1.254' }, :chef_recipes => ["chocolatey"], :vb_memory => 4096 } } Vagrant.configure("2") do |global_config| guests.each_pair do | name, options | names = [name] names.each do |name| global_config.vm.define name do |config| guest_is_windows = options[:box].include? 'windows' config.vm.hostname = "#{name}.homelab.com" config.vm.box = options[:box] config.butcher.enabled = true config.butcher.verify_ssl = false config.omnibus.chef_version = :latest pub=options [:public_network] config.vm.network 'public_network', :bridge => pub[:bridge], :ip => pub[:ip], :netmask => pub[:netmask], :gw => pub[:gw] if guest_is_windows config.winrm.username = "vagrant" config.winrm.password = "vagrant" config.vm.communicator = "winrm" config.vm.guest = :windows config.vm.network :forwarded_port, guest: 3389, host: 3389, id: "rdp", auto_correct: true config.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct: true config.vm.hostname = "#{name}" $hostname = "#{name}.homelab.com" config.vm.provision "shell", inline: "(Get-WmiObject Win32_ComputerSystem).Rename($hostname)" else config.ssh.username = "vagrant" config.vm.hostname = "#{name}.homelab.com" end config.vm.provision :chef_client do |chef| chef.node_name = "#{name}" if guest_is_windows chef.provisioning_path = 'c:\\chef' else chef.provisioning_path = "/etc/chef" end chef.chef_server_url = "https://api.chef.io/organizations/test-lab-athreya" chef.validation_client_name = "test-lab-athreya-validator" chef.validation_key_path = "/home/learn/Downloads/validation.pem" options[:chef_recipes].each do | recipe | chef.add_recipe recipe end end end end end end INFO interface: error: Chef never successfully completed! Any errors should be visible in the output above. Please fix your recipes so that they properly complete. Chef never successfully completed! Any errors should be visible in the output above. Please fix your recipes so that they properly complete. INFO interface: Machine: error-exit ["VagrantPlugins::Chef::Provisioner::Base::ChefError", "Chef never successfully completed! Any errors should be visible in the\noutput above. Please fix your recipes so that they properly complete."] On Saturday, 15 April 2017 21:18:53 UTC+1, Alvaro Miranda Aguilera wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6783003f-b1a7-4634-aa42-27026957a60e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
Re: Error with vagrant 1.9.3 and virtualbox "Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name."
|
|
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 the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezwqYt7x_xzfa0-BYeo8yw6SF9pMHbGV7k4zkV_N-apWQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
|
|
I just tried that, Removed the renaming part, just left it to "win". to keep it simple. Still the error is same. 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 <[hidden email]> wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAK-gxkPNMuDrAk9vbR9nrg-tg%3DSGKs4NwGVTbt1Tu6zsa2swHQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
Re: Error with vagrant 1.9.3 and virtualbox "Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name."
|
|
Thanks Can you open a issue on GitHub and share a reproducible project? Thanks! Alvaro On Sun, Apr 16, 2017 at 2:50 PM, athreyavc <[hidden email]> wrote:
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 [hidden email]. 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. |
|
|
Hi Sure, I can Open a Bug. Meanwhile any other version you know I can use? I really need to get this working. It was somehow working with 1.6.3, but now vagrant-butcher seem to be not compatible with version 1.6.3 Just can't get it installed. Regards, On Sun, Apr 16, 2017 at 2:32 PM, Alvaro Miranda Aguilera <[hidden email]> wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAK-gxkNa%3D3C_U-LgdLaZJr6y9p_Qz5eHwxVH_F0619kRus1M5A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
|
|
Hi,
-- I have made a good progress on this and it seem to be working for me now https://github.com/athreyavc1/testingchef/blob/master/Vagrantfile Thanks a lot helping me out. Regards, A On Sunday, 16 April 2017 14:39:36 UTC+1, athreya vc wrote:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/37a5f2eb-33f6-45b5-8992-d373438465b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
«
Return to Vagrant
|
1 view|%1 views
| Free forum by Nabble | Edit this page |