Bug #2013

mountpoint is added every run to /etc/fstab

Added by Peter Meier almost 3 years ago. Updated almost 3 years ago.

Status:Closed Start date:02/22/2009
Priority:Normal Due date:
Assignee:James Turnbull % Done:

0%

Category:-
Target version:0.24.8
Affected Puppet version:0.24.7 Branch:
Keywords:
Votes: 0

Description

While testing HEAD of 0.24.x I discovered that mountpoints are added every run to the /etc/fstab and tried to be reloaded. This behaviour is not in 0.24.7

History

Updated by James Turnbull almost 3 years ago

  • Status changed from Unreviewed to Accepted
  • Target version changed from 0.24.7 to 0.24.8

Updated by Peter Meier almost 3 years ago

immerda wrote:'

While testing HEAD of 0.24.x I discovered that mountpoints are added every run to the /etc/fstab and tried to be reloaded. This behaviour is not in 0.24.7

it happens only if the mount parameter has an alias defined. With the following snippet I can reproduce the error:

file{['/tmp/a', '/tmp/b' ]:
    ensure => directory,
}

mount{'test_mount':
    name => '/tmp/a',
        atboot => true,
        device => '/tmp/b',
        ensure => mounted,
        fstype => none,
        options => 'bind',
    remounts => true,
}

leaving ‘test_mount’ away the problem doesn’t occure.

Updated by Luke Kanies almost 3 years ago

  • Assignee set to Luke Kanies

To clarify, is this behaviour in 0.24.7 if you do have an alias?

I don’t think I changed anything about mounts since 0.24.7.

Updated by Luke Kanies almost 3 years ago

  • Status changed from Accepted to In Topic Branch Pending Review
  • Assignee changed from Luke Kanies to James Turnbull

Pushed in tickets/0.24.x/2013 in my repo.

Updated by James Turnbull almost 3 years ago

  • Status changed from In Topic Branch Pending Review to Closed

Pushed in commit:9577d3af929727ac1e7b5e7e54e4491990d55995 in branch 0.24.x

Also available in: Atom PDF