Jira (PDB-3843) Error: /Stage[main]/Postgresql::Server::Config/Concat[/var/lib/pgsql/9.6/data/pg_hba.conf]/Concat_file[/var/lib/pgsql/9.6/data/pg_hba.conf]: Failed to generate additional resources usi
Title: Message Title Ken Barber commented on PDB-3843 Re: Error: /Stage[main]/Postgresql::Server::Config/Concat[/var/lib/pgsql/9.6/data/pg_hba.conf]/Concat_file[/var/lib/pgsql/9.6/data/pg_hba.conf]: Failed to generate additional resources using 'eval_generate': comparison of Array with Array failed harish could you please provide: The full code for how you applied the puppetdb module, what instructions did you follow, and can you show me the code snippet for how you applied it? What is the full error, if you try puppet agent -t --trace when running the agent it should show a full stack trace Thanks. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet
Jira (PDB-3193) Fix beaker bug around duplicate keys
Title: Message Title Ken Barber updated an issue PuppetDB / PDB-3193 Fix beaker bug around duplicate keys Change By: Ken Barber Story Points: 5 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 (PDB-3193) Fix beaker bug around duplicate keys
Title: Message Title Ken Barber updated an issue PuppetDB / PDB-3193 Fix beaker bug around duplicate keys Change By: Ken Barber Sprint: NG 2016-11-30, NG 2016-12-14, NG 2017-01-11 , NG 2017-01-25 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 (PDB-3193) Fix beaker bug around duplicate keys
Title: Message Title Ken Barber commented on PDB-3193 Re: Fix beaker bug around duplicate keys Raised PR here: https://github.com/puppetlabs/beaker/pull/1307 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 (PDB-3193) Fix beaker bug around duplicate keys
Title: Message Title Ken Barber updated an issue PuppetDB / PDB-3193 Fix beaker bug around duplicate keys Change By: Ken Barber Sprint: NG 2016-11-30, NG 2016-12-14, NG 2017-01- 25 11 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 (PDB-3204) Change /aws/instances endpoint to return a list of instances
Title: Message Title Ken Barber created an issue PuppetDB / PDB-3204 Change /aws/instances endpoint to return a list of instances Issue Type: Task Assignee: Unassigned Created: 2016/11/28 10:01 AM Priority: Normal Reporter: Ken Barber As discussed with the eng team, John wants a list of instances to show some results after foraging without having to tap the database. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3204) Change /aws/instances endpoint to return a list of instances
Title: Message Title Ken Barber assigned an issue to Ken Barber PuppetDB / PDB-3204 Change /aws/instances endpoint to return a list of instances Change By: Ken Barber Assignee: Ken Barber 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 (PDB-3193) Fix beaker bug around duplicate keys
Title: Message Title Ken Barber updated an issue PuppetDB / PDB-3193 Fix beaker bug around duplicate keys Change By: Ken Barber Story Points: 3 5 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 (PDB-3193) Fix beaker bug around duplicate keys
Title: Message Title Ken Barber assigned an issue to Ken Barber PuppetDB / PDB-3193 Fix beaker bug around duplicate keys Change By: Ken Barber Assignee: Ken Barber 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 (PDB-3193) Fix beaker bug around duplicate keys
Title: Message Title Ken Barber created an issue PuppetDB / PDB-3193 Fix beaker bug around duplicate keys Issue Type: Bug Affects Versions: PDB 3.2.5 Assignee: Unassigned Created: 2016/11/16 5:18 PM Fix Versions: PDB 3.2.5 Labels: maintenance Priority: Normal Reporter: Ken Barber Our acceptance tests are throwing errors due to duplicate keys during the aws_sdk setup steps. I've done some work to get us running the latest beaker, so now we can develop a fix for this transient bug. It seems to be appear quite a lot lately, and its something we can control and fix.
Jira (PDB-3155) (maint) Update beaker to 3.2.x, unpin from 2.30.1
Title: Message Title Ken Barber assigned an issue to Ken Barber PuppetDB / PDB-3155 (maint) Update beaker to 3.2.x, unpin from 2.30.1 Change By: Ken Barber Assignee: Ken Barber 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 (PDB-3155) (maint) Update beaker to 3.2.x, unpin from 2.30.1
Title: Message Title Ken Barber updated an issue PuppetDB / PDB-3155 (maint) Update beaker to 3.2.x, unpin from 2.30.1 Change By: Ken Barber Labels: maintenance Story Points: 1 5 Team: Next Generation Sprint: NG 2016-11-16 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 (PDB-3155) (maint) Update beaker to 3.2.x, unpin from 2.30.1
Title: Message Title Ken Barber updated an issue PuppetDB / PDB-3155 (maint) Update beaker to 3.2.x, unpin from 2.30.1 Change By: Ken Barber Fix Version/s: PDB 3.2.5 Issue Type: Bug Task 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 (PDB-3110) Add postgres_datadir to params
Title: Message Title Ken Barber updated an issue PuppetDB / PDB-3110 Add postgres_datadir to params Change By: Ken Barber Team: Next Generation Sprint: NG 2016-11-16 Issue Type: Bug Improvement 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 (PDB-3035) PDB should use gzip when replicating data
Title: Message Title Ken Barber commented on PDB-3035 Re: PDB should use gzip when replicating data Brett Gray well spotted mate . Last time I looked, we had the server support (spent a bit of time around this for the puppet master->puppetdb integration). This would just be the client most probably in clojure, not having the correct params or something simple. Brett dude, did you want to break out your replication issue perhaps into a different ticket so we can debate outside of this gzip issue? Feels like this gzip thing is trivial and really more like a bug/misconfig, and that replication issue is a medium. Probably best not to conflate? Also, the HA guys might want to consider the problem on their own. 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-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Ken Barber commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type We have a patch up here: https://github.com/puppetlabs/puppet/pull/5220 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Ken Barber commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type Kenn Hussey understood, we have some partial fixes in already, there is a final patch/approach we are debating still that might not make it, we're just not sure if its a good idea to rush it yet. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Ken Barber commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type Okay, working with Branan Riley he pointed out a comment from Michal Ruzicka on PCP-542 about stripping YAML tags before parsing. I implemented this here (excuse the code, its mainly just for show at the moment): https://github.com/puppetlabs/puppet/pull/5214/files#diff-a5348c3071a6b3d7b77bf0ed94147edfR12 Actually seems to work, rather we have no more parsing errors with acl at all now. Still figuring out if this is the right approach of course, but the stripping technique does seem solid on its own. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title
Ken Barber updated an issue
Puppet / PUP-6629
Corrective Change YAML file causes errors when type parameter is a complex type
Change By:
Ken Barber
https://jenkins-modules.puppetlabs.com/view/3.%20windows%20only/view/acl/view/acl%20-%20master/job/forge-windows_puppetlabs-acl_intn-sys_smoke-master/PLATFORM=windows-2008r2-64a,WORKER_LABEL=beaker/20/consoleFull{code}file { 'c:/tmp': ensure => directory,}user { 'bob': ensure => present, groups => 'Users', managehome => true, password => "L0v3Pupp3t!"}acl { 'c:/tmp': permissions => [{ identity => 'bob', perm_type => 'allow', rights => ['modify'] }, ],}{code}The permissions property of acl is a hash type. This looks to be killing runs for anyone using acl or another type that has a parameter/property that is a hash type.The contents of the transactionstore.yaml are as so:{code}---resources: File[c:/temp]:parameters: ensure:system_value: :directory File[c:/temp/deny_full_rights_dir]:parameters: ensure:system_value: :directory User[bob]:parameters: ensure:system_value: :present password:system_value: L0v3Pupp3t! groups:system_value: BUILTIN\Users,Users Acl[c:/temp/deny_full_rights_dir]:parameters: permissions: system_value:- !ruby/hash:Puppet::Type::Acl::Ace { } inherit_parent_permissions:system_value: :true{ code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title
Ken Barber updated an issue
Puppet / PUP-6629
Corrective Change YAML file causes errors when type parameter is a complex type
Change By:
Ken Barber
https://jenkins-modules.puppetlabs.com/view/3.%20windows%20only/view/acl/view/acl%20-%20master/job/forge-windows_puppetlabs-acl_intn-sys_smoke-master/PLATFORM=windows-2008r2-64a,WORKER_LABEL=beaker/20/consoleFull{code}file { 'c:/tmp': ensure => directory,}user { 'bob': ensure => present, groups => 'Users', managehome => true, password => "L0v3Pupp3t!"}acl { 'c:/tmp': permissions => [{ identity => 'bob', perm_type => 'allow', rights => ['modify'] }, ],}{code}The permissions property of acl is a hash type. This looks to be killing runs for anyone using acl or another type that has a parameter/property that is a hash type.The contents of the transactionstore.yaml are as so:{code} {code} ---resources: File[c:/temp]:parameters: ensure:system_value: :directory File[c:/temp/deny_full_rights_dir]:parameters: ensure:system_value: :directory User[bob]:parameters: ensure:system_value: :present password:system_value: L0v3Pupp3t! groups:system_value: BUILTIN\Users,Users Acl[c:/temp/deny_full_rights_dir]:parameters: permissions:{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title
Ken Barber updated an issue
Puppet / PUP-6629
Corrective Change YAML file causes errors when type parameter is a complex type
Change By:
Ken Barber
https://jenkins-modules.puppetlabs.com/view/3.%20windows%20only/view/acl/view/acl%20-%20master/job/forge-windows_puppetlabs-acl_intn-sys_smoke-master/PLATFORM=windows-2008r2-64a,WORKER_LABEL=beaker/20/consoleFull{code}file { 'c:/tmp': ensure => directory,}user { 'bob': ensure => present, groups => 'Users', managehome => true, password => "L0v3Pupp3t!"}acl { 'c:/tmp': permissions => [{ identity => 'bob', perm_type => 'allow', rights => ['modify'] }, ],}{code}The permissions property of acl is a hash type. This looks to be killing runs for anyone using acl or another type that has a parameter/property that is a hash type. The contents of the transactionstore.yaml are as so:{code}{code}---resources: File[c:/temp]:parameters: ensure:system_value: :directory File[c:/temp/deny_full_rights_dir]:parameters: ensure:system_value: :directory User[bob]:parameters: ensure:system_value: :present password:system_value: L0v3Pupp3t! groups:system_value: BUILTIN\Users,Users Acl[c:/temp/deny_full_rights_dir]:parameters: permissions:{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Ken Barber commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type So, I think the class Ace.rb just won't deserialize in its current form, I also believe this will show up in ORCH-1285 when you sort out the type loading problem too (at least it looks like a library path problem, but it also might be that the code isn't on the box where you run puppet job ...). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6630) Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows
Title: Message Title Ken Barber commented on PUP-6630 Re: Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows This looks like a duplicate of PUP-6629. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Ken Barber commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type This doesn't solve the issue per se, but it will at least avoid the case where the YAML corrupts and puppet can't continue: https://github.com/puppetlabs/puppet/pull/5214. This puts us in line with the approach to make corrective_change soft fail in the wild as much as possible. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PDB-2962) (maint) Missing implicit inventory relationships
Title: Message Title Ken Barber updated an issue PuppetDB / PDB-2962 (maint) Missing implicit inventory relationships Change By: Ken Barber Affects Version/s: PDB 4.2.0 Fix Version/s: PDB 4.2.1 Fix Version/s: PDB 4.3.0 Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PDB-2962) (maint) Missing implicit inventory relationships
Title: Message Title
Ken Barber updated an issue
PuppetDB / PDB-2962
(maint) Missing implicit inventory relationships
Change By:
Ken Barber
(maint) Missing implicit inventory relationshipsThis adds relationships from environment and node entities to inventory tobehave in a similar way to factsets. This allows implicit subqueries to work.Without this patch you cannot do queries of this nature:{ { code} nodes { inventory { facts.operatingsystem = "CentOS" } } {code } } Instead you are forced to use explicit querying:{ { code} nodes { certname in inventory[certname] { facts.operatingsystem = "CentOS" } } {code } } Which is a lot more verbose and should be unnecessary.Signed-off-by: Ken Barber
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 (PDB-2962) (maint) Missing implicit inventory relationships
Title: Message Title
Ken Barber updated an issue
PuppetDB / PDB-2962
(maint) Missing implicit inventory relationships
Change By:
Ken Barber
Affects Version/s:
PDB 4.2.0
Fix Version/s:
PDB 4.2.1
(maint) Missing implicit inventory relationships This adds relationships from environment and node entities to inventory , tobehave in a similar way to factsets. This allows implicit subqueries to work. Without this patch you cannot do queries of this nature:nodes { inventory { facts.operatingsystem = "CentOS" } }Instead you are forced to use explicit querying:nodes { certname in inventory[certname] { facts.operatingsystem = "CentOS" } }Which is a lot more verbose and should be unnecessary. Signed-off-by: Ken Barber
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (PDB-2962) (maint) Missing implicit inventory relationships
Title: Message Title
Ken Barber updated an issue
PuppetDB / PDB-2962
(maint) Missing implicit inventory relationships
Change By:
Ken Barber
(maint) Missing implicit inventory relationshipsThis adds relationships from environment and node entities to inventory tobehave in a similar way to factsets. This allows implicit subqueries to work.Without this patch you cannot do queries of this nature: {{ nodes { inventory { facts.operatingsystem = "CentOS" } } }} Instead you are forced to use explicit querying: {{ nodes { certname in inventory[certname] { facts.operatingsystem = "CentOS" } } }} Which is a lot more verbose and should be unnecessary.Signed-off-by: Ken Barber
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 (PDB-2228) Create "examples repo" and tie that into PDB CLI manpage creation
Title: Message Title Ken Barber commented on PDB-2228 Re: Create "examples repo" and tie that into PDB CLI manpage creation This is kind of related to the stuff I'm doing for ORCH-1491. At least, its a place for example. Implementation-wise though, we're looking at a simple docs update, but the examples can totally be re-used. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6295) Include corrective_change field in reports
Title: Message Title Ken Barber updated an issue Puppet / PUP-6295 Include corrective_change field in reports Change By: Ken Barber Release Notes Summary: This release adds a new report event field called ‘corrective_change’ that is designed to detect manual change that has been corrected by a Puppet run.This feature should help users be able to detect when an unexpected change occurred outside of Puppet, allowing better auditing and understanding around changes.This feature achieves this by storing the last best known value for each property that is applied by Puppet, and comparing that against the values in the next Puppet run.As part of the requirement is to store values, this feature also introduces a new local storage mechanism, and introduces a new configuration option ‘transactionstorefile’ which points at the YAML file used. This storage is queried for each run for old values during comparison, and persists the new values for next transaction to do its calculation.While we’ve done our best to ensure this feature works well, this entire process is still in development and is quite new, and has some known points of interest:* For noop events in particular, these a treated especially. We will continue to return a positive ‘corrective_change’ flag if there will be a corrective_change, if Puppet was to be ran in enforcement mode.* Today, idempotency issues are raised as ‘corrective_change’ because we can’t tell the difference. An idempotency issue is when either a provider has a bug applying a change twice consistently, or when Puppet DSL code (or external dependences) is used that has idempotency issues (common in service, and exec resources for example). For those properties that have known idempotency issues, we have introduced an ‘idempotent’ flag for declaring that corrective_change calculation can be skipped. An example can be found in the notify provider, as the message property on notify has been a long-standing and well known non-idempotent property: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/notify.rb#L9* The API for comparison in Puppet for older arbitrary values is brittle, and some custom Puppet types may show the incorrect thing for corrective_change as a consequence. We ask users to raise bugs when these cases are discovered.* For now, if there is any exception during value comparison we will still continue to run Puppet, but return an error to the user so it can be debugged. Also, we return a ‘corrective_change’ as nil instead, indicating an unknown state. Any cases where this occurs should be raised as bugs to the appropriate project.* Comparison of secret values is currently out of scope. For us to ensure we could compare these values, we would have to store them in doing so leak secret information. We’ve decided we would step back from this problem, and for now secret properties are not supported for being flagged as corrective.Along with flagging each event with the ‘corrective_change’ field, we also flag a resource that has such events, and the entire report. Metrics have been included to allow report consumers to see a count of events that are marked as ‘corrective_change’ also.
