Uploaded image for project: 'Puppet Enterprise (moved to puppet.atlassian.net)'
  1. Puppet Enterprise (moved to puppet.atlassian.net)
  2. ENTERPRISE-181

Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • PE 3.2.3
    • PE 2015.2.0
    • Agent Installer
    • Windows 8.0 64bit using the puppet-enterprise-3.2.3.msi installer

    • puppet-enterprise-3.2.3.msi

    Description

      I was creating a masterless puppet agent on a fresh Windows 8 installation, so I installed the Puppet agent with the following command line;

      MSIEXEC /i "<source>\puppet-enterprise-3.2.3.msi" PUPPET_AGENT_STARTUP_MODE=Disabled REBOOT=ReallySuppress ALLUSERS=1 /qb- /l*v "c:\PuppetAgent.Install.log"
      

      Then I tried to run a Puppet Apply with the following command line;

      C:\Windows\SysWOW64\cmd.exe /E:ON /C ""C:\Program Files (x86)\Puppet Labs\Puppet Enterprise\bin\puppet.bat" apply --modulepath="%LOCALSRC%\modules" "%LOCALSRC%\manifests\site.pp""
      

      However i received an error that it could not created resources.dot. It was trying to create it in C:\ProgramData\PuppetLabs\puppet\var\state\graphs which looks like the expected place, however the directory structure was incomplete. Only C:\ProgramData\PuppetLabs\puppet\var existed. If I manually created this directory (MD C:\ProgramData\PuppetLabs\puppet\var\state\graphs) and then ran Puppet Apply it executed fine.

      It seems like that the code that creates the resources.dot file does not check for the existence of the dependent directory structure first.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Glenn Sarti Glenn Sarti
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support