Issue #22383 has been updated by Andrew Parker. Target version set to 3.3.0
I think the right fix for this is a combination of what Stefan and Josh are saying. The parameter should be declared as `:boolean` to allow various ways of specifying "true" and "false", which is good because it doesn't leak the implementation detail that solaris only accepts "yes" and "no" and fits with a user's mental model about that parameter. Then the provider for solaris should be updated to translate those true and false values to "yes" and "no" as needed. ---------------------------------------- Bug #22383: mount no longer allows true or false for atboot https://projects.puppetlabs.com/issues/22383#change-97178 * Author: Chuck Schweizer * Status: Accepted * Priority: Normal * Assignee: * Category: * Target version: 3.3.0 * Affected Puppet version: 3.3.0-rc2 * Keywords: * Branch: ---------------------------------------- Error: Failed to apply catalog: Parameter atboot failed on Mount[/home]: Invalid value true. Valid values are yes, no. mount { '/home': ensure => 'mounted', device => '/dev/mapper/rootvg-lv_home', fstype => 'ext4', options => 'defaults,nodev', dump => '1', pass => '2', remounts => true, atboot => true, } -- 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.
