Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-4045

Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket

    XMLWordPrintable

Details

    • Normal
    • Bug Fix
    • This release allows Puppet to retrieve attributes for `fifo` and `socket` files and manage them when given manifest has a `file` resource which is recursing over a given path.

    Description

      Using a slightly modified version of the code from "Pro Puppet" I am getting the following error:

          Jun 13 01:36:33 media puppet-agent[18196]: (/Stage[main]/Mysql::Config/File[mysql_data_dir]) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
      

      The file resource in mysql/manifests/config.pp is as follows:

          file { "mysql_data_dir" :
              path => $mysql::params::data_directory,
              group => "mysql",
              owner => "mysql",
              recurse => true,
              require => File["my.cnf"],
          }
      

      And for this particular $operatingsystem (Fedora) the value for $data_directory in mysql/manifests/params.pp is :

          $data_directory = "/var/lib/mysql"
      

      By default mysql on a Fedora system places its mysql.sock file in the data directory but it appears when a you try and change the permissions recursively, puppet doesn't know what to do with the socket file.

      I can place the socket file elsewhere as a work around but I believe that puppet needs to ignore socket files when changing permissions.

          [root@media modules]# puppet --version
          2.6.8
          [root@media modules]# puppet master --version
          2.6.8
      

      Attachments

        Issue Links

          Activity

            People

              luchian.nemes Luchian Nemes
              redmine.exporter redmine.exporter
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support