Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-8821

puppet_agent installer not upgrading windows nodes when in a non-production environment

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • puppet_agent 2.1.1
    • puppet_agent
    • None
    • Skeletor
    • 1
    • Skeletor Kanban
    • Needs Assessment
    • 34018
    • 1
    • Not Needed
    • Needs Assessment

    Description

      puppet_agent installer not upgrading windows nodes when in a non-production environment

       

      To replicate issue:

       Install 1.10.5 on windows agent.

      Classify node to agent specified environment ‘test’

      Run puppet agent on ‘test’ environment

      Attempt to upgrade using puppet_agent module to 5.5.8

      On puppet run 'Puppet_agent::Windows::Install/Exec[install_puppet.ps1]/returns: executed successfully' is shown however the agent is not upgraded

      Error shown in installer log:

      C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'test' anywhere in the path: C:/ProgramData/PuppetLabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound)

      No test folder located in C:/ProgramData/PuppetLabs/code/environments - only production

      Deleting the production folder will result in an empty being recreated on the next puppet run if environment set to production.

      Creating an empty test folder in the directory manually will allow the upgrade to complete

       

      There is another bug regarding environments and the puppet_agent module:

      https://tickets.puppetlabs.com/browse/MODULES-4730 

       I tested the associated pull request but this didn't resolve this new issue.

       

      Attachments

        Issue Links

          Activity

            People

              sean.mcdonald Sean McDonald
              elaine.mccloskey Elaine McCloskey
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support