Issue #7300 has been updated by John Warburton.
Looks good to me on Solaris (after applying patch from issue #6845)
Unpatched 2.6.8
mount { '/system/object':
ensure => 'unmounted',
atboot => 'no',
blockdevice => '-',
device => 'objfs',
fstype => 'objfs',
options => '-',
pass => '-',
target => '/etc/vfstab',
}
mount { '/tmp':
ensure => 'unmounted',
atboot => 'yes',
blockdevice => '-',
device => 'swap',
fstype => 'tmpfs',
options => 'size=512m',
pass => '-',
target => '/etc/vfstab',
}
Patched with 7300
mount { '/system/object':
ensure => 'mounted',
atboot => 'no',
blockdevice => '-',
device => 'objfs',
fstype => 'objfs',
options => '-',
pass => '-',
target => '/etc/vfstab',
}
mount { '/tmp':
ensure => 'mounted',
atboot => 'yes',
blockdevice => '-',
device => 'swap',
fstype => 'tmpfs',
options => 'size=512m',
pass => '-',
target => '/etc/vfstab',
}
It has introduced these "ghost" mounts for my zfs mounts & Solaris bits and
bobs - does it mean anything?
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 5.68G 2.07G 97K /rpool
rpool/ROOT 4.74G 2.07G 21K legacy
rpool/ROOT/Solaris_10_U9 4.74G 2.07G 4.19G /
rpool/ROOT/Solaris_10_U9/var 563M 2.07G 563M /var
rpool/dump 250M 2.07G 250M -
rpool/local 343M 2.07G 25K /local
rpool/local/app 21K 2.07G 21K /local/app
rpool/local/home 4.82M 2.07G 4.82M /local/home
rpool/local/sendmail 338M 2.07G 338M /local/sendmail
rpool/swap 258M 2.25G 79.8M -
rpool/varcore 114M 2.07G 114M /var/core
mount { '/':
ensure => 'ghost',
}
. . .
mount { '/etc/mnttab':
ensure => 'ghost',
}
mount { '/etc/svc/volatile':
ensure => 'ghost',
}
mount { '/local':
ensure => 'ghost',
}
mount { '/local/app':
ensure => 'ghost',
}
mount { '/local/home':
ensure => 'ghost',
}
mount { '/local/sendmail':
ensure => 'ghost',
}
mount { '/platform/sun4v/lib/libc_psr.so.1':
ensure => 'ghost',
}
----------------------------------------
Bug #7300: "puppet resource mount" reports wrong mountstate
https://projects.puppetlabs.com/issues/7300
Author: Stefan Schulte
Status: Available In Testing Branch
Priority: Normal
Assignee: Stefan Schulte
Category: mount
Target version: 2.6.9
Affected Puppet version: 2.6.7
Keywords:
Branch: https://github.com/stschulte/puppet/tree/ticket/2.7.x/7300
In 2.6.7 the instances method of the mountprovider is broken:
<pre>
% puppet resource mount /
mount { '/':
ensure => 'unmounted', # obviously wrong
[...]
target => '/etc/fstab',
}
</pre>
Since puppet-2.6.7 the behaviour of the mounttype has changed (in order to fix
#4914). The Mounttype doesn't run the mountcommand anymore when `retrieve` is
called. Instead it relies on the prefetched value of the mountprovider.
But when running `puppet resource mount`, puppet uses the `instances` method
(instead of prefetch). Because the `instances` method just parses `/etc/fstab`
every mount is reported as `unmounted`.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
