Issue #22769 has been updated by Stefan Schulte.

Status changed from Unreviewed to Needs More Information

The `atboot` property is a mandatory field in Solaris `/etc/vfstab` file and 
should only be set to `yes` or `no` so your first example will actually create 
an invalid `/etc/vfstab` entry according to 
http://docs.oracle.com/cd/E19455-01/805-7228/6j6q7uev3/index.html (if you run 
puppet >3.3, you'll be able to use `true`/`false` as an alias for `yes`/`no` 
though - see #22383)

Linux does not use `/etc/vfstab` but `/etc/fstab` which has a different format 
that does not feature an `atboot` field so the `atboot` property is completly 
ignored on Linux (you'll have to use the `auto`/`noauto` boot options to get 
the same effect).

Having said that puppet should always complain on solaris if you do not specify 
`atboot` *unless* the resource is already present and puppet only has to modify 
an already existent entry that already has an `atboot` value. Can you please 
verify that you have tested both puppet versions under the same circumstances 
(mount point already present in `/etc/vfstab` or mount point absent prior to 
running puppet)?

About your last example: It should work when you put quotation marks around 
`false` but as I said at the beginning, `false` is not really valid in 
`/etc/vfstab`, so you should use `no` here.

----------------------------------------
Bug #22769: mount{} type on Solaris 10 requires 'atboot' option to be set to 
true.
https://projects.puppetlabs.com/issues/22769#change-98791

* Author: Paul Lussier
* Status: Needs More Information
* Priority: Normal
* Assignee: 
* Category: Solaris
* Target version: 
* Affected Puppet version: 2.7.21
* Keywords: mount solaris
* Branch: 
----------------------------------------
$mountops  = 'proto=tcp,vers=3,rsize=32768,wsize=32768,noexec,nosuid,rw,bg,hard\
,intr'
$fs = '/foo'

# This works fine
mount {
  $fs :
    device      => "${nfs_server}:${fs}",
    atboot      => true,
    ensure      => mounted,
    fstype      => 'nfs',
    blockdevice => '-',
    options     => $mountops,
    dump        => 1;                                                           
}

#####
# The following fail
#####
mount {
  $fs :
    device      => "${nfs_server}:${fs}",
    ensure      => mounted,
    fstype      => 'nfs',
    blockdevice => '-',
    options     => $mountops,
    dump        => 1;                                                           
}

mount {
  $fs :
    device      => "${nfs_server}:${fs}",
    atboot      => false,
    ensure      => mounted,
    fstype      => 'nfs',
    blockdevice => '-',
    options     => $mountops,
    dump        => 1;                                                           
}

The error message provided for the last two calls to mount is:

"err: /Stage[main]/Mount[/foo]/ensure: change from absent to mounted failed: 
Got a nil value for should at /etc/puppet/manifests/nodes.pp:68"

This does not occur on Linux, or with puppet 2.7.9 and earlier.



-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to