[Puppet Users] Announcement: Release of Bolt 0.25.0
Hello Everyone! We kick off the month with the release of Bolt 0.25.0. Added in this release is a return value for the apply action and a handful of bug fixes. For more information, see: https://puppet.com/docs/bolt/0.x/bolt_release_notes.html To try this new version, follow the installation instructions for your operating system at: https://puppet.com/docs/bolt/0.x/bolt_installing.html Thanks! -- Kate Lopresti Senior Technical Writer kate.lopre...@puppet.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2B%2BkvarbYG8e5q%2BP4mFFEsXXoq5AYAYJdkJtV9Dnq5_oc31_-w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me
> I would expect this to get into 5.5.7 but can't promise yet. Brilliant - as long as it's not me being crazy. Thanks again. /Eirik -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/F1172FD8-CDC6-4E21-A4A1-B7BD2EA2DDBC%40anduin.net. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me
On Friday, October 5, 2018 at 11:22:30 AM UTC-7, Eirik Øverby wrote: > > > I've resuscitated my JIRA account, so if you wish to attach me to the > ticket in some way, my username is 'ltning'. > > I presume 5.5.7 should have this one fixed then? :) > > /Eirik I have set you as the Reporter. I would expect this to get into 5.5.7 but can't promise yet. -Kris -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/a2022c8f-f8af-4a13-b8ce-87fc65fd7278%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me
> Hi X, > > Nick Lewis helped me reproduce this issue with the extra module path, I have > filed https://tickets.puppetlabs.com/browse/PUP-9211 for the issue. > > Thanks! Thanks a *lot*! I've resuscitated my JIRA account, so if you wish to attach me to the ticket in some way, my username is 'ltning'. I presume 5.5.7 should have this one fixed then? :) /Eirik -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/660D6F34-A653-462E-B0EA-645CCA3228DB%40anduin.net. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me
On Friday, October 5, 2018 at 10:55:52 AM UTC-7, Eirik Øverby wrote:
>
> > Hi Eirik,
> >
> > I was unable to reproduce your issue in Puppet 5.5.6 (aka SHA 60de165
> from https://github.com/puppetlabs/puppet/releases):
> >
> > kris.bosland@kris:puppet % git checkout 60de165
>
>±[5.5.6^0]
> > HEAD is now at 60de165b86... Merge pull request #7007 from
> justinstoller/maint-pin-rake-more
> > kris.bosland@kris:puppet % cat ../tmp/test/bash/manifests/init.pp
>
>±[5.5.6^0]
> > class bash {
> > package { "shells/bash":
> > ensure => installed,
> > }
> > }
> >
> > class smash {
> > package { "shells/bash":
> > ensure => installed,
> > }
> > }
> > kris.bosland@kris:puppet % bx puppet apply --modulepath ../tmp/test -e
> 'class test { include bash }; include test'
> ±[5.5.6^0]
> > Warning: Unacceptable location. The name 'smash' is unacceptable in file
> '/Users/kris.bosland/work/tmp/test/bash/manifests/init.pp' (file:
> /Users/kris.bosland/work/tmp/test/bash/manifests/init.pp, line: 7, column:
> 1)
> > Notice: Compiled catalog for kris.bosland-c02kf9eafft1 in environment
> production in 0.56 seconds
> > Error: Mac OS X PKG DMGs must specify a package source.
> > Error: /Stage[main]/Bash/Package[shells/bash]/ensure: change from
> 'absent' to 'present' failed: Mac OS X PKG DMGs must specify a package
> source.
> > Notice: Applied catalog in 0.02 seconds
> > kris.bosland@kris:puppet %
> >
> > Note that Puppet complains about the class 'smash' in the 'bash' module,
> but not the class 'bash'.
>
> I would expect that too - not that I like it (it will still require a load
> of work to clean up our puppetserver.log), but in our end it complains even
> about 'bash'..
>
>
> > Can you provide a more detailed example that fails for you?
>
> I'm not sure how much more detail I can give? Most of our in-house modules
> are relatively simple, much like my original example. It complains about -
> it seems, but I haven't counted - every module we have written.
>
> One possible issue might be that we have several module directories - all
> listed in basemodulepath:
> /usr/local/etc/puppet/modules - anything installed using 'puppet
> module...'
> /usr/local/etc/puppet/modules.common - all in-house modules that apply to
> all our environments
> - This is where the bash module (and git, sudo, nano, vim, etcall
> suffering from the same) lives
> /usr/local/etc/puppet/nodes.common - all node classes and definitions that
> are the same across all our environments
>
> We're on FreeBSD and running unmodified puppetserver from the ports tree.
> Puppet server is v5.3.5
>
> Does this help? Any information I can collect that would shed light on
> this?
>
>
> Thanks,
> /Eirik
Hi X,
Nick Lewis helped me reproduce this issue with the extra module path, I
have filed https://tickets.puppetlabs.com/browse/PUP-9211 for the issue.
Thanks!
-Kris
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/b0173fab-d4e5-403d-b11e-99f7b3715c18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me
> Hi Eirik,
>
> I was unable to reproduce your issue in Puppet 5.5.6 (aka SHA 60de165 from
> https://github.com/puppetlabs/puppet/releases):
>
> kris.bosland@kris:puppet % git checkout 60de165
>
>±[5.5.6^0]
> HEAD is now at 60de165b86... Merge pull request #7007 from
> justinstoller/maint-pin-rake-more
> kris.bosland@kris:puppet % cat ../tmp/test/bash/manifests/init.pp
>
>±[5.5.6^0]
> class bash {
> package { "shells/bash":
> ensure => installed,
> }
> }
>
> class smash {
> package { "shells/bash":
> ensure => installed,
> }
> }
> kris.bosland@kris:puppet % bx puppet apply --modulepath ../tmp/test -e 'class
> test { include bash }; include test'
>±[5.5.6^0]
> Warning: Unacceptable location. The name 'smash' is unacceptable in file
> '/Users/kris.bosland/work/tmp/test/bash/manifests/init.pp' (file:
> /Users/kris.bosland/work/tmp/test/bash/manifests/init.pp, line: 7, column: 1)
> Notice: Compiled catalog for kris.bosland-c02kf9eafft1 in environment
> production in 0.56 seconds
> Error: Mac OS X PKG DMGs must specify a package source.
> Error: /Stage[main]/Bash/Package[shells/bash]/ensure: change from 'absent' to
> 'present' failed: Mac OS X PKG DMGs must specify a package source.
> Notice: Applied catalog in 0.02 seconds
> kris.bosland@kris:puppet %
>
> Note that Puppet complains about the class 'smash' in the 'bash' module, but
> not the class 'bash'.
I would expect that too - not that I like it (it will still require a load of
work to clean up our puppetserver.log), but in our end it complains even about
'bash'..
> Can you provide a more detailed example that fails for you?
I'm not sure how much more detail I can give? Most of our in-house modules are
relatively simple, much like my original example. It complains about - it
seems, but I haven't counted - every module we have written.
One possible issue might be that we have several module directories - all
listed in basemodulepath:
/usr/local/etc/puppet/modules - anything installed using 'puppet module...'
/usr/local/etc/puppet/modules.common - all in-house modules that apply to all
our environments
- This is where the bash module (and git, sudo, nano, vim, etcall
suffering from the same) lives
/usr/local/etc/puppet/nodes.common - all node classes and definitions that are
the same across all our environments
We're on FreeBSD and running unmodified puppetserver from the ports tree.
Puppet server is v5.3.5
Does this help? Any information I can collect that would shed light on this?
Thanks,
/Eirik
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/3A1D3608-9A23-44FE-A2B5-A3351266BFD2%40anduin.net.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me
On Friday, October 5, 2018 at 8:20:51 AM UTC-7, Eirik Øverby wrote:
>
> On Tuesday, August 28, 2018 at 6:50:48 PM UTC+3, Branan Purvine-Riley
> wrote:
>
>> Hi Jon,
>>
>> In Puppet 6 we're going to start requiring that the names of
>> classes/defines match the name that's implied by their file path[1]. We
>> added that deprecation warning in 5.5.6[2] as part of a push to get
>> upcoming Puppet 6 changes printing warnings whenever possible.
>>
>> [1] https://tickets.puppetlabs.com/browse/PUP-1434 and
>> https://tickets.puppetlabs.com/browse/PUP-4242
>> [2] https://tickets.puppetlabs.com/browse/PUP-8894
>>
>
> Since 5.5.6 our puppetserver has been issuing warnings of this kind:
> Puppet Unacceptable location. The name 'bash' is unacceptable in file
> '/usr/local/etc/puppet/modules.common/bash/manifests/init.pp'
>
> The init.pp file contains only this:
> class bash {
> package { "shells/bash":
> ensure => installed,
> }
> }
>
> I am at a loss as to how I'm supposed to refactor this to make the warning
> go away. We do need an init.pp, and I know that for style points we should
> split this into a base class and a ::install class, but I refuse to believe
> that this is *required* for something as simple as the above. I am also not
> finding the documentation particularly helpful in this simple use-case. It
> does look like it's complaining about absolutely every class we have
> defined, no matter if we use only init.pp or properly-defined
> directory/file hierarchy and -naming for the classes, defines, etc.
>
> Can someone help me nudge my neurons in a way that I understand what is
> expected of me?
>
> /Eirik
>
Hi Eirik,
I was unable to reproduce your issue in Puppet 5.5.6 (aka SHA 60de165
from https://github.com/puppetlabs/puppet/releases):
kris.bosland@kris:puppet % git checkout 60de165
±[5.5.6^0]
HEAD is now at 60de165b86... Merge pull request #7007 from
justinstoller/maint-pin-rake-more
kris.bosland@kris:puppet % cat ../tmp/test/bash/manifests/init.pp
±[5.5.6^0]
class bash {
package { "shells/bash":
ensure => installed,
}
}
class smash {
package { "shells/bash":
ensure => installed,
}
}
kris.bosland@kris:puppet % bx puppet apply --modulepath ../tmp/test -e
'class test { include bash }; include test'
±[5.5.6^0]
Warning: Unacceptable location. The name 'smash' is unacceptable in file
'/Users/kris.bosland/work/tmp/test/bash/manifests/init.pp' (file:
/Users/kris.bosland/work/tmp/test/bash/manifests/init.pp, line: 7, column:
1)
Notice: Compiled catalog for kris.bosland-c02kf9eafft1 in environment
production in 0.56 seconds
Error: Mac OS X PKG DMGs must specify a package source.
Error: /Stage[main]/Bash/Package[shells/bash]/ensure: change from 'absent'
to 'present' failed: Mac OS X PKG DMGs must specify a package source.
Notice: Applied catalog in 0.02 seconds
kris.bosland@kris:puppet %
Note that Puppet complains about the class 'smash' in the 'bash' module,
but not the class 'bash'.
Can you provide a more detailed example that fails for you?
Thanks.
-Kris
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/843a35f0-4c1b-47fc-936c-708afedde507%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me
On Friday, October 5, 2018 at 8:20:51 AM UTC-7, Eirik Øverby wrote:
>
> On Tuesday, August 28, 2018 at 6:50:48 PM UTC+3, Branan Purvine-Riley
> wrote:
>
>> Hi Jon,
>>
>> In Puppet 6 we're going to start requiring that the names of
>> classes/defines match the name that's implied by their file path[1]. We
>> added that deprecation warning in 5.5.6[2] as part of a push to get
>> upcoming Puppet 6 changes printing warnings whenever possible.
>>
>> [1] https://tickets.puppetlabs.com/browse/PUP-1434 and
>> https://tickets.puppetlabs.com/browse/PUP-4242
>> [2] https://tickets.puppetlabs.com/browse/PUP-8894
>>
>
> Since 5.5.6 our puppetserver has been issuing warnings of this kind:
> Puppet Unacceptable location. The name 'bash' is unacceptable in file
> '/usr/local/etc/puppet/modules.common/bash/manifests/init.pp'
>
> The init.pp file contains only this:
> class bash {
> package { "shells/bash":
> ensure => installed,
> }
> }
>
> I am at a loss as to how I'm supposed to refactor this to make the warning
> go away. We do need an init.pp, and I know that for style points we should
> split this into a base class and a ::install class, but I refuse to believe
> that this is *required* for something as simple as the above. I am also not
> finding the documentation particularly helpful in this simple use-case. It
> does look like it's complaining about absolutely every class we have
> defined, no matter if we use only init.pp or properly-defined
> directory/file hierarchy and -naming for the classes, defines, etc.
>
> Can someone help me nudge my neurons in a way that I understand what is
> expected of me?
>
> /Eirik
>
Hi Eirik,
I have tried, but was unable to reproduce the issue you have described here
in Puppet 5.5.6 (SHA 60de165
from https://github.com/puppetlabs/puppet/releases):
kris.bosland@kris:puppet % git checkout 60de165
±[6.0.0^0]
Previous HEAD position was 06ad255754... Merge pull request #7097 from
Magisus/device-fix
HEAD is now at 60de165b86... Merge pull request #7007 from
justinstoller/maint-pin-rake-more
kris.bosland@kris:puppet % cat ../tmp/test/bash/manifests/init.pp
±[5.5.6^0]
class bash {
package { "shells/bash":
ensure => installed,
}
}
kris.bosland@kris:puppet % bx puppet apply --modulepath ../tmp/test -e
'class test { include bash }'
±[5.5.6^0]
Notice: Compiled catalog for kris.bosland-c02kf9eafft1 in environment
production in 0.01 seconds
Notice: Applied catalog in 0.01 seconds
kris.bosland@kris:puppet %
Can you provide a more detailed example that fails for you?
Thanks.
-Kris
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/542e3b3b-20dc-4154-b8e5-945a3189ba4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: REGRESSION - Re: [Puppet Users] Announcement: Release of Puppet Platform 6.0.1
Thanks for reporting this duritong - I wanted to follow up to say that this was fixed in 6.0.2 (indeed this was the reason we shipped 6.0.2 after 1 day:) ) On Wednesday, October 3, 2018 at 1:30:22 AM UTC-7, Peter Meier wrote: > > Hi All, > > > We're happy to announce the release of Puppet Platform 6.0.1. This is > > primarily a bug release, with some improvements to Puppet, some new > > features in Puppet Server, and some new component versions in Puppet > > Agent. > > Just a heads up to everybody: There is a pretty severe regression in the > exec provider together with cwd, as the behavior of the type/provider > changed from 6.0.0 to 6.0.1: > > https://tickets.puppetlabs.com/browse/PUP-9194 > > tldr; The cwd param is not respected in 6.0.1 for the commands specified > in unless or onlyif. This might trigger an unwanted execution of the > command, as the safe-guards in unless/onlyif might fail as they are not > anymore executed in the cwd. > > best > > ~pete > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7f2df5c4-d5b7-4931-8899-68c0ca8b3dcd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Set default param value based on another param
I'd like to set default values for parameters that will be passed to epp
templates. However, the default value is based on another parameter. I
understand that variables are immutable but this is a parameter that
shouldn't be touched unless it wasn't set.
Here is an example construct with a few of my syntax attempts.
class myClass (
String $base_dir,
Optional[String] $conf_dir,
) {
#Attempt 1: Failed
if $myClass::conf_dir == undef { $myClass::conf_dir = "$myClass::base_dir
/conf" }
#Attempt 2: Failed
if !$myClass::conf_dir { $myClass::conf_dir = "$myClass::base_dir/conf" }
#Attempt 3: Failed
unless $myClass::conf_dir { $myClass::conf_dir = "$myClass::base_dir/conf" }
}
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/8e2db8c1-7353-4360-adc5-00713e1c0214%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me
On Tuesday, August 28, 2018 at 6:50:48 PM UTC+3, Branan Purvine-Riley wrote:
> Hi Jon,
>
> In Puppet 6 we're going to start requiring that the names of
> classes/defines match the name that's implied by their file path[1]. We
> added that deprecation warning in 5.5.6[2] as part of a push to get
> upcoming Puppet 6 changes printing warnings whenever possible.
>
> [1] https://tickets.puppetlabs.com/browse/PUP-1434 and
> https://tickets.puppetlabs.com/browse/PUP-4242
> [2] https://tickets.puppetlabs.com/browse/PUP-8894
>
Since 5.5.6 our puppetserver has been issuing warnings of this kind:
Puppet Unacceptable location. The name 'bash' is unacceptable in file
'/usr/local/etc/puppet/modules.common/bash/manifests/init.pp'
The init.pp file contains only this:
class bash {
package { "shells/bash":
ensure => installed,
}
}
I am at a loss as to how I'm supposed to refactor this to make the warning
go away. We do need an init.pp, and I know that for style points we should
split this into a base class and a ::install class, but I refuse to believe
that this is *required* for something as simple as the above. I am also not
finding the documentation particularly helpful in this simple use-case. It
does look like it's complaining about absolutely every class we have
defined, no matter if we use only init.pp or properly-defined
directory/file hierarchy and -naming for the classes, defines, etc.
Can someone help me nudge my neurons in a way that I understand what is
expected of me?
/Eirik
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/1a76f507-f1a6-4115-be51-1c504fd84ed4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
