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

Mount resources could handle invalid options better

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.8.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Agent
    • Story Points:
      0
    • Sprint:
      AP 2016-09-21
    • CS Priority:
      Reviewed

      Description

      If I specify in a manifest:

      mount { '/var/tmp':
            ensure      => 'mounted',
            device      => '/dev/sdb1',
            fstype      => 'ext4',
            options     => 'ro,nosuid,noexec,foo,bar',
            atboot      => true,
            dump        => '0',
            pass        => '0',
            remounts => true,
          }
      

      ...puppet will add an entry to /etc/fstab:

      # cat /etc/fstab | grep /var/tmp
      /dev/sdb1	/var/tmp	ext4	ro,nosuid,noexec,foo,bar	  0	0
      

      ...and the remount attempt will spawn an error:

      Error: /Stage[main]/Mounts/Mount[/var/tmp]: Execution of '/bin/mount -o remount /var/tmp' returned 32: mount: /var/tmp not mounted already, or bad option
      

      ...however subsequent runs will not reattempt the remount and will ignore the discrepancy between /etc/fstab and the actual mounted volume.

      Could there be output in subsequent puppet runs that points out the discrepancy?

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  erik.hansen Erik Hansen
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  11 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support