Jira (FACT-1571) Add "is_virtual" fact for AIX
Title: Message Title
Scott Pruzinsky commented on FACT-1571
Re: Add "is_virtual" fact for AIX
Scenarios:
For AIX running on bare-metal (non-LPAR), is_virtual should return "false". This is where the following OS commands return a value of "1":
lparstat -i | grep 'Partition Number' | awk '{print $4}'
For AIX running in an LPAR (virtualized partition running on top of IBM’s VIOS hypervisor), is_virtual should return "true". This is where the same command above returns a value > 1.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7221) puppet type schedule: weekday parameters: integers not allowed
Title: Message Title otheus created an issue Puppet / PUP-7221 puppet type schedule: weekday parameters: integers not allowed Issue Type: Bug Affects Versions: PUP 4.9.2, PUP 3.8.0 Assignee: Nicholas Fagerlund Components: DOCS, Types and Providers Created: 2017/02/15 5:09 PM Priority: Normal Reporter: otheus See https://github.com/puppetlabs/puppet/blame/master/lib/puppet/type/schedule.rb#L373 Documentation says numbers may be used for day-of-week, but code clearly expects strings. Add Comment
Jira (PUP-4736) add tempfile_suffix attribute to file type
Title: Message Title Stefan Bethke commented on PUP-4736 Re: add tempfile_suffix attribute to file type See also https://github.com/saz/puppet-sudo/issues/124 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7220) Concatenating an optional array results in 'undef'
Title: Message Title
Thomas Hallgren commented on PUP-7220
Re: Concatenating an optional array results in 'undef'
I don't think this is a bug. Using '+' on an array will either concatenate two arrays or add an value to an array. undef is a value in this context. So what you get in $members is the array after add is:
['one', 'two', 'three', undef]
Then, when the array is used as a title, it results in multiple notify resources where the last one has an undef title.
Instead of using undef as the default, try using an empty array. That way, you can also remove the Optional and the size constraint (must accept empty array), i.e.
class arrayjank (
Array[String] $extra_members = []
) {
$base_members = ['one','two','three']
$members = $base_members + $extra_members
notify { $members: }
}
Jira (PUP-7220) Concatenating an optional array results in 'undef'
Title: Message Title
Nick Miller created an issue
Puppet / PUP-7220
Concatenating an optional array results in 'undef'
Issue Type:
Bug
Affects Versions:
PUP 4.9.2
Assignee:
Unassigned
Components:
DSL
Created:
2017/02/15 9:04 AM
Priority:
Normal
Reporter:
Nick Miller
See the example class below:
class arrayjank (
Optional[Array[String,1]] $extra_members = undef
) {
Jira (PUP-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7215 Problem with puppet-agent 1.9.x and hiera eyaml backend Change By: Thomas Hallgren Affects Version/s: PUP 4.9.2 Story Points: 1 Team: Puppet Developer Experience Sprint: PDE 2017-02-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7215 Problem with puppet-agent 1.9.x and hiera eyaml backend Change By: Thomas Hallgren Fix Version/s: PUP 4.9.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7215 Problem with puppet-agent 1.9.x and hiera eyaml backend Change By: Thomas Hallgren Assignee: Angel L. Mateo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend
Title: Message Title Thomas Hallgren commented on PUP-7215 Re: Problem with puppet-agent 1.9.x and hiera eyaml backend The fix for this ticket is in the PR for PUP-7216. Although not strictly the same issue, the fix touched exactly the same code so it was not meaningful to provide separate commits. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend
Title: Message Title Thomas Hallgren commented on PUP-7215 Re: Problem with puppet-agent 1.9.x and hiera eyaml backend Thanks Angel L. Mateo, this really helps. The bug is caused by a bug in the Hiera::Backend::Backen1xWrapper. It is triggered because the Eyaml backend uses the deprecated Hiera 1.x backend API. I will have a fix for this shortly. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Thomas Hallgren commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master I tried recreating an environment with the sample files that is provided here but I'm not able to reproduce the problem. I assumed that the yaml file under node should look something like this: --- some_module : name_a : uri: foo shortname: x name_b : uri: bar shortname: y There's nothing in the example that is exposed to `deeper` merge strategy. Perhaps that's needed in order to reproduce?
Jira (PUP-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend
Title: Message Title Angel L. Mateo updated an issue Puppet / PUP-7215 Problem with puppet-agent 1.9.x and hiera eyaml backend I have added puppetserver.log which is the server log with trace enabled and puppet_lookup.trace which is the result of puppet lookup with --explain and -trace options. Change By: Angel L. Mateo Attachment: puppet_lookup.trace Attachment: puppetserver.log Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend
Title: Message Title Thomas Hallgren commented on PUP-7215 Re: Problem with puppet-agent 1.9.x and hiera eyaml backend An easier alternative would perhaps be to use the lookup with --trace and --explain sudo puppet lookup --explain --trace --node mus30.um.es role cluster=mus hostgroup=mus --environment production Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend
Title: Message Title Thomas Hallgren commented on PUP-7215 Re: Problem with puppet-agent 1.9.x and hiera eyaml backend Angel L. Mateo, the log from the agent doesn't contain much of value. Would it be possible for you to produce a log from the server with loglevel 'trace'? The loglevel is normally set in /etc/puppetlabs/puppetserver/logback.xml. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7169) puppet 4.9.0 breaks hiera-eyaml
Title: Message Title
Thomas Hallgren commented on PUP-7169
Re: puppet 4.9.0 breaks hiera-eyaml
The hiera_include function is also affected by PUP-7216. A workaround until that bug-fix is available is to replace it with lookup so that: If a merge_strategy is defined in hiera.yaml, then use:
include(lookup($key))
or, remove the merge_strategy from hiera.yaml and instead use:
include(lookup($key, { 'merge' => 'deep' }))
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to
Jira (PUP-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Andreas Papst commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Hey, as you can see from node.yaml: hiera_hash is used implicitly. And deeper merge is defined in hiera.conf: :merge_behavior: deeper :deep_merge_options: :knock_out_prefix: '--' :sort_merge_arrays: true :merge_hash_arrays: true I guess too that hiera is the prime suspect. Maybe deeper merge is broken even when there is no second hash to merge. Cheers Andreas Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7169) puppet 4.9.0 breaks hiera-eyaml
Title: Message Title Angel L. Mateo commented on PUP-7169 Re: puppet 4.9.0 breaks hiera-eyaml Yes, in some places. The problem with puppet agent runs is in a hiera_include call. It is also failing in a puppet lookup run. I have reported the problem in PUP-7215. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Thomas Hallgren commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Andreas Papst, if you're using the hiera_hash function, then it's not unlikely that this is the same problem as PUP-7216. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7169) puppet 4.9.0 breaks hiera-eyaml
Title: Message Title Thomas Hallgren commented on PUP-7169 Re: puppet 4.9.0 breaks hiera-eyaml Angel L. Mateo, it is not unlikely that the problem you are seeing is the same problem that is described in PUP-7216. Are you using the hiera_hash function? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7216) hiera_hash doesn't use deeper merge
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7216 hiera_hash doesn't use deeper merge Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7216) hiera_hash doesn't use deeper merge
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7216 hiera_hash doesn't use deeper merge Change By: Thomas Hallgren Story Points: 1 Team: Puppet Developer Experience Sprint: PDE Triage 2017-02-22 Fix Version/s: PUP 4.9.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7216) hiera_hash doesn't use deeper merge
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7216 hiera_hash doesn't use deeper merge Change By: Thomas Hallgren Component/s: Puppet Server Component/s: Language Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7216) hiera_hash doesn't use deeper merge
Title: Message Title Thomas Hallgren commented on PUP-7216 Re: hiera_hash doesn't use deeper merge I can reproduce the problem using the attached files and confirm that this is a regression in Puppet 4.9.x. The regression is limited to the hiera_xxx calls. Christopher Siedler, a workaround while waiting for a bug-fix on this is to use the lookup function instead of hiera_hash. Just replacing the function name works in example that you provided. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7216) hiera_hash doesn't use deeper merge
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7216 hiera_hash doesn't use deeper merge Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7216) hiera_hash doesn't use deeper merge
Title: Message Title Christopher Siedler updated an issue Puppet / PUP-7216 hiera_hash doesn't use deeper merge Change By: Christopher Siedler Environment: Ubuntu 10 14 .04 LTS on all Servers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7216) hiera_hash doesn't use deeper merge
Title: Message Title Christopher Siedler commented on PUP-7216 Re: hiera_hash doesn't use deeper merge Hello, yes I did restart the server several times since the upgrade. In the mean time I did restore the puppetserver from an backup (it's an VM) . In this backup there was puppet-agent 1.8.3-1trusty installed and everything worked fine. Then I made a snapshot, upgraded puppet-agent to 1.9.1-1trusty and had the desicribed problems again. So it's definitly an issue of the puppet-agent package on the puppet server. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
