Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

windows 2016 provisioning broken with chefdk 13 #90

Open
KirkMartinez opened this issue Jul 18, 2017 · 3 comments
Open

windows 2016 provisioning broken with chefdk 13 #90

KirkMartinez opened this issue Jul 18, 2017 · 3 comments

Comments

@KirkMartinez
Copy link

KirkMartinez commented Jul 18, 2017

At least I assume it's the ChefDK version since all the other deps are specified...and when I added "version": "12.19.36" to the chef-solo provisioner entries in vbox-2016.json it fixed it.

    virtualbox-iso: Synchronizing Cookbooks:
    virtualbox-iso: - wsus-client (1.2.1)
    virtualbox-iso: - packer-templates (0.1.0)
    virtualbox-iso: - windows (1.44.1)
    virtualbox-iso: - chef_handler (1.4.0)
    virtualbox-iso: Installing Cookbook Gems:
    virtualbox-iso: Compiling Cookbooks...
    virtualbox-iso:
    virtualbox-iso: ================================================================================
    virtualbox-iso: Recipe Compile Error in c:/windows/temp/packer-chef-solo/local-mode-cache/cache/cookbooks/packer-templates/recipes/uninstall_powershell_ise.rb
    virtualbox-iso: ================================================================================
    virtualbox-iso:
    virtualbox-iso: Chef::Exceptions::NoSuchResourceType
    virtualbox-iso: ------------------------------------
    virtualbox-iso: Cannot find a resource for windows_feature_dism on windows version 10.0.14393
    virtualbox-iso:
    virtualbox-iso: System Info:
    virtualbox-iso: ------------


    virtualbox-iso: chef_version=13.2.20
    virtualbox-iso: platform=windows
    virtualbox-iso: platform_version=10.0.14393
    virtualbox-iso: ruby=ruby 2.4.1p111 (2017-03-22 revision 58053) [x64-mingw32]
    virtualbox-iso: program_name=c:/opscode/chef/bin/chef-solo
    virtualbox-iso: executable=c:/opscode/chef/bin/chef-solo
    virtualbox-iso:
    virtualbox-iso:
    virtualbox-iso: Running handlers:
    virtualbox-iso: [2017-07-18T19:26:01+00:00] ERROR: Running exception handlers
    virtualbox-iso: Running handlers complete
    virtualbox-iso: [2017-07-18T19:26:01+00:00] ERROR: Exception handlers complete
    virtualbox-iso: Chef Client failed. 0 resources updated in 06 seconds
    virtualbox-iso: [2017-07-18T19:26:01+00:00] FATAL: Stacktrace dumped to c:/windows/temp/packer-chef-solo/local-mode-cache/cache/chef-stacktrace.out
    virtualbox-iso: [2017-07-18T19:26:01+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
    virtualbox-iso: [2017-07-18T19:26:01+00:00] FATAL: Chef::Exceptions::NoSuchResourceType: Cannot find a resource for windows_feature_dism on windows version 10.0.14393
    virtualbox-iso: c:/windows/temp/packer-chef-solo/local-mode-cache/cache/cookbooks/windows/resources/printer_port.rb:38: warning: constant ::Fixnum is deprecated
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Error executing Chef: Non-zero exit status: 1

==> Some builds didn't complete successfully and had errors:
--> virtualbox-iso: Error executing Chef: Non-zero exit status: 1

==> Builds finished but no artifacts were created.
@urisimchoni
Copy link
Contributor

"version" is supported by packer 1.0.1 or later.

@johnrizzo1
Copy link

Was this ever fixed. I have the same issue.

@scolligan
Copy link

scolligan commented Sep 21, 2017

I was having the same issue with the Chef 13 client. To work around it, I deleted:

.\cookbooks\packer-templates\Berksfile.lock

before I ran

berks vendor ../../vendor/cookbooks

This allowed berks to use the latest version of the Windows cookbook, which eliminates the error reported above. The Berksfile.lock file looked like this after running the berks vendor command:

DEPENDENCIES
  packer-templates
    path: .
    metadata: true

GRAPH
  ohai (5.2.0)
  packer-templates (0.1.0)
    windows (>= 0.0.0)
    wsus-client (>= 0.0.0)
  windows (3.1.3)
    ohai (>= 4.0.0)
  wsus-client (1.2.1)

This allowed me to successfully build with the vbox-2016.json template using Chef Client 13.4.24.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants