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

Managed files on FUSE without chmod/chown functionality

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: PUP 2.7.23, PUP 3.6.2, PUP 4.5.0
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Labels:
    • Environment:
      • Debian Wheezy 7.5
      • Proxmox [pve-manager/3.2-4/e24a91c1 (running kernel: 2.6.32-27-pve)]
    • Template:
    • UX Priority:
      Major

      Description

      Since an upgrade of puppet agent from (2.7.18-5) to (2.7.23-1) puppet is unable to manage files on FUSE-Filesystem pmxcfs.

      pmxcfs is a filesystem without owner and permissions. (https://pve.proxmox.com/wiki/Proxmox_Cluster_file_system_%28pmxcfs%29)

      Puppets temporary file handling got changed in between, that it calls tempfile.chown as well as tempfile.chmod on every run the target file should change. Puppet skips the resource with "failed: Function not implemented" error.
      ( see in function Puppet.Util.replace_file() )

      The origin version 2.7.18 tempfile handling was more acceptable, because it kept the current values of mode, uid and gid without trying to set it every time.

      I've also tried to set current owner and mode in puppet - which would be a acceptable workaround for me - but it did not work because tempfile handling.

      Maybe you could offer an option to define a different path for tempfiles which would relax the situation too.

      I've tried to change this behavior by writing another file-provider but tempfile-handling is done in core util class.

      For me that is a real major bug because it changes a core functionality of puppet within a minor-update!

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              blogbasti blogbasti
              QA Contact:
              Narmadha Perumal
            • Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support