You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that boxstarter fails to install when using this cookbook because the following commands in bootstrapper.ps1 ask the user for confirmation and the default answer is "no":
Here is a snippet from the choco log on the guest:
2015-04-18 04:42:09,218 [INFO ] - ============================================================
2015-04-18 04:42:09,250 [INFO ] - Chocolatey v0.9.9.4
2015-04-18 04:42:09,327 [INFO ] - Chocolatey is unpacking required files for use. Overwriting? True
2015-04-18 04:42:10,186 [INFO ] - ============================================================
2015-04-18 04:42:10,218 [INFO ] - Chocolatey v0.9.9.4
2015-04-18 04:42:10,296 [INFO ] - Chocolatey is unpacking required files for use. Overwriting? True
2015-04-18 04:42:11,108 [INFO ] - ============================================================
2015-04-18 04:42:11,139 [INFO ] - Chocolatey v0.9.9.4
2015-04-18 04:42:11,202 [INFO ] - Installing the following packages:
2015-04-18 04:42:11,202 [INFO ] - boxstarter.Common
2015-04-18 04:42:11,202 [INFO ] - By installing you accept licenses for the packages.
2015-04-18 04:42:18,218 [INFO ] -
BoxStarter.Common v2.4.205 (forced)
2015-04-18 04:42:18,249 [INFO ] - Found 'chocolateyinstall.ps1':
2015-04-18 04:42:18,249 [INFO ] -
$tools = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
. (Join-Path $tools Setup.ps1)
try {
$ModuleName = (Get-ChildItem $tools | ?{ $_.PSIsContainer }).BaseName
Install-Boxstarter "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" $ModuleName $env:chocolateyPackageParameters
Write-ChocolateySuccess $ModuleName
} catch {
Write-ChocolateyFailure $ModuleName "$($_.Exception.Message)"
throw
}
2015-04-18 04:42:18,265 [INFO ] -
Do you want to run the script?
NOTE: If you choose not to run the script, the installation will
fail.
Skip is an advanced option and most likely will never be wanted.
2015-04-18 04:42:18,265 [INFO ] - 1) yes
2015-04-18 04:42:18,265 [INFO ] - 2) no [Default - Press Enter]
2015-04-18 04:42:18,265 [INFO ] - 3) skip
2015-04-18 04:42:18,281 [ERROR] - boxstarter.common install not successful.
2015-04-18 04:42:18,281 [ERROR] - User cancelled powershell portion of installation for 'C:\ProgramData\chocolatey\lib\BoxStarter.Common\tools\chocolateyinstall.ps1'.
Use skip to install without run.
2015-04-18 04:42:20,311 [WARN ] -
Chocolatey installed 0/1 package(s). 1 package(s) failed.
See the log for details.
2015-04-18 04:42:20,311 [ERROR] - Failures:
2015-04-18 04:42:20,311 [ERROR] - - boxstarter.common
2015-04-18 04:42:20,749 [INFO ] - ============================================================
(it's the same for boxstarter.chocolatey, boxstarter.winconfig, and boxstarter.bootstrap)
My workaround was to add a '-y' switch to all cinst commands.
What makes this issue much more confusing - and harder to identify - is that the "kitchen converge" command with run-list=recipe[boxstarter::default] doesn't report any failures:
c:\chef-repo\cookbooks\tlv-dotnet>bundle exec kitchen converge
-----> Starting Kitchen (v1.4.0.rc.1)
-----> Converging <default-windows-2012R2>...
Preparing files for transfer
Preparing dna.json
Resolving cookbook dependencies with Berkshelf 3.2.3...
Removing non-cookbook files before transfer
Preparing solo.rb
-----> Chef Omnibus installation detected (install only if missing)
Transferring files to <default-windows-2012R2>
Starting Chef Client, version 12.2.1
Recipe: boxstarter::default
* directory[C:\Users\ADMINI~1\AppData\Local\Temp/boxstarter] action create (up to date)
* cookbook_file[bootstrapper.ps1] action create (up to date)
* template[C:\Users\ADMINI~1\AppData\Local\Temp/boxstarter/setup.bat] action create (up to date)
- execute C:\Users\ADMINI~1\AppData\Local\Temp/boxstarter/setup.bat
Running handlers:
Running handlers complete
Chef Client finished, 7/21 resources updated in 64.234364 seconds
Finished converging <default-windows-2012R2> (1m22.86s).
Please take a look - thanks!
-Omer
The text was updated successfully, but these errors were encountered:
Hi Matt,
I noticed that boxstarter fails to install when using this cookbook because the following commands in bootstrapper.ps1 ask the user for confirmation and the default answer is "no":
Here is a snippet from the choco log on the guest:
(it's the same for boxstarter.chocolatey, boxstarter.winconfig, and boxstarter.bootstrap)
My workaround was to add a '-y' switch to all cinst commands.
What makes this issue much more confusing - and harder to identify - is that the "kitchen converge" command with run-list=recipe[boxstarter::default] doesn't report any failures:
Please take a look - thanks!
-Omer
The text was updated successfully, but these errors were encountered: