Uploaded image for project: 'Puppet Development Kit'
  1. Puppet Development Kit
  2. PDK-546

Unable to pdk validate existing IIS module on Windows

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Windows 10
      PDK 1.1.0
      Puppetlabs-iis module

    • QA Risk Assessment:
      Needs Assessment

      Description

      I tried to do a pdk validate on the puppetlabs-iis module on Windows 10 however I received the following issue;

      ...
      Fetching fog-vmfusion 0.1.0
      Installing fog-vmfusion 0.1.0
      Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
       
      C:/PROGRA~1/PUPPET~1/DevelopmentKit/private/ruby/2.1.9/bin/ruby.exe -r
      ...
      An error occurred while installing ruby-ll (2.1.2), and Bundler cannot continue.
      Make sure that `gem install ruby-ll -v '2.1.2'` succeeds before bundling.
       
      In Gemfile:
        puppet-module-win-system-r2.1 was resolved to 0.1.1, which depends on
          beaker-module_install_helper was resolved to 0.1.5, which depends on
            beaker was resolved to 3.25.0, which depends on
              beaker-puppet was resolved to 0.7.0, which depends on
                oga was resolved to 2.11, which depends on
                  ruby-ll
      ...
      

      This was using the puppetlabs-iis module (although not created FROM PDK) at master (23d2964832aac1f12b579f3eb3cad744ff1b7e04)

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  glenn.sarti Glenn Sarti
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support