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

[regression] Mount options not idempotent

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • PUP 4.8.0
    • PUP 4.8.1
    • Types and Providers
    • Debian 8, CentOS 7.2.1511

    • Agent
    • 3
    • AP 2016-11-16
    • Bug Fix
    • Hide
      In Puppet 4.8.0, we added new functionality to the mount provider intended to detect if a mounted filesystem did not match /etc/fstab. Unfortunately, there is not a reliable mechanism for doing this and the detection did not work as intended. It has been removed.
      Show
      In Puppet 4.8.0, we added new functionality to the mount provider intended to detect if a mounted filesystem did not match /etc/fstab. Unfortunately, there is not a reliable mechanism for doing this and the detection did not work as intended. It has been removed.

    Description

      After upgrading to Puppet 4.8.0, I keep seeing Puppet reports along the following lines:

      2016-11-02 09:32:16 +0100 /Stage[main]/Mount[/]/options (notice): options changed 'defaults,acl,user_xattr' to 'defaults,acl,user_xattr'
      2016-11-02 09:32:16 +0100 /Stage[main]/Mount[/] (notice): Triggered 'refresh' from 1 events
      2016-11-02 09:32:17 +0100 /Stage[main]/Mount[/var/redacted]/options (notice): options changed 'rw,bind,acl' to 'rw,bind,acl'
      2016-11-02 09:32:17 +0100 /Stage[main]/Mount[/var/redacted] (notice): Triggered 'refresh' from 1 events
      

      Even though the actual mount options are identical to the desired state, Puppet keeps thinking they are out-of-sync and re-mounting the mount point. This worked fine with Puppet 4.7.x.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              arnoutboks Arnout Boks
              Votes:
              4 Vote for this issue
              Watchers:
              22 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support