Jira (PUP-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: John Duarte Assignee: Maggie Dreyer John Duarte 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-3566) Commands which don't pass schema check are never cleaned up
Title: Message Title Russell Mull commented on PDB-3566 Re: Commands which don't pass schema check are never cleaned up This is a very low risk fix; we should merge it up. 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-3558) Update puppetdb-termini 5 package to dep on puppet-agent >= 5
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3558 Update puppetdb-termini 5 package to dep on puppet-agent >= 5 Change By: Kenn Hussey Flagged: Impediment 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-3566) Commands which don't pass schema check are never cleaned up
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3566 Commands which don't pass schema check are never cleaned up Change By: Kenn Hussey Flagged: Impediment 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: Geoff Nichols Sub-team: 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: Kenn Hussey Flagged: Impediment 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-2398) PuppetDB should enable emergency deletion of historical data
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-2398
PuppetDB should enable emergency deletion of historical data
Change By:
Nick Walker
When a disk fills up on a database server, it is useful to have an option for reducing the disk space used without deleting data used by catalog compilation or requiring an increase in disk space. Disk increases can be infeasible or may require a long change cycle during which the Puppet infrastructure is inoperative.h2. Historical ContextIn PuppetDB 2.x disk usage could be reduced in an emergency by truncating the reports table, which is often the largest table in the database by several orders of magnitude. This would return large amounts of space to the operating system, enabling further maintenance operations, while keeping exported resources intact for catalog compilation:{noformat}# PE 3.8.x# sudo -u pe-postgres /opt/puppet/bin/psql -d pe-puppetdbcould not change directory to "/root"psql (9.2.14)Type "help" for help.pe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 5(1 row)pe-puppetdb=# TRUNCATE TABLE reports CASCADE;NOTICE: truncate cascades to table "resource_events"NOTICE: truncate cascades to table "latest_reports"TRUNCATE TABLEpe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 5(1 row){noformat}In 2015.3.x, the TRUNCATE operation now cascades beyond the tables related to reporting and wipes out exported resources, which negatively impacts catalog compilation:{noformat}# PE 2015.x# sudo -u pe-postgres /opt/puppetlabs/server/bin/psql -d pe-puppetdbcould not change directory to "/root": Permission deniedpsql (9.4.5)Type "help" for help.pe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 6(1 row)pe-puppetdb=# TRUNCATE TABLE reports CASCADE;NOTICE: truncate cascades to table "certnames"NOTICE: truncate cascades to table "resource_events"NOTICE: truncate cascades to table "factsets"NOTICE: truncate cascades to table "catalogs"NOTICE: truncate cascades to table "facts"NOTICE: truncate cascades to table "catalog_resources"TRUNCATE TABLEpe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 0(1 row){noformat}h2. Desired FunctionalityPuppetDB should allow for emergency removal of historical data without impacting catalog compilation or requiring changes to disk space allocation. h1. Workaround / Proposed Implementation {code}# cat /tmp/emergency_delete.sqlBEGIN TRANSACTION;ALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT "certnames_reports_id_fkey" FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;COMMIT TRANSACTION;{code}{code}# su - pe-postgres -s /bin/bash -c "/opt/puppetlabs/server/bin/psql -d pe-puppetdb -f /tmp/emergency_delete.sql"BEGINALTER TABLEUPDATE 1psql:/tmp/emergency_delete.sql:7: NOTICE: truncate cascades to table "resource_events"TRUNCATE TABLEALTER TABLECOMMIT{code}
Jira (PUP-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title John Duarte assigned an issue to Maggie Dreyer Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: John Duarte Assignee: John Duarte Maggie Dreyer 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-4345) Port PUP-3388 "Issue Creating Multiple Mirrors in Zpool Resource" to PUP 3.8
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-4345 Port PUP-3388 "Issue Creating Multiple Mirrors in Zpool Resource" to PUP 3.8 Change By: Jorie Tappa Release Notes: Bug Fix Not Needed 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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Jorie Tappa updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Jorie Tappa
Labels:
regression resolved-issue-added
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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title John Duarte commented on PUP-2280 Re: If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Using the --detailed-exitcodes options allows an expected exit (4 or 6) to be successfully returned which meets the expectation. So, for the previously sites reproduction steps, using the --detailed-exitcodes flag produces the following. [root@wk3atoozb8ir582 ~]# puppet apply pup-2280.pp --detailed-exitcodes Notice: Compiled catalog for wk3atoozb8ir582.delivery.puppetlabs.net in environment production in 0.07 seconds Notice: /Stage[main]/Main/Exec[/bin/true]/returns: executed successfully Error: /Stage[main]/Main/Exec[/bin/false]: Failed to call refresh: '/bin/false' returned 1 instead of one of [0] Error: /Stage[main]/Main/Exec[/bin/false]: '/bin/false' returned 1 instead of one of [0] Notice: /Stage[main]/Main/Exec[require_echo]: Dependency Exec[/bin/false] has failures: false Warning: /Stage[main]/Main/Exec[require_echo]: Skipping because of failed dependencies Notice: Applied catalog in 0.03 seconds
Jira (PUP-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: John Duarte Assignee: qa John Duarte 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: John Duarte Status: Ready for Engineering Test Assignee: Maggie Dreyer qa 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Maggie Dreyer commented on PUP-2280 Re: If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure After talking to Josh Cooper about this, we determined that we do not want the the run to exit 1, but rather to flag as "failed" in the report. I too found it unclear what the acceptance criteria in this ticket were describing, and we decided that setting the report status to "failed" if there was a resource that had failed to restart was more reasonable than exiting 1. I'll update the acceptance criteria to be more clear. 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: Maggie Dreyer Acceptance Criteria: If a resource is triggered by a refresh, and it fails, puppet treats it will flag the run as a failure failed in the report . 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title
John Duarte commented on PUP-2280
Re: If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Using puppet-agent at SHA de8df4913 containing puppet at SHA 3e66932, the acceptance criteria for this issue are not met.
The reproduction step outlined by Charlie Sharpsteen in the comment above was used. The resource with the failed dependency is successfully noted as skipped, but the failed resource still results in a passing exit code from the run.
[root@wk3atoozb8ir582 ~]# cat /opt/puppetlabs/puppet/VERSION
4.99.0.301.gde8df49
[root@wk3atoozb8ir582 ~]# cat pup-2280.pp
exec{'/bin/true':}
exec{'/bin/false':
refreshonly => true,
subscribe => Exec['/bin/true'],
Jira (PUP-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title John Duarte assigned an issue to Maggie Dreyer Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: John Duarte Assignee: John Duarte Maggie Dreyer 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-5755) Replace win32-eventlog calls with internal API implementations that are wide-string compatible
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5755 Replace win32-eventlog calls with internal API implementations that are wide-string compatible Change By: Geoff Nichols Release Notes Summary: Closed as duplicate of PUP-5756. 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-5755) Replace win32-eventlog calls with internal API implementations that are wide-string compatible
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5755 Replace win32-eventlog calls with internal API implementations that are wide-string compatible Change By: Geoff Nichols Release Notes: Not Needed 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-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7677 Create a feature flag setting for puppet 6 features during puppet 5 lifetime Change By: Moses Mendoza Issue Type: Bug New Feature 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-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime
Title: Message Title Moses Mendoza commented on PUP-7677 Re: Create a feature flag setting for puppet 6 features during puppet 5 lifetime cc Geoff Nichols Josh Cooper 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-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7677 Create a feature flag setting for puppet 6 features during puppet 5 lifetime Change By: Moses Mendoza Comment: Oops - didn't mean to add this to the current sprint 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-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7677 Create a feature flag setting for puppet 6 features during puppet 5 lifetime Change By: Moses Mendoza Sprint: Agent Grooming 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-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime
Title: Message Title Moses Mendoza commented on PUP-7677 Re: Create a feature flag setting for puppet 6 features during puppet 5 lifetime Oops - didn't mean to add this to the current sprint 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-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7677 Create a feature flag setting for puppet 6 features during puppet 5 lifetime Issue Type: Bug Assignee: Unassigned Created: 2017/06/19 3:27 PM Fix Versions: PUP 5.1.0 Priority: Normal Reporter: Moses Mendoza We will need a mechanism to ship dark changes during the puppet 5 series that are targeted to go live / on by default in puppet 6 In Scope Create a puppet setting that can be used to determine whether a user wants to opt into possible future behavior of puppet (including breaking changes) Suggest name `--future-features` with boolean possible values: true, false (default to false) Notes This flag doesn't have to be constrained to the puppet 5 => 6 transition. We could consider just retaining it to generally mean "major features or changes anticipated for the next major version of puppet" Docs should note that code enabled
Jira (PUP-7321) Update API schema docs
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-7321 Update API schema docs Change By: Moses Mendoza Assignee: Moses Mendoza 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-7662) SPIKE - investigate agent/master/puppetdb HTTP coms optimizations
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7662 SPIKE - investigate agent/master/puppetdb HTTP coms optimizations Change By: Moses Mendoza Sprint: Agent Grooming : Pay it down! 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Thomas Hallgren commented on PUP-7657 Re: Providers requiring files in other modules might cause intermittent compilation failures I agree that it doesn't make much sense to load the providers during compile. That's why we provide the puppet generate types solution. With PUP-7674 in place, the generated types should prevent all ruby types and providers from being loaded during compile. We can of course investigate if the load of providers could be prevented in general in the compile phase, but I think that would be a non-trivial given that we don't know if that compile then will be followed by an apply (on the same master). Should that happen, then the type must be reloaded, this time with providers. Some additional housekeeping of states would be needed in order to make that work seamlessly. I think it's unlikely that we will investigate that further since the consensus is that loading ruby code during compile is a bad idea in general. The solution is to use generated types. 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-3566) Messages which don't pass schema check are never cleaned up
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3566 Messages which don't pass schema check are never cleaned up Change By: Russell Mull Fix Version/s: PDB 5.0.0 Fix Version/s: PDB 4.4.2 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-3566) Messages which don't pass schema check are never cleaned up
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3566 Messages which don't pass schema check are never cleaned up Change By: Russell Mull Affects Version/s: PDB 4.4.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 (PDB-3566) Commands which don't pass schema check are never cleaned up
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3566 Commands which don't pass schema check are never cleaned up Change By: Russell Mull Summary: Messages Commands which don't pass schema check are never cleaned up 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-3566) Messages which don't pass schema check are never cleaned up
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3566 Messages which don't pass schema check are never cleaned up Issue Type: Bug Assignee: Unassigned Created: 2017/06/19 1:36 PM Priority: Normal Reporter: Russell Mull 1. Send a report to PuppetDB with a resource event which has a 'null' status 2. Look at the stockpile directory It should have seen the failure and put the message in the discard dir, but instead it just sits there forever. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3566) Messages which don't pass schema check are never cleaned up
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3566 Messages which don't pass schema check are never cleaned up Change By: Russell Mull Sprint: Hopper 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-3566) Messages which don't pass schema check are never cleaned up
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3566 Messages which don't pass schema check are never cleaned up Change By: Russell Mull Affects Version/s: PDB 4.4.0 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Nacho Barrientos commented on PUP-7657 Re: Providers requiring files in other modules might cause intermittent compilation failures I looked into it, and I don't think it's that bad actually. What happens is that when the type is created, it loads all providers for that type. So although it's a "load all", it's not a "load all types". Yes, correct. This behaviour is mentioned here. Once a type is needed it's read from disk. After that, the next step in newtype() is to loadall() all the providers available for it (example – second formatted block). If the provider does not work in the master (for instance, missing dependencies) the type loading error is cached (the action, not the error itself) and the compilation aborts (unable to load provider...). The next compilation by the same thread succeeds if the failure in loading the provider is not critical for the type definition to be used to validate what's in the catalog. That's exactly what's happening with the specific example on this ticket, the Nova_network type. 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Thomas Hallgren commented on PUP-7657 Re: Providers requiring files in other modules might cause intermittent compilation failures I looked into it, and I don't think it's that bad actually. What happens is that when the type is created, it loads all providers for that type. So although it's a "load all", it's not a "load all types". The reason all providers for a type is loaded is that it's needed to establish which one of them that is the default for the given platform. That could perhaps be optimized, especially for 'package' which has a large number of providers. Not sure how though, since the file name doesn't seem to follow any specific convention. 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: John Duarte Assignee: qa John Duarte 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7657 Providers requiring files in other modules might cause intermittent compilation failures Change By: Kenn Hussey Team: Agent 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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Kenn Hussey updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Kenn Hussey
Flagged:
Impediment
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Jorie Tappa updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Jorie Tappa
Release Notes Summary:
Puppet 4.10.3 contained a regression where resources created using the syntax {{Resource \ [xx::yy]}} would cause an error as Puppet would not find an existing 'xx::yy' user defined resource type. This was caused by fixing another problem with inconsistent use of upper/lower case in references.
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-7674) Resource collectors fails to load generated resource types.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7674 Resource collectors fails to load generated resource types. Change By: Henrik Lindberg Priority: Normal Major 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-7110) Unable to halt Puppet service on Solaris using Puppet
Title: Message Title Michael Smith updated an issue Puppet / PUP-7110 Unable to halt Puppet service on Solaris using Puppet Change By: Michael Smith Release Notes Summary: A Puppet resource is now able to halt the Puppet service without terminating an agent run started by that service. Release Notes: Bug Fix 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-7575) Add CLI flag to pass job-id to puppet agent
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-7575
Add CLI flag to pass job-id to puppet agent
Change By:
Michael Smith
Release Notes Summary:
Puppet now accepts an arbitrary string as a Job identifier via {{--job-id}} that is used in catalog requests and reports.
Release Notes:
New Feature
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-7674) Resource collectors fails to load generated resource types.
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7674 Resource collectors fails to load generated resource types. Change By: Kenn Hussey Flagged: Impediment 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-7674) Resource collectors fails to load generated resource types.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7674 Resource collectors fails to load generated resource types. Change By: Henrik Lindberg Fix Version/s: PUP 5.0.0 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-7674) Resource collectors fails to load generated resource types.
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7674 Resource collectors fails to load generated resource types. Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Maggie Dreyer commented on PUP-2280 Re: If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure I got it. 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: Maggie Dreyer Release Notes Summary: Puppet will now report runs as failed when an exec resource fails to refresh. In the past, failures to restart would not flag the run as failed. Release Notes: Bug Fix 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-3558) Update puppetdb-termini 5 package to dep on puppet-agent >= 5
Title: Message Title Kenn Hussey commented on PDB-3558 Re: Update puppetdb-termini 5 package to dep on puppet-agent >= 5 Russell Mull please provide release notes for this issue, if applicable. 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-3732) type validation should not run for `puppet resource`
Title: Message Title Hunter (Hunner) Haugen commented on PUP-3732 Re: type validation should not run for `puppet resource` Josh Cooper I see occurrences of this at least in the F5, netapp, and Azure modules, if you want code examples. Otherwise specific scenarios may not help as it's a "gotcha" any time I'm coding any global validate block (and especially having to make "required" parameters since there is no way to make required parameters for puppet types otherwise). Eg: validate do raise ArgumentError, "Passing value or othervalue is required" if ! self[:value] and ! self[:othervalue] end 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
Jira (PUP-7674) Resource collectors fails to load generated resource types.
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7674
Resource collectors fails to load generated resource types.
Change By:
Henrik Lindberg
Release Notes Summary:
A problem was found with the environment isolation solution ({{generate types}} where a collection of a type would cause it to be loaded as a Ruby implementation instead of the generated meta data. This in turn could cause isolation problems if different environments had different versions of this type.This is now fixed so collectors also load the generated meta data form if present.
Release Notes:
Bug Fix
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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Kenn Hussey commented on PUP-2280 Re: If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Henrik Lindberg please provide release notes for this issue, if applicable. 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-7382) Ensure current values are YAML serializable
Title: Message Title Maggie Dreyer commented on PUP-7382 Re: Ensure current values are YAML serializable Deferring to Josh Cooper 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-7575) Add CLI flag to pass job-id to puppet agent
Title: Message Title Kenn Hussey commented on PUP-7575 Re: Add CLI flag to pass job-id to puppet agent Nick Lewis please provide release notes for this issue, if applicable. 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-7110) Unable to halt Puppet service on Solaris using Puppet
Title: Message Title Kenn Hussey commented on PUP-7110 Re: Unable to halt Puppet service on Solaris using Puppet Michael Smith please provide release notes for this issue, if applicable. 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Henrik Lindberg commented on PUP-7657 Re: Providers requiring files in other modules might cause intermittent compilation failures We need to look into the calling of "load all types" - that is bad in any case. 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-7382) Ensure current values are YAML serializable
Title: Message Title Kenn Hussey commented on PUP-7382 Re: Ensure current values are YAML serializable Maggie Dreyer please provide release notes for this issue, if applicable. 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-7073) Comparisons between SELinux file categories should always translate to the numeric version
Title: Message Title Kenn Hussey commented on PUP-7073 Re: Comparisons between SELinux file categories should always translate to the numeric version Branan Riley please provide release notes for this issue, if applicable. 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7657 Providers requiring files in other modules might cause intermittent compilation failures Change By: Henrik Lindberg Priority: Major Normal 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7657 Providers requiring files in other modules might cause intermittent compilation failures Change By: Henrik Lindberg Priority: Normal Major 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-7675) Add the ability to typecast a key using lookup_options
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-7675 Add the ability to typecast a key using lookup_options Issue Type: New Feature Assignee: Unassigned Created: 2017/06/19 10:40 AM Priority: Normal Reporter: Henrik Lindberg With the addition of the Init[T, arg, ...] data type it is possible to formalize and describe type casting of values. This can be added to lookup_options to enable type casting. This is of value as there is no way to represent certain data types directly in JSON, YAML, etc. By adding the key data_type to lookup options, and setting either the desired type directly (for example Sensitive), or by setting it to an Init[T, arg,...arg] enables type casts of the looked up data to be performed by lookup before the value is returned. If a simple data type is used (for example Sensitive) it is expected that this type has a single argument constructor that accepts the looked up value and returns an instance of the specified data type. If the constructor is more complex and needs additional arguments, or where its single argument constructor is not appropriate for the use case, an Init[T, args...] is instead used. (An example could be interpretation of a String in a particular format used to construct a time/date value). The data_type entry in lookup_options is a String with a valid Puppet Type System specification of a data type.
Jira (PUP-7674) Resource collectors fails to load generated resource types.
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7674 Resource collectors fails to load generated resource types. Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-7277) Add Init[T] type to type system
Title: Message Title Henrik Lindberg commented on PUP-7277 Re: Add Init[T] type to type system There may be some types where the constructor has an overloaded variant that returns a transformed version of the input. So an Init[T, arg] will not match a T unless there is constructor signature of [T,arg] (i.e. cannot automatically be taken as just the given instance of T). 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-7277) Add Init[T] type to type system
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7277 Add Init[T] type to type system Change By: Henrik Lindberg Fix Version/s: PUP 5.1.0 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-5893) Add the tree iterative function tree_each
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5893
Add the tree iterative function tree_each
Change By:
Henrik Lindberg
UPDATE-A simpler solution was implemented. The function {{tree_each}} which is configurable to iterate over Array, Hash and Object data types (the type of container can be selected), yielding elements that represents a "flattened tree". This enables other existing iterable functions to be used to map, filter, reduce (etc.) the result.At the end, a tree can again be constructed by creating a new Hash using {{Hash(, 'tree')}}. For details see the documentation in the {{new}} function, and in the documentation for {{tree_each}}.The Original ticket text is retained below (mostly for its motivation why the function is wanted).ORIGINAL-BackgroundAt the moment it is difficult to flatten out a complex structure. There is a flatten in standard lib that creates a flat copy of a tree of {{Array}} objects, and it errors if given a Hash. If the restriction was lifted to also support Hash, Ruby flatten method flattens a hash by making an array of keys and values. That makes the result hard to use if it is a mix of arrays and hashes.It is very useful to be able to iterate over such a tree instead of creating a copy, and it is of value to iterate over it in different ways. This is what the flat_each does.To describe what is wanted; imagine the two functions {{each_element}}, and {{each_container}} (these are not the functions we want at the end; they are too special, but they serve as illustration).{{each_element(Iterable $x)}}This function visits each container and leaf in the tree $x and calls a given block with 1.3 parameters. The block gets container, index, and value if defining three parameters, if using 2 arguments the container and index is delivered as a tuple, and if using 1 arg the three args are delivered as a Triple. The first yielded value is the given argument value. Each element in the tree is yielded with parent before children, depth first.When not given a block, each_element produces an Iterator that yields a triplet.{{each_container(Iterable $x)}}This function is he same as to each_element but skips children that are not containers. This enables doing inner loops conditionally.What we should do instead is to first implement {{next()}} since that makes it possible to do general skipping and pruning; {{next(true)}} means skip this element and its children and {{next()}}, or {{next(false)}} to mean "do not prune", take next element I am done with the one you just gave me. ProposalImplement flat_each such that:* It accepts an Iterable and a required block* It produces an Iterator if not given a block* When given a block, it produces the given first argument* It yields 1-3 arguments as described for each_element* The value produced by the block is ignored (as for a regular each)* If next is called, the value given to next determines if iteration continues with the next in order {{next(false)}}/{{next()}}, or if it prunes {{next(true)}}.Implement flat_reduce such that:* It accepts an Any and a required block* if value is not Iterable, the given value is yielded and nothing more, else every value in the iterable is yielded to the block* It produces an Iterator if not given a block* When given a
Jira (PUP-5893) Add the tree iterative function tree_each
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5893 Add the tree iterative function tree_each Change By: Henrik Lindberg 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-5893) Add the tree iterative function tree_each
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5893
Add the tree iterative function tree_each
Change By:
Henrik Lindberg
Release Notes Summary:
The functions function {{ tree_each , and tree_reduce have }} has been added to allow convenient iteration , filtering, mapping, and reduction over complex structures. The function iterates recursively in a way that flattens a structure into a sequence, but that retains information about the structure thus making it possible to put it back together with possibly altered values. This was a difficult operation to do in Puppet Language earlier and required a user to write a custom recursive function to achieve the same result.
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-5893) Add the tree iterative function tree_each
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5893 Add the tree iterative function tree_each Change By: Henrik Lindberg Fix Version/s: PUP 5.1.0 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-5893) Add the tree iterative function tree_each
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5893
Add the tree iterative function tree_each
Change By:
Henrik Lindberg
UPDATE-A simpler solution was implemented. The function {{tree_each}} which is configurable to iterate over Array, Hash and Object data types (the type of container can be selected), yielding elements that represents a "flattened tree". This enables other existing iterable functions to be used to map, filter, reduce (etc.) the result.At the end, a tree can again be constructed by creating a new Hash using {{Hash(, 'tree')}}. For details see the documentation in the {{new}} function, and in the documentation for {{tree_each}}.The Original ticket text is retained below (mostly for its motivation why the function is wanted).ORIGINAL- BackgroundAt the moment it is difficult to flatten out a complex structure. There is a flatten in standard lib that creates a flat copy of a tree of {{Array}} objects, and it errors if given a Hash. If the restriction was lifted to also support Hash, Ruby flatten method flattens a hash by making an array of keys and values. That makes the result hard to use if it is a mix of arrays and hashes.It is very useful to be able to iterate over such a tree instead of creating a copy, and it is of value to iterate over it in different ways. This is what the flat_each does.To describe what is wanted; imagine the two functions {{each_element}}, and {{each_container}} (these are not the functions we want at the end; they are too special, but they serve as illustration).{{each_element(Iterable $x)}}This function visits each container and leaf in the tree $x and calls a given block with 1.3 parameters. The block gets container, index, and value if defining three parameters, if using 2 arguments the container and index is delivered as a tuple, and if using 1 arg the three args are delivered as a Triple. The first yielded value is the given argument value. Each element in the tree is yielded with parent before children, depth first.When not given a block, each_element produces an Iterator that yields a triplet.{{each_container(Iterable $x)}}This function is he same as to each_element but skips children that are not containers. This enables doing inner loops conditionally.What we should do instead is to first implement {{next()}} since that makes it possible to do general skipping and pruning; {{next(true)}} means skip this element and its children and {{next()}}, or {{next(false)}} to mean "do not prune", take next element I am done with the one you just gave me.ProposalImplement flat_each such that:* It accepts an Iterable and a required block* It produces an Iterator if not given a block* When given a block, it produces the given first argument* It yields 1-3 arguments as described for each_element* The value produced by the block is ignored (as for a regular each)* If next is called, the value given to next determines if iteration continues with the next in order {{next(false)}}/{{next()}}, or if it prunes {{next(true)}}.Implement flat_reduce such that:* It accepts an Any and a required block* if value is not Iterable, the given value is yielded and nothing more, else every value in the iterable is yielded to the block* It produces an Iterator if not given a block* When given a
Jira (PUP-7674) Resource collectors fails to load generated resource types.
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7674 Resource collectors fails to load generated resource types. Change By: Henrik Lindberg Assignee: Henrik Lindberg 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 (PDOC-45) Strings crashes when documenting puppet's defined.rb
Title: Message Title Jorie Tappa updated an issue Puppet Strings / PDOC-45 Strings crashes when documenting puppet's defined.rb Change By: Jorie Tappa Release Notes: Bug Fix Not Needed 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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
John Duarte commented on PUP-7671
Re: Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
This has passed CI for puppet-agent 4.10.4 (8a1be18)
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Kenn Hussey updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Kenn Hussey
Flagged:
Impediment
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Kenn Hussey updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Kenn Hussey
Flagged:
Impediment
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Kenn Hussey assigned an issue to qa
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Kenn Hussey
Status:
Ready for CI Test
Assignee:
Moses Mendoza qa
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-6242) Semantic::VersionRange does not interpret tilde ranges according to spec.
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6242 Semantic::VersionRange does not interpret tilde ranges according to spec. Change By: Thomas Hallgren Release Notes Summary: The parser for version ranges did not handle tilde ranges correctly. Instead of increasing #minor and resetting #patch to zero in the upper bound, it increased #patch. This is now fixed. The parser is now also capable of handling caret versions. A caret version shares the semantics of a tilde version for versions with #major of 0. For other versions, it sets the upper bound to the next #major, and resets #minor and #patch to zero. Release Notes: Bug Fix 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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
can be covered by unit tests. validation would be good as this regressed.
Change By:
Eric Delaney
QA Risk Assessment Reason:
can be covered by unit tests. qa to confirm. validation would be good as Thomas requested an acceptance test for this regressed
QA Risk Assessment:
Manual Automate
QA Contact:
Eric Delaney
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
Jira (PUP-6368) Semantic::VersionRange creates incorrect range for <= version
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6368 Semantic::VersionRange creates incorrect range for <= version Change By: Thomas Hallgren Release Notes Summary: When converting version ranges back to their string representation, the string would often be different and sometimes even invalid. This is now fixed so that the original string representation is retained. Release Notes: Bug Fix 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-6264) Semantic::VersionRange considers '1.0.0-alpha' part of range '>=1.0.0'
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6264 Semantic::VersionRange considers '1.0.0-alpha' part of range '>=1.0.0' Change By: Thomas Hallgren Release Notes: Bug Fix 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-6264) Semantic::VersionRange considers '1.0.0-alpha' part of range '>=1.0.0'
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6264 Semantic::VersionRange considers '1.0.0-alpha' part of range '>=1.0.0' Change By: Thomas Hallgren Release Notes Summary: A version range declared as ">=x.y.z" would incorrectly include pre-releases of version x.y.z. That is now corrected so that pre-releases are always considered to be semantically less than the actual release. 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-7674) Resource collectors fails to load generated resource types.
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7674 Resource collectors fails to load generated resource types. Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-7658) Puppet 4.10.2 fails when Facter facts contains ampersand
Title: Message Title John Duarte updated an issue Puppet / PUP-7658 Puppet 4.10.2 fails when Facter facts contains ampersand Change By: John Duarte QA Risk Assessment: Needs Assessment No Action 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Thomas Hallgren commented on PUP-7657 Re: Providers requiring files in other modules might cause intermittent compilation failures I created ticket PUP-7674 to track progress for the collectors problem. The problem described here should be able to circumvent using puppet generate types so this ticket is in some sense blocked by that ticket, even if it's not the same problem. 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-7665) Puppet 5 fails when facter facts contain ampersands
Title: Message Title John Duarte updated an issue Puppet / PUP-7665 Puppet 5 fails when facter facts contain ampersands Change By: John Duarte QA Risk Assessment: Needs Assessment Automate 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-7674) Resource collectors fails to load generated resource types.
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7674 Resource collectors fails to load generated resource types. Issue Type: Bug Assignee: Thomas Hallgren Created: 2017/06/19 7:40 AM Fix Versions: PUP 4.10.5 Priority: Normal Reporter: Thomas Hallgren A resource collector will always load the ruby resource, even if resources has been generated using puppet generate types. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7664) "Function lookup() did not find a value for the name 'classes' on node"
Title: Message Title John Duarte updated an issue Puppet / PUP-7664 "Function lookup() did not find a value for the name 'classes' on node" Change By: John Duarte QA Risk Assessment: Needs Assessment No Action 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-3564) Create stubbed graphql endpoint for PDB
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3564 Create stubbed graphql endpoint for PDB Change By: Russell Mull Summary: Create stubbed graphql endpoint for PDB 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-5893) Add the tree iterative function tree_each
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5893 Add the tree iterative function tree_each Change By: Henrik Lindberg Summary: Add the tree iterative functions - function tree_each , and tree_reduce 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7657 Providers requiring files in other modules might cause intermittent compilation failures Change By: Thomas Hallgren Fix Version/s: PUP 4.10.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 (PUP-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7657 Providers requiring files in other modules might cause intermittent compilation failures Change By: Thomas Hallgren Assignee: Nacho Barrientos 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Thomas Hallgren commented on PUP-7657 Re: Providers requiring files in other modules might cause intermittent compilation failures Thanks Nacho Barrientos. That was very helpful. One bug related to generated types is indeed squashed but that revealed another. The problem here seems to be an oversight in the collector where the check for the generated type is missing. The good news is that this should be easy to fix. 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-4951) "puppet module build" too picky about SemVer
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4951 "puppet module build" too picky about SemVer Change By: Henrik Lindberg Fix Version/s: PUP 5.0.0 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-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Nacho Barrientos commented on PUP-7657 Re: Providers requiring files in other modules might cause intermittent compilation failures Thomas Hallgren, there you go: [qtp1249723194-67] [puppetserver] Puppet CERN - autoloader: load_file (trying to load): /var/lib/puppet/environments/inc1382019/modules/nova/lib/puppet/type/nova_network.rb inc1382019 [qtp1249723194-67] [puppetserver] Puppet CERN - load_file: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/autoload.rb:209:in `load' [qtp1249723194-67] [puppetserver] Puppet CERN - load_file: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/metatype/manager.rb:173:in `type' [qtp1249723194-67] [puppetserver] Puppet CERN - load_file: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource.rb:389:in `resource_type' [qtp1249723194-67] [puppetserver] Puppet CERN - load_file: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource.rb:377:in `resource_type' [qtp1249723194-67] [puppetserver] Puppet CERN - load_file: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource.rb:318:in `initialize' [qtp1249723194-67] [puppetserver] Puppet CERN - load_file: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/evaluator/collectors/catalog_collector.rb:13:in `initialize' [qtp1249723194-67] [puppetserver] Puppet CERN - load_file:
Jira (PUP-7665) Puppet 5 fails when facter facts contain ampersands
Title: Message Title Ethan Brown commented on PUP-7665 Re: Puppet 5 fails when facter facts contain ampersands Merged to master in https://github.com/puppetlabs/puppet/commit/c71fc233c81a2645ff32e3c8b16ad1ab41c8bb97 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-3732) type validation should not run for `puppet resource`
Title: Message Title Bernhard Frauendienst commented on PUP-3732 Re: type validation should not run for `puppet resource` Taylan Develioglu, it turns out that checking for managed? does not help (at least not in all cases), because even for managed resources the above situation occurs, where the resource is created but validation is called before properties are set. However, the resources is already marked as managed. 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-3732) type validation should not run for `puppet resource`
Title: Message Title Bernhard Frauendienst commented on PUP-3732 Re: type validation should not run for `puppet resource` Taylan Develioglu thanks, that's good to know! However, in my case, even for unmanaged resources that validated invariant always holds true, so guarding for managed resources would just be working around implementation details. 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-3732) type validation should not run for `puppet resource`
Title: Message Title Taylan Develioglu commented on PUP-3732 Re: type validation should not run for `puppet resource` Just wanted to chime that you can guard against this behavior by checking if the resource is managed. e.g.: validate do if managed? unless self[:value] raise ArgumentError, 'Active_value must be set' end end end Add Comment
Jira (PUP-3732) type validation should not run for `puppet resource`
Title: Message Title Bernhard Frauendienst commented on PUP-3732 Re: type validation should not run for `puppet resource` This should still work for normal catalog application, as a resource returned by self.instances and thus passing global validation is already configured correctly. Are you sure about this? I've encountered the same issue with resources created by self.instances when trying to purge them with resources. I tried to follow the code, the resources are created in self.instances @ type.rb#L1174 with just a name and a provider, and are then validated in initialize @ type.rb#L2398. I can't see where the values from the provider would be set inbetween, and given that the validation fails, this does not seem to be the case. Then again, I'm very new to the Ruby language. Am I missing something here? I've checked most built-in types, and none of them have a global validate block that would not work if the values are not set. That would explain why this never was reported with a built-in type. 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.
