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

custom mountpoints do not work

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: PUP 3.3.1, PUP 3.3.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Ruby 1.8.7 (but should not matter)

    • Template:

      Description

      I have the same problem as in the question puppetAsk#2838.

      to reproduce make a module with this init.pp

      class demo_module {
      file

      Unknown macro: { 'a_directory' }

      }

      and fileserver.con

      [my_mount]
      /some/path
      allow *

      create /some/path/test_dir/ and a textfile there
      include demo_module in some node and shedule a puppet run for that node

      I did a little more digging and found that the path passed inside the request to puppet::indirector::file_server.rb is nil. But I am new to ruby and puppet, so I have no clue where to procede from that point.

      UPDATE:
      I found the problem. It is actualy a combination of suboptimal error handling in puppet and a typro on user side. If you use custom mount points and misstype the file name of the fileserver.conf, puppet returns the errormessage for missing files of an inbuild mount point instead of reporting unknown mountpoint. What should happen is, if puppet finds a reference for an unknown mountpoint and no config file, it should tell the user 'no coustom mountpoints defined: fileserver config missing?'. At the moment that case is not covered.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              pascal Pascal Flach
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support