Jira (PUP-1983) contain causes edges with nil targets to be added to the catalog
Title: Message Title
Daniele Sluijters commented on an issue
Re: contain causes edges with nil targets to be added to the catalog
In order to reproduce this bug:
class test {
notice('class test')
}
class profile::test {
notice('containing test')
contain test
}
include ::profile::test
Running puppet apply test.pp now results in:
Error: undefined method `ref' for nil:NilClass on node chell
Error: undefined method `ref' for nil:NilClass on node chell
Using Richard Clamp's suggested workaround results in a functional catalog:
class test {
notice('class test')
}
class profile::test {
notice('containing test')
include ::test
contain test
}
include ::profile::test
Running puppet apply test.pp now results in:
Notice: Scope(Class[Profile::Test]): containing test
Notice: Scope(Class[Test]): class test
Notice: Compiled catalog for chell.nedap.local in environment production in 0.02 seconds
Notice: Finished catalog run in 0.06 seconds
Add Comment
Puppet / PUP-1983
contain causes edges with nil targets to be added to the catalog
Jira (PUP-1983) contain causes edges with nil targets to be added to the catalog
Title: Message Title Daniele Sluijters updated an issue Puppet / PUP-1983 contain causes edges with nil targets to be added to the catalog Change By: Daniele Sluijters Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1983) contain causes edges with nil targets to be added to the catalog
Title: Message Title
Daniele Sluijters commented on an issue
Re: contain causes edges with nil targets to be added to the catalog
I've raised this bug to critical as this behaviour is both surprising, unintended and undocumented and results in broken catalogs.
Add Comment
Puppet / PUP-1983
contain causes edges with nil targets to be added to the catalog
With certain manifests, interestingly enough not all of them, using contain causes nil edges to be added to the catalog. {noformat} class profile::apt { contain apt contain apt::backports contain apt::unattended_upgrades } {noformat} This causes a nil edge to appear in the catalog from {{Class\[Apt\]}} to nothing. Using this pattern, wh...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-1983) contain causes edges with nil targets to be added to the catalog
Title: Message Title Daniele Sluijters updated an issue Puppet / PUP-1983 contain causes edges with nil targets to be added to the catalog Change By: Daniele Sluijters Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2014) Gem provider will match more than one gem, sorted alphabetically.
Title: Message Title
Ronald Valente updated an issue
Puppet / PUP-2014
Gem provider will match more than one gem, sorted alphabetically.
Change By:
Ronald Valente
*OldWay*Gemproviderwouldcontinuouslyupgradebundlerbecauseitwouldmatchon ` {{ 0.1.0 ` }} not ` {{ 1.5.3 ` }} .{{gemlist--remotebundler$}}REMOTEGEMSappbundler(0.1.0)asset_bundler(0.2.0)assetbundler(0.0.0)atd-asset_bundler(0.0.3)bowline-bundler(0.0.4)bundler(1.5.3)capistrano-bundler(1.1.2)capistrano-ext-rvm-bundler(0.0.2)ctags-bundler(0.0.1)gem_bundler(0.2)guard-bundler(2.0.0)guard-ctags-bundler(1.0.2)hello_world_bundler(0.1.2)hoe-bundler(1.2.0)jbundler(0.5.5)moneypools-bundler(0.8.1)motion-bundler(0.2.1)mpapis-bundler(1.0.21.1)ofxbundler(0.2.8)peritor-bundler(0.7.0)quick-bundler(0.0.3)rails-assets-bundler(0.0.1)rubygems-bundler(1.4.2)rubysl-bundler(2.0.0)smart_bundler(0.0.1)tvd-bundler(0.0.8)unbundler(0.0.2)vagrant-bundler(0.1.1)vagrant-plugin-bundler(0.1.1)vim-bundler(0.3.0)web_resource_bundler(0.0.23)widget_bundler(0.0.10)*ProposedNewWay*Returnsonlythespecificgem.{{gemlist--remote^bundler$}}REMOTEGEMSbundler(1.5.3)
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2014) Gem provider will match more than one gem, sorted alphabetically.
Title: Message Title
Ronald Valente updated an issue
Puppet / PUP-2014
Gem provider will match more than one gem, sorted alphabetically.
Change By:
Ronald Valente
# * OldWay * Gemproviderwouldcontinuouslyupgradebundlerbecauseitwouldmatchon`0.1.0`not`1.5.3`. ` {{ gemlist--remotebundler$ ` }} *** REMOTEGEMS *** appbundler(0.1.0)asset_bundler(0.2.0)assetbundler(0.0.0)atd-asset_bundler(0.0.3)bowline-bundler(0.0.4)bundler(1.5.3)capistrano-bundler(1.1.2)capistrano-ext-rvm-bundler(0.0.2)ctags-bundler(0.0.1)gem_bundler(0.2)guard-bundler(2.0.0)guard-ctags-bundler(1.0.2)hello_world_bundler(0.1.2)hoe-bundler(1.2.0)jbundler(0.5.5)moneypools-bundler(0.8.1)motion-bundler(0.2.1)mpapis-bundler(1.0.21.1)ofxbundler(0.2.8)peritor-bundler(0.7.0)quick-bundler(0.0.3)rails-assets-bundler(0.0.1)rubygems-bundler(1.4.2)rubysl-bundler(2.0.0)smart_bundler(0.0.1)tvd-bundler(0.0.8)unbundler(0.0.2)vagrant-bundler(0.1.1)vagrant-plugin-bundler(0.1.1)vim-bundler(0.3.0)web_resource_bundler(0.0.23)widget_bundler(0.0.10) # * ProposedNewWay * Returnsonlythespecificgem. ` {{ gemlist--remote^bundler$ ` }} *** REMOTEGEMS *** bundler(1.5.3)
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2014) Gem provider will match more than one gem, sorted alphabetically.
Title: Message Title Ronald Valente created an issue Puppet / PUP-2014 Gem provider will match more than one gem, sorted alphabetically. Issue Type: Bug Affects Versions: 3.4.3 Assignee: Kylo Ginsberg Components: Types and Providers Created: 20/Mar/14 4:58 AM Fix Versions: 3.5.0 RC Priority: Normal Reporter: Ronald Valente Original Estimate: 1 hour Remaining Estimate: 1 hour Old Way
Jira (PUP-2014) Make gem provider match on a single gem name
Title: Message Title Ronald Valente updated an issue Puppet / PUP-2014 Make gem provider match on a single gem name Change By: Ronald Valente Summary: Gem Makegem provider will match morethanone onasingle gem ,sortedalphabetically. name Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1183) Allow provider-specific options as a first class part of the RAL model.
Title: Message Title
Erik Daln updated an issue
Puppet / PUP-1183
Allow provider-specific options as a first class part of the RAL model.
Change By:
Erik Daln
http://groups.google.com/group/puppet-users/browse_thread/thread/2ef615fc42225d99?pli=1Ourrequirementismoreorlessthesameasinthelinkedthread,weneedtouseaproxytoinstallgemsbutforavarietyofreasonscan'tsetaglobalproxyonthemachines.Thussomewayofpassingoptionstogemisnecessary.(Nigel)-Weshoulddothisconsistentlyacrossproviders,perhapscombiningwiththepreseedfunctionalityofapt/dpkg.Ratherthandoingthisasagenericpassunstructureddatahack,weshouldresolvethisbyallowingprovider-specificparameterstobefirstclasselementsindeclarations: pre {code} package{example:provider=something,something_specific_parameter=value} /pre {code} Thatshouldcovermorethanjustpackages-extendingtoalltypes.Requiringtheprovidertobeexplicitlyspecifiedispreferabletoallowingittobeinferredwhennon-typeparametersorpropertiesarepresent.Itisunclearifbothpropertiesandparametersshouldbesupported,orifonlyparametersshouldbeallowed.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2002) Docs pushed
Title: Message Title Justin Holguin updated an issue Puppet / PUP-2002 Docs pushed Change By: Justin Holguin Assignee: JustinHolguin NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker created an issue Puppet / PUP-2015 Identify and fix test slowdowns on windows Issue Type: Task Affects Versions: 3.5.0 Assignee: Ethan Brown Components: Test Infrastructure Created: 20/Mar/14 10:27 AM Environment: Windows Priority: Normal Reporter: Andy Parker The merge of the master branch into the stable branch for the 3.5.0 release showed a significant jump in the time it took the spec tests to run in Jenkins (~9 minutes to ~20 minutes). There is also a noticeable upward trend in the runtime of the spec tests on the master branch.
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker updated an issue Puppet / PUP-2015 Identify and fix test slowdowns on windows Change By: Andy Parker Attachment: Puppet-Specs-Windows-stable.jpg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker updated an issue Puppet / PUP-2015 Identify and fix test slowdowns on windows Change By: Andy Parker Attachment: Puppet-Specs-stable.jpg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker updated an issue Puppet / PUP-2015 Identify and fix test slowdowns on windows Change By: Andy Parker Attachment: Puppet-Specs-master.jpg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title
Kenneth Barber commented on an issue
Re: ERROR: duplicate key value violates unique constraint catalogs_pkey
Den Mat what exact version of postgresql are you running? 8.4.13 I see, but what package? Also - what distribution are you on?
Have you checked the postgresql.log to see if there is anything relevant after the upgrade?
Add Comment
PuppetDB / PDB-510
ERROR: duplicate key value violates unique constraint catalogs_pkey
We receive these errors every few minutes. Our logs indicate that these error began to occurring once our puppetdb instance was upgraded from 1.5.2 - 1.6.2. {code} 2014-03-12 15:33:03,107 ERROR [command-proc-82] [puppetdb.command] [7b979257-dda8-4d46-b8b2-242b88611523] [replace catalog] Retrying after attempt 12, due to: org.postgresql.util.PSQLEx...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title
Kenneth Barber commented on an issue
Re: ERROR: duplicate key value violates unique constraint catalogs_pkey
Den Mat Tyler Parsons can you show me consecutive logs showing the full duration between the upgrade, and then the start of the errors? I want exact log lines here so I can get an idea of the timelines of this bug, but the hostnames might give away private information so you might want to obfuscate that. Let me know if you'd rather send it privately.
Add Comment
PuppetDB / PDB-510
ERROR: duplicate key value violates unique constraint catalogs_pkey
We receive these errors every few minutes. Our logs indicate that these error began to occurring once our puppetdb instance was upgraded from 1.5.2 - 1.6.2. {code} 2014-03-12 15:33:03,107 ERROR [command-proc-82] [puppetdb.command] [7b979257-dda8-4d46-b8b2-242b88611523] [replace catalog] Retrying after attempt 12, due to: org.postgresql.util.PSQLEx...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-1840) Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts
Title: Message Title Jared Jennings commented on an issue Re: Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts Joseph Yaworski Wait, what, the interpreter dumps core?! That should already have been fixed in ruby-1.8.7.352-3.el6, years ago. But I have ruby-1.8.7.352-13.el6, and sure enough, it dumps core. That has to be fixed (again?) for Puppet to be able to detect at startup that it can't use MD5. Add Comment Puppet / PUP-1840 Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts I'm using Puppet in part to ensure [Federal Information Processing Standard 140-2](http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf) (FIPS 140-2) compliance on my network. Part of this compliance for the system underlying Puppet is to make sure that only [FIPS Approved](http://csrc.nist.gov/publications/fips/fips140-2/fips1402annexa.pdf) algo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker updated an issue Puppet / PUP-2015 Identify and fix test slowdowns on windows Change By: Andy Parker Attachment: Puppet-Specs-Windows-master.jpg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-407) Facts hang on certain kernels when IO.read is called on /proc filesystem
Title: Message Title Zachary Stern created an issue Facter / FACT-407 Facts hang on certain kernels when IO.read is called on /proc filesystem Issue Type: Bug Assignee: Eric Sorenson Created: 20/Mar/14 11:06 AM Priority: Normal Reporter: Zachary Stern Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker updated an issue Puppet / PUP-2015 Identify and fix test slowdowns on windows Change By: Andy Parker Attachment: Puppet-Specs-Windows-masterWin2008r2.jpg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-407) Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem
Title: Message Title Zachary Stern updated an issue Facter / FACT-407 Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem Change By: Zachary Stern Summary: Facts Blockdevicefacts hangoncertainkernelswhenIO.readiscalledon/procfilesystem Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-407) Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem
Title: Message Title Zachary Stern updated an issue Facter / FACT-407 Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem Change By: Zachary Stern Labels: customersupport Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker updated an issue Puppet / PUP-2015 Identify and fix test slowdowns on windows Change By: Andy Parker Attachment: Puppet-Specs-Windows-masterWin2003r2.jpg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker updated an issue Puppet / PUP-2015 Identify and fix test slowdowns on windows Change By: Andy Parker Attachment: Puppet-Specs-Windows-stableWin2003r2.jpg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker updated an issue Puppet / PUP-2015 Identify and fix test slowdowns on windows Change By: Andy Parker Attachment: Puppet-Specs-Windows-stableWin2008r2.jpg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker commented on an issue Re: Identify and fix test slowdowns on windows I've attached a number of screenshots of the build times, as reported by Jenkins. The interesting things to note are that both windows and non-windows specs on stable (Puppet-Specs-stable.jpg and Puppet-Specs-Windows-stable.jpg) both show an increase at the time of the merge. The linux increase seems to be less dramatic, but it is still there. On the windows side, it is clear that both 2008 and 2003 saw a jump with the change to 3.5.0-rc1 (Puppet-Specs-Windows-stable Win2003r2.jpg and Puppet-Specs-Windows-stable Win2008r2.jpg), but 2003 was much more significant. The graphs for the master builds also show little or now upward trend in the win2008 builds, whereas the win2003 builds do show an upward trend. Add Comment Puppet / PUP-2015 Identify and fix test slowdowns on windows The merge of the master branch into the stable branch for the 3.5.0 release showed a significant jump in the time it took the spec tests to run in Jenkins (~9 minutes to ~20 minutes). There is also a noticeable upward trend in the runtime of the spec tests on the master branch. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Andy Parker commented on an issue Re: Identify and fix test slowdowns on windows I should also mention that the linux build time changes from the 3.5.0 merge could simply be due to migrating the build configuration from the master jobs to the stable jobs. The migration added several more cells to the build matrix and so would dramatically increase the number of tests run. I believe that ruby 2.1.0 was added to the matrix. Add Comment Puppet / PUP-2015 Identify and fix test slowdowns on windows The merge of the master branch into the stable branch for the 3.5.0 release showed a significant jump in the time it took the spec tests to run in Jenkins (~9 minutes to ~20 minutes). There is also a noticeable upward trend in the runtime of the spec tests on the master branch. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-1975) Environment transaction_uuid is not passed to facts indirector during compilation
Title: Message Title Andy Parker commented on an issue Re: Environment transaction_uuid is not passed to facts indirector during compilation Merged into stable in 2ed40f. This will go out in the next 3.5.0-rc Add Comment Puppet / PUP-1975 Environment transaction_uuid is not passed to facts indirector during compilation The class Puppet::Indirector::Catalog::Compiler contains a method 'extract_facts_from_request' which extracts facts from the request to be stored in a cache indirector. This call is used in the flow for the PuppetDB terminus to save facts. The problem however, is that the environment is not passed through to the indirector, which means we cannot pre... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1944) Error when manifest is a directory but not the same as manifestdir
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-1944 Error when manifest is a directory but not the same as manifestdir Change By: Andy Parker Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1955) purge_ssh_keys causes stack trace when creating new users on redhat
Title: Message Title Andy Parker updated an issue Puppet / PUP-1955 purge_ssh_keys causes stack trace when creating new users on redhat Change By: Andy Parker Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1796) File resource fails for root(/) directory.
Title: Message Title
Rodney Beede commented on an issue
Re: File resource fails for root(/) directory.
Temporary work-around:
file { '/./': }
Add Comment
Puppet / PUP-1796
File resource fails for root(/) directory.
I know this is probably an extreme edge case, but I recently noticed that this fails: {code} file { '/': ensure = directory } with the error: Parameter path failed: File paths must be fully qualified, not '' at /tmp/test.pp:1 {code} A little background, This comes from a larger module that I have which uses the lvm module to create additional...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1174) PR (2247) Ability to purge .ssh/authorized_keys
Title: Message Title Charlie Sharpsteen commented on an issue Re: PR (2247) Ability to purge .ssh/authorized_keys Current status: this ticket is blocked until PUP-1955 is resolved. Once that ticket clears CI, this can re-enter functional review. Add Comment Puppet / PUP-1174 PR (2247) Ability to purge .ssh/authorized_keys As I'm new to puppet i'll try to describe this as good as i can. I wanted to use the ssh_authorized_key type to add keys to ssh. After a discussion on irc i was suggested to use virtual resources and realize each key for each class needed. This worked well for me. However i am not able to purge all other keys from the authorized_keys file without ei... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-398) Smoke test packages
Title: Message Title Kylo Ginsberg assigned an issue to Adrien Thebo Facter / FACT-398 Smoke test packages Change By: Kylo Ginsberg Assignee: KyloGinsberg AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title
Kenneth Barber commented on an issue
Re: ERROR: duplicate key value violates unique constraint catalogs_pkey
This seems to be caused by the fact that we are copying id's and not incrementing the sequence as a result: https://github.com/puppetlabs/puppetdb/blob/1.6.x/src/com/puppetlabs/puppetdb/scf/migrate.clj#L624-L626
We're testing this theory, and if true we'll produce a fix for this.
Add Comment
PuppetDB / PDB-510
ERROR: duplicate key value violates unique constraint catalogs_pkey
We receive these errors every few minutes. Our logs indicate that these error began to occurring once our puppetdb instance was upgraded from 1.5.2 - 1.6.2. {code} 2014-03-12 15:33:03,107 ERROR [command-proc-82] [puppetdb.command] [7b979257-dda8-4d46-b8b2-242b88611523] [replace catalog] Retrying after attempt 12, due to: org.postgresql.util.PSQLEx...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-510 ERROR: duplicate key value violates unique constraint catalogs_pkey Change By: Kenneth Barber Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-514) Add optional type to parameters
Title: Message Title Daniele Sluijters commented on an issue Re: Add optional type to parameters I would very much like to see this added for 4.0. Andy Parker suggested the syntax would look something like this Type $var = value, which I'll +1. Add Comment Puppet / PUP-514 Add optional type to parameters It is of great value to be able to optionally type the parameters of defines and classes (as well as types). This is quite easy to implement as there now is a type system. The default type is Data. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-398) Smoke test packages
Title: Message Title Michelle Johansen updated an issue Facter / FACT-398 Smoke test packages Change By: Michelle Johansen Fix Version/s: 2.0.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-127) Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Title: Message Title
Chris Portman commented on an issue
Re: Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Hi Andy Parker,
In your last comment on PR #184 (https://github.com/puppetlabs/hiera/pull/184), are you saying that % {%} {Something literal}
already works?
Thanks, Chris
Add Comment
Hiera / HI-127
Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
I have some data that contains Apache variables (such as %{SERVER_NAME}, %{QUERY_STRING}, etc ) in a Hiera file (Yaml backend). However, when I retrieve the value, the string is replaced with empty value. For instance, for: myserver: http://%{SERVER_NAME} I got the value http// I found out that during the lookup in the YAML backend, the answ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 (FACT-398) Smoke test packages
Title: Message Title Michelle Johansen commented on an issue Re: Smoke test packages Adrien Thebo or Kylo Ginsberg Any update on this issue or blockers? It would be nice to get this out the door. Add Comment Facter / FACT-398 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-398) Smoke test packages
Title: Message Title Michelle Johansen updated an issue Facter / FACT-398 Smoke test packages Change By: Michelle Johansen Reporter: gepetto-bot RyanMcKern Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1840) Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts
Title: Message Title
Jared Jennings commented on an issue
Re: Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts
Joseph Yaworski, oho, the crash that was fixed in 2011 was when you do
ruby -ropenssl -e puts OpenSSL::Digest::MD5.new('hi').hexdigest
The crash I see now is when I do
ruby -rdigest -e puts Digest::MD5.new('hi').hexdigest
Filed vendor bug https://bugzilla.redhat.com/show_bug.cgi?id=1079042 and upstream bug https://bugs.ruby-lang.org/issues/9659.
Add Comment
Puppet / PUP-1840
Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts
I'm using Puppet in part to ensure [Federal Information Processing Standard 140-2](http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf) (FIPS 140-2) compliance on my network. Part of this compliance for the system underlying Puppet is to make sure that only [FIPS Approved](http://csrc.nist.gov/publications/fips/fips140-2/fips1402annexa.pdf) algo...
This message was sent by Atlassian JIRA
Jira (FACT-185) No EC2 facts shown on newly-built Amazon Linux host
Title: Message Title Adrien Thebo commented on an issue Re: No EC2 facts shown on newly-built Amazon Linux host It looks like this is fixed on the master branch: root@ip-172-16-128-22:/opt/facter# git checkout stable Switched to branch 'stable' root@ip-172-16-128-22:/opt/facter# ruby -Ilib bin/facter |grep ec2 root@ip-172-16-128-22:/opt/facter# git checkout master Switched to branch 'master' root@ip-172-16-128-22:/opt/facter# ruby -Ilib bin/facter |grep ec2 Cannot load GCE facts: no JSON gem available ec2_ami_id = ami-fa9cf1ca ec2_ami_launch_index = 0 ec2_ami_manifest_path = (unknown) ec2_block_device_mapping_ami = /dev/sda1 ec2_block_device_mapping_root = /dev/sda1 ec2_hostname = ip-172-16-128-22.us-west-2.compute.internal ec2_instance_action = none ec2_instance_id = i-0eba5906 ec2_instance_type = t1.micro ec2_kernel_id = aki-fc8f11cc ec2_local_hostname = ip-172-16-128-22.us-west-2.compute.internal ec2_local_ipv4 = 172.16.128.22 ec2_mac = 06:76:45:32:9c:e1 ec2_metrics_vhostmd = ?xml version=1.0 encoding=UTF-8? ec2_network_interfaces_macs_06:76:45:32:9c:e1_device_number = 0 ec2_network_interfaces_macs_06:76:45:32:9c:e1_interface_id = eni-15cc0362 ec2_network_interfaces_macs_06:76:45:32:9c:e1_ipv4_associations_54.186.106.90 = 172.16.128.22 ec2_network_interfaces_macs_06:76:45:32:9c:e1_local_hostname = ip-172-16-128-22.us-west-2.compute.internal ec2_network_interfaces_macs_06:76:45:32:9c:e1_local_ipv4s = 172.16.128.22 ec2_network_interfaces_macs_06:76:45:32:9c:e1_mac = 06:76:45:32:9c:e1 ec2_network_interfaces_macs_06:76:45:32:9c:e1_owner_id = 482693910459 ec2_network_interfaces_macs_06:76:45:32:9c:e1_public_hostname = ec2_network_interfaces_macs_06:76:45:32:9c:e1_public_ipv4s = 54.186.106.90 ec2_network_interfaces_macs_06:76:45:32:9c:e1_security_group_ids = sg-c8dd25ad ec2_network_interfaces_macs_06:76:45:32:9c:e1_security_groups = adrien-sg ec2_network_interfaces_macs_06:76:45:32:9c:e1_subnet_id = subnet-be060eca ec2_network_interfaces_macs_06:76:45:32:9c:e1_subnet_ipv4_cidr_block = 172.16.128.16/28 ec2_network_interfaces_macs_06:76:45:32:9c:e1_vpc_id = vpc-3c7d9c59 ec2_network_interfaces_macs_06:76:45:32:9c:e1_vpc_ipv4_cidr_block = 172.16.128.0/24 ec2_placement_availability_zone = us-west-2b ec2_profile = default-paravirtual ec2_public_hostname = ec2_public_ipv4 = 54.186.106.90 ec2_public_keys_0_openssh_key = ssh-rsa B3NzaC1yc2EDAQABAAABAQCoLR5VmIJgHaHQhDFJMTdm+86zvG4f6llpF87wUBpe+nIxfHvrcCnAr1yNa34BkJGYm8yYd3IYIhlnhGQ4SXdgk3DASg7TfdbToVV4f5lDxQB8O+HArs8/Nrx5BsxOhUWJTmaQnLnw+QVe7rCuiMdivHtAH9SrdZZjUQJkutgmGeCzKSQK5r6c4P5+PbSr8JQHEX7CoZiuxjVYFyh4ST4jtiHXoJbwjvdq7zsmhWknjdNx7v1TGz9P/1hFZR2Y7AULh+Q43rCZUB7Mo66qdwR1/jGQw3WhycqE+EiwpK0356OzWJeDklEd1Zc9qeLf2b8iCAt3QJqb+n4N4ywYGnBr adrien@grey ec2_reservation_id = r-7fe8f176 ec2_security_groups = adrien-sg I believe this should be a simple matter of backporting those changes onto the facter-2 branch. Add Comment
Jira (FACT-398) Smoke test packages
Title: Message Title Kylo Ginsberg commented on an issue Re: Smoke test packages Michelle Johansen We need moar meetings! Add Comment Facter / FACT-398 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Working on smoke testing, I've been side tracked with AWS work and interview training for most of the day. Add Comment Facter / FACT-398 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Validated on CentOS 5: architecture = i386 bios_release_date = 12/01/2006 bios_vendor = innotek GmbH bios_version = VirtualBox blockdevice_hda_size = 4294965248 blockdevice_hdc_size = 4294965248 blockdevice_sda_model = VBOX HARDDISK blockdevice_sda_size = 10632560640 blockdevice_sda_vendor = ATA blockdevices = hda,hdc,sda boardmanufacturer = Oracle Corporation boardproductname = VirtualBox boardserialnumber = 0 domain = localdomain facterversion = 2.0.1-rc3 filesystems = ext2,ext3,iso9660 fqdn = localhost.localdomain hardwareisa = i686 hardwaremodel = i686 hostname = localhost id = root interfaces = eth0,lo,sit0 ipaddress = 10.0.2.15 ipaddress_eth0 = 10.0.2.15 ipaddress_lo = 127.0.0.1 is_virtual = true kernel = Linux kernelmajversion = 2.6 kernelrelease = 2.6.18-348.el5 kernelversion = 2.6.18 macaddress = 08:00:27:14:DC:79 macaddress_eth0 = 08:00:27:14:DC:79 manufacturer = innotek GmbH memoryfree = 295.39 MB memoryfree_mb = 295.39 memorysize = 375.80 MB memorysize_mb = 375.80 mtu_eth0 = 1500 mtu_lo = 16436 mtu_sit0 = 1480 netmask = 255.255.255.0 netmask_eth0 = 255.255.255.0 netmask_lo = 255.0.0.0 network_eth0 = 10.0.2.0 network_lo = 127.0.0.0 operatingsystem = CentOS operatingsystemmajrelease = 5 operatingsystemrelease = 5.9 osfamily = RedHat path = /usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/vagrant/bin physicalprocessorcount = 1 processor0 = Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount = 1 productname = VirtualBox ps = ps -ef rubysitedir = /usr/lib/ruby/site_ruby/1.8 rubyversion = 1.8.7 selinux = true selinux_config_mode = enforcing selinux_config_policy = targeted selinux_current_mode = enforcing selinux_enforced = true selinux_policyversion = 21 serialnumber = 0 sshdsakey = B3NzaC1kc3MAAACBAKKhiPVK4t/rviwOHlRJglVybmwqmX710PsNh0/GjSj1Xl7i9WXBAUSyH01gTF70cmYDVlBsYK97n+yH4tBysavWJCweSYsCmoWAoIAnAxy0PkxfnvbdC8r1r7TIjqzYDctBFJlxDQJJbxP3pzPbiwoFQMuWYPg4ecWJCbAK1N2xFQChUyFqqu5EmmExX96rJSygMyDAtQAAAIEAliPF89Nmc10RGr8JMSPfiudEYJqkNRyWtEFXuS/7N9F8AWT4pWBQ0O/Tv5c6xPPFXoLaa/yl9Ht5v2ojmjhFyZzkgZt8BTKkd8PMUIDrTZteHGNC+p+XlWJsdVx1qmWAziqPx2ZqEQI7J5tmEc/qtpESO4GXPYbNlsCFpa/yy8gAAACAUCFlM7PurckeAee02QvJdxpDt/Za6AsHjn5IPwHLcujbFs0gD/fzjahTeVemv5upXqqVzqScbDkCTUyHlsjlYjWQZo9J+Vm0r81D6SxpGoseX3LoZmzllkWFVa2Oa/V9XqhxNcIbc3k065nXGwII5AxGQu5RZcmcqmwEL4oo5f4= sshfp_dsa = SSHFP 2 1 d1efc678ce197de277448223eece233ddab1af2c SSHFP 2 2 3f0a524896a8321895ca0e2d720081b407f42215d1784132502c9cdd8067fc22 sshfp_rsa = SSHFP 1 1 64ad22ccadfe518d06e9ed5ddcc99b958b153c8d SSHFP 1 2 7de57c080e5ff6e0686283e5894fd9c11b85eea68d3ce0c359d64121d2a072ad sshrsakey = B3NzaC1yc2EBIwAAAQEAnIJGJqJJbLnH7Lo4vNsRzasgyHOTeEfQPn7hdCq8RLt/R239VQe/P/82F2o0VWC5JgxzqsJjSFU/jzeP/ZA8UTSM8VXtwy7dwxdwp5XcAQfOthX8BParoEgKYoZ5DPs7B7ytiO91Em5euTT2L8Xz1Sum6HPTft4BxqJ4FD1VIOKwwMb6+gLT2gsbrDKx+IYyu9iJtbrm145q+3iLGPMFXdf+sdYb5nCu1E61R7dKyk5P/wqkco8ttxar3sTDqhZhvEsjF/Q216DpNzzmF139e+l0VotCd0dyepJBPXp0m/2qpNilNx8blSQ1d8Wkh+7O4HlxoiElDBkj+WrFuHJiFw== swapfree = 1.03 GB swapfree_mb = 1055.99 swapsize = 1.03 GB swapsize_mb = 1055.99 timezone = PDT type = Other uniqueid = 007f0100 uptime = 0:05 hours uptime_days = 0 uptime_hours = 0 uptime_seconds = 332 uuid = 11BAA974-A65E-472C-B5D5-303CFE073FC5 virtual = virtualbox
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Validated on CentOS 6: bios_release_date = 12/01/2006 bios_vendor = innotek GmbH bios_version = VirtualBox blockdevice_sda_model = VBOX HARDDISK blockdevice_sda_size = 10632560640 blockdevice_sda_vendor = ATA blockdevice_sr0_model = CD-ROM blockdevice_sr0_size = 1073741312 blockdevice_sr0_vendor = VBOX blockdevice_sr1_model = CD-ROM blockdevice_sr1_size = 1073741312 blockdevice_sr1_vendor = VBOX blockdevices = sda,sr0,sr1 boardmanufacturer = Oracle Corporation boardproductname = VirtualBox boardserialnumber = 0 facterversion = 2.0.1-rc3 filesystems = ext4,iso9660 hardwareisa = i686 hardwaremodel = i686 hostname = localhost id = root interfaces = eth0,lo ipaddress = 10.0.2.15 ipaddress_eth0 = 10.0.2.15 ipaddress_lo = 127.0.0.1 is_virtual = true kernel = Linux kernelmajversion = 2.6 kernelrelease = 2.6.32-358.el6.i686 kernelversion = 2.6.32 macaddress = 08:00:27:5A:A7:BF macaddress_eth0 = 08:00:27:5A:A7:BF manufacturer = innotek GmbH memoryfree = 432.93 MB memoryfree_mb = 432.93 memorysize = 467.01 MB memorysize_mb = 467.01 mtu_eth0 = 1500 mtu_lo = 16436 netmask = 255.255.255.0 netmask_eth0 = 255.255.255.0 netmask_lo = 255.0.0.0 network_eth0 = 10.0.2.0 network_lo = 127.0.0.0 operatingsystem = CentOS operatingsystemmajrelease = 6 operatingsystemrelease = 6.4 osfamily = RedHat path = /sbin:/bin:/usr/sbin:/usr/bin physicalprocessorcount = 1 processor0 = Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount = 1 productname = VirtualBox ps = ps -ef rubysitedir = /usr/lib/ruby/site_ruby/1.8 rubyversion = 1.8.7 selinux = false serialnumber = 0 sshdsakey = B3NzaC1kc3MAAACBANMQ3RN4DipyndspoCfX/Tyf5f1jMk6ChGnw7cpElrgZEa/qL1jZXCjTY7uJ9fkYW5vmWZniL9GkDSpypBYslycK92FczGDx61UVGF6QNYvaMpRoYyfruBBrR3kVaje89vzr2/JH18IlyfaOwFo/rHawGQfnknyavxIMPQyD+cdlFQCihVec1bguOTV1CX8rNvvyuDQRkQAAAIBdGVvpqueZoBnOGnz19EAbytgB0indR1+r0As5YIDfXprw4YAze+4UGAXEWDjRFzImwawSe4BrDDXxUYY3+MBK8cwxuLSwal5hropJy2V5kPL1vqnEYIJHcIU0fvas+cPdqikem+hMDib3+NgcqdfKCuHgdMvmWtVmVvaaTrTGBQAAAIBu5t0ZSw/bGSc/DFOGHU93eabaikilsMgx6sln31gnwQhgK/E7y2FV8MmWVv1t+Hnt6jOAaz61XxKxVzsmnSfIkJkeQ+K5aD4GUcCU2STj61rFOl4JPk3VBTjVnAryY/cw6xL2moWnDtBZdiHgz2TBZpQjQewW2cCKwt8aWYEYqw== sshfp_dsa = SSHFP 2 1 281581c44145ee674cc68ac8ca1298b3894e04bc SSHFP 2 2 7044190f754885c3874726cdb81e22f781a124bd151d253f1a95cb540d35d7f8 sshfp_rsa = SSHFP 1 1 98adf757db1b7e6e8b82e13f682dba1190c2787f SSHFP 1 2 60f8106db3c69cb0a1b18193f46009b32cc54f03dfc234ff30929377457d20e2 sshrsakey = B3NzaC1yc2EBIwAAAQEAyMga7AhTA85iE2s2ZbWHwHdCtOiduxt7HYJsyNTyAfTtTOaF4Xu5cr15fnm0D1KbyWhTRy2E+/91Q1awmfibVPyRh7tLeQ/ICOyloKFg/ca1bAEmoX9v/GCHT3zB0WE0CGwO3mCLwffJZXXkCXGnopRLtqG1zOedZFSQhd3GKpGxDW5jkfsZeiqUKjv0m695bh1Yog06pLZCv0WlelvwZBd+TW7CG4PRxYh1NroYWe0WQRevpECW2BOFeccHJo/UfF2qWff7BLd5+7/6h+aGsiF4ChOkAq3yihoHggE4cjmQemN59CbPYXCLxzW9IlXVQ/HS3QVe8USTmJNJRRjsNw== swapfree = 959.99 MB swapfree_mb = 959.99 swapsize = 959.99 MB swapsize_mb = 959.99 timezone = UTC type = Other uniqueid = 007f0100 uptime = 0:05 hours uptime_days = 0 uptime_hours = 0 uptime_seconds = 312 uuid = 55EC53D3-1A20-4D73-AE70-A3EA4E5DE7FA virtual = virtualbox
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Validated on Debian 7: architecture = i386 bios_release_date = 12/01/2006 bios_vendor = innotek GmbH bios_version = VirtualBox blockdevice_sda_model = VBOX HARDDISK blockdevice_sda_size = 10632560640 blockdevice_sda_vendor = ATA blockdevice_sr0_model = CD-ROM blockdevice_sr0_size = 1073741312 blockdevice_sr0_vendor = VBOX blockdevice_sr1_model = CD-ROM blockdevice_sr1_size = 1073741312 blockdevice_sr1_vendor = VBOX blockdevices = sda,sr0,sr1 boardmanufacturer = Oracle Corporation boardproductname = VirtualBox boardserialnumber = 0 domain = vagrantup.com facterversion = 2.0.1-rc3 filesystems = ext2,ext3 fqdn = debian-7-i386.vagrantup.com hardwareisa = unknown hardwaremodel = i686 hostname = debian-7-i386 id = root interfaces = eth0,lo ipaddress = 10.0.2.15 ipaddress_eth0 = 10.0.2.15 ipaddress_lo = 127.0.0.1 is_virtual = true kernel = Linux kernelmajversion = 3.2 kernelrelease = 3.2.0-4-686-pae kernelversion = 3.2.0 lsbdistcodename = wheezy lsbdistdescription = Debian GNU/Linux 7.0 (wheezy) lsbdistid = Debian lsbdistrelease = 7.0 lsbmajdistrelease = 7 macaddress = 08:00:27:7c:ea:12 macaddress_eth0 = 08:00:27:7c:ea:12 manufacturer = innotek GmbH memoryfree = 343.54 MB memoryfree_mb = 343.54 memorysize = 375.34 MB memorysize_mb = 375.34 mtu_eth0 = 1500 mtu_lo = 16436 netmask = 255.255.255.0 netmask_eth0 = 255.255.255.0 netmask_lo = 255.0.0.0 network_eth0 = 10.0.2.0 network_lo = 127.0.0.0 operatingsystem = Debian operatingsystemmajrelease = 7 operatingsystemrelease = 7.0 osfamily = Debian path = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin physicalprocessorcount = 1 processor0 = Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount = 1 productname = VirtualBox ps = ps -ef rubysitedir = /usr/local/lib/site_ruby/1.9.1 rubyversion = 1.9.3 selinux = false serialnumber = 0 sshdsakey = B3NzaC1kc3MAAACBAI2OsI8BNQK2qMDbuVZjiPRlIjh5I5DZWcV2Z05bS8Q+ni5GD/ZDa1SANaQecrNVo6y3RIpL8Uo7Prhl8mR8+uWh+kvGRPu0lhTpWhptiiAeqti0ch9WmhD+tjVczrAV6m3Tt7xiYN3Nq0e4sVHmZi0GWqT6bxEWTC0ZAm5WoJQRFQCJrPr3aIOQDABg/wbQOfZ4eZlziwAAAIAOgpGUgAWBjeT/KfHHNvB8leBlcMemWccx9VaUE32+5olWe4apPbZXKqyEnNvR9dgoK7r5HlgbKqnP4u0PYV+PS47uEMy7IwVB+b2c3kWc3AiBryeWMxb4uQLvYvpxu4/mVkIWix0G8xgo6DnueMks6OF03Tw5zzKkO0QmPE6IHgAAAIAeIjtBDcckLCRlNrQ36VwpJvUYd+zVe/4FsMecU6FN6J8wQ61MCnNbwB2UGVqNcR0AWSMCeJwYosSTMkEWeBV+/cs4yWteAee/slGBudC+HJxMYBHvbfjNSwJs9m/Z1WS517Lf8tWaSwbfFahdrVTWxYpLfAZt2QzxFKGpLESEKw== sshecdsakey = E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBJgtJl/IlHw74EqnSFT2xQRMZv2SHUogpIXN96GxxHfsx2x4TuZPHNrmmccp9u2MW3kpcWZzjLT552WPOiiQEW8= sshfp_dsa = SSHFP 2 1 204b51330d83ec15c3ed522692ac10f70a7c072f SSHFP 2 2 0920fe3e886fa5703969635615e117ebdaed21624d3d402956161337b722ed33 sshfp_ecdsa = SSHFP 3 1 2a365770ea6fd069c3c1f8b0b4b86c88b6b6b92a SSHFP 3 2 9a1dc83a76acef199fb765f24b194aecb8f6fc00e1ab7075d1562e119bed49b3 sshfp_rsa = SSHFP 1 1 6b2284770b39a525d6021b4a2b30e332762f115d SSHFP 1 2 26e33eabe0e8bcfdb538a99b9fba436fece8324f6a1e9f807c4d2a6bbd0e3da0 sshrsakey = B3NzaC1yc2EDAQABAAABAQCpRpNCshDHQoTYCv0azEdzpPoVVNqb44WJKtqs8WY75p+bp7hdmWRhKLN1a/ySsb1iObBTMO/w5wkBRg6UNUhfdsdYs4dg/hhjQGLRT9aXSNCCkDkgdSKO6PtRo+5WiMxIjnw2J4g9FLKh/M5rR+J58Mqd7jYGCdqUwhYw6ymfNk+B64mdd/CS9H/WqSpNl9eSLPUjteKgcMdm+o8V9u0iIC55/7eC6HSbJ824hNSv0JHaN3TFohbGddKAkFhZSS1igh3iKHGtXEwzrRkUYRdvTdEGKJgJiWvQylL/dDyc7qI5//h1uY2sU454KaEHJmq4FI5DJNCLEXTJwsVx9nTf swapfree = 456.00 MB swapfree_mb = 456.00 swapsize = 456.00 MB swapsize_mb = 456.00 timezone = UTC type = Other uniqueid = 007f0101 uptime = 0:05 hours uptime_days = 0 uptime_hours = 0 uptime_seconds = 321 uuid = 6D2813BC-02CD-491C-B6AA-ED08B2A62E8F virtual = virtualbox
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Validated on Debian 6: architecture = i386 bios_release_date = 12/01/2006 bios_vendor = innotek GmbH bios_version = VirtualBox blockdevice_sda_model = VBOX HARDDISK blockdevice_sda_size = 10632560640 blockdevice_sda_vendor = ATA blockdevice_sr0_model = CD-ROM blockdevice_sr0_size = 1073741312 blockdevice_sr0_vendor = VBOX blockdevice_sr1_model = CD-ROM blockdevice_sr1_size = 1073741312 blockdevice_sr1_vendor = VBOX blockdevices = sda,sr0,sr1 boardmanufacturer = Oracle Corporation boardproductname = VirtualBox boardserialnumber = 0 domain = dc1.puppetlabs.net facterversion = 2.0.1-rc3 filesystems = ext2,ext3 fqdn = debian-6-i386.dc1.puppetlabs.net hardwareisa = unknown hardwaremodel = i686 hostname = debian-6-i386 id = root interfaces = eth0,lo ipaddress = 10.0.2.15 ipaddress_eth0 = 10.0.2.15 ipaddress_lo = 127.0.0.1 is_virtual = true kernel = Linux kernelmajversion = 2.6 kernelrelease = 2.6.32-5-686 kernelversion = 2.6.32 lsbdistcodename = squeeze lsbdistdescription = Debian GNU/Linux 6.0.7 (squeeze) lsbdistid = Debian lsbdistrelease = 6.0.7 lsbmajdistrelease = 6 macaddress = 08:00:27:3a:9d:d7 macaddress_eth0 = 08:00:27:3a:9d:d7 manufacturer = innotek GmbH memoryfree = 343.57 MB memoryfree_mb = 343.57 memorysize = 375.61 MB memorysize_mb = 375.61 mtu_eth0 = 1500 mtu_lo = 16436 netmask = 255.255.255.0 netmask_eth0 = 255.255.255.0 netmask_lo = 255.0.0.0 network_eth0 = 10.0.2.0 network_lo = 127.0.0.0 operatingsystem = Debian operatingsystemmajrelease = 6 operatingsystemrelease = 6.0.7 osfamily = Debian path = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin physicalprocessorcount = 1 processor0 = Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount = 1 productname = VirtualBox ps = ps -ef rubysitedir = /usr/local/lib/site_ruby/1.8 rubyversion = 1.8.7 selinux = false serialnumber = 0 sshdsakey = B3NzaC1kc3MAAACBAMao58AjusuEma6TzpnF8h/lN7g0A3wWmAOyO8VuikEH4eCpE59AflF+z+c+jzhQa/oHl7fpf5XohTAkrY6W4Y/YQnOCkfrRKSa9NliRl+hYf+Y0lDTFr7Cdk8NE5aAWflNrVHxXrrSS+4x/D52BG5WnNG+psezosW6UuvciVMjLFQD3kZRXLhGZklygKctBIDY7Vb5TwQAAAIEAjMaroVHtoTu/3txJ/EeE6WJn4f37U/8j0harBF19KuJb8ult4sTlxg2FPGmdZBecPcMDbIxcuINzr2Jviyg9ZnzjbR44f106ZQgIFIjElO79XE3PsHJa0vfKpRuTmChnfcWgVH+T7tMLSRa9BO1kwy+Uj4bhqjpYpfpa/sWv+E8AAACBAKu4uMlXgwLDuqEfNZ5htQuIty6xkQRvPo1ziE06ppSj4Vy2NZy80OIFppwumkqKqxbS9j3SCxPj1M01Jsysx2HuJaWq0mTi/plMGxY3yN+YIbOpNGcOkOu1/JSlHMBjRwqEUy07Opo9SvhiBl5etWXw1V1Wg61VF0EOIp1xnV5b sshfp_dsa = SSHFP 2 1 e2dec8bb4349c557cab7111cdeece9060ee65b1c SSHFP 2 2 1505077ddefd207792093b808c0d247a7d1710df50a46910f02955769efc06ab sshfp_rsa = SSHFP 1 1 a03ec0d9ca479337890f4323309c810b293cb9b8 SSHFP 1 2 664da055eb8ae3e2cabc0cb465a5e2115295c659489adcde95c825e8a49d4a2d sshrsakey = B3NzaC1yc2EDAQABAAABAQCiKOi7C4mkdFzKbEugMDXZWE8aKwyJgakDarZdSrg7/Fmg7ihlprgv4pw3r1WNBmWFduvAEF1clQ/8aOcA2S9332FemzGVyvTSpoM2GtyLo5b2E07y2sPgLMEwtPZJSdOYjfBQZDTKYJlo003PVX5G2EKvkj30Ocqh1BI15QwJTJF6yhPw+9nlMJw1wlN9Z7oGKeeWPGW7c6d3GZceaAMlRFvyY30fb5Ip68m1f87lYA7tddEYPjY03NC9TbgDPJyzX2eLKH9mwzm6UCnIFGFkb7mwGsrEoILyvsjguJFSWHtubRCCOyGI5Aj5TSCf87Bw6sdomEq5QbTpGryWDac9 swapfree = 455.99 MB swapfree_mb = 455.99 swapsize = 455.99 MB swapsize_mb = 455.99 timezone = UTC type = Other uniqueid = 007f0101 uptime = 0:05 hours uptime_days = 0 uptime_hours = 0 uptime_seconds = 324 uuid = E8E5F221-309A-4E44-8BD8-CA086B959EA1 virtual = virtualbox
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title
Ryan Senior commented on an issue
Re: ERROR: duplicate key value violates unique constraint catalogs_pkey
I am able to reproduce this issue with the following steps:
1 - Install PuppetDB 1.5.2 (with a postgres as the store) 2 - Insert 10+ node catalogs 3 - Stop PuppetDB 4 - Upgrade to PuppetDB 1.6.2 5 - Submit a catalog for a new node (not part of the 10+ previous nodes) 6 - tail -f /var/log/puppetdb/puppetdb.log - will need to wait a minute or two as the message will be retried
The failure will say that it failed on id=5. The sequence is not being reset after the migration so the next key it should choose is one higher than the number of nodes that had catalogs inserted (i.e. 11). The insert fails, but the sequence still gets incremented, so it fails 5 times and eventually gives up.
Add Comment
PuppetDB / PDB-510
ERROR: duplicate key value violates unique constraint catalogs_pkey
We receive these errors every few minutes. Our logs indicate that these error began to occurring once our puppetdb instance was upgraded from 1.5.2 - 1.6.2. {code} 2014-03-12 15:33:03,107 ERROR [command-proc-82] [puppetdb.command] [7b979257-dda8-4d46-b8b2-242b88611523] [replace catalog] Retrying after attempt 12, due to: org.postgresql.util.PSQLEx...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Validated on Ubuntu 10.04: architecture = amd64 bios_release_date = 12/01/2006 bios_vendor = innotek GmbH bios_version = VirtualBox blockdevice_sda_model = VBOX HARDDISK blockdevice_sda_size = 10632560640 blockdevice_sda_vendor = ATA blockdevice_sr0_model = CD-ROM blockdevice_sr0_size = 1073741312 blockdevice_sr0_vendor = VBOX blockdevice_sr1_model = CD-ROM blockdevice_sr1_size = 1073741312 blockdevice_sr1_vendor = VBOX blockdevices = sda,sr0,sr1 boardmanufacturer = Oracle Corporation boardproductname = VirtualBox boardserialnumber = 0 domain = vm facterversion = 2.0.1-rc3 filesystems = ext2,ext3,ext4 fqdn = ubuntu-server-10044-x64-vbox4210-nocm.vm hardwareisa = unknown hardwaremodel = x86_64 hostname = ubuntu-server-10044-x64-vbox4210-nocm id = root interfaces = eth0,lo ipaddress = 10.0.2.15 ipaddress_eth0 = 10.0.2.15 ipaddress_lo = 127.0.0.1 is_virtual = true kernel = Linux kernelmajversion = 2.6 kernelrelease = 2.6.32-46-server kernelversion = 2.6.32 lsbdistcodename = lucid lsbdistdescription = Ubuntu 10.04.4 LTS lsbdistid = Ubuntu lsbdistrelease = 10.04 lsbmajdistrelease = 10 macaddress = 08:00:27:35:10:7d macaddress_eth0 = 08:00:27:35:10:7d manufacturer = innotek GmbH memoryfree = 317.01 MB memoryfree_mb = 317.01 memorysize = 367.41 MB memorysize_mb = 367.41 mtu_eth0 = 1500 mtu_lo = 16436 netmask = 255.255.255.0 netmask_eth0 = 255.255.255.0 netmask_lo = 255.0.0.0 network_eth0 = 10.0.2.0 network_lo = 127.0.0.0 operatingsystem = Ubuntu operatingsystemrelease = 10.04 osfamily = Debian path = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games physicalprocessorcount = 1 processor0 = Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount = 1 productname = VirtualBox ps = ps -ef rubysitedir = /usr/local/lib/site_ruby/1.8 rubyversion = 1.8.7 selinux = false serialnumber = 0 sshdsakey = B3NzaC1kc3MAAACBALgXGkqVE6srvj0+++yhW6jn5mFqiK65SPHOpVok5VKwb2Xh61QshNRa/E5JVkc3PrM81tQwHxseLWWgLO0jhWsrQk6fW5PFid4SBgRxumuC4Eb2wjCtQkBXtCDO/YmhN5dC1Y1s3hmVMci4gISqI8aMsiMz1VPldQJC9DTTwNGLFQCIintMfOw0Uk+Zovzyd6fzhcQn5wAAAIAGgIjtHoj6czvnC9pdSI18lr3PJj89GsEK/FGkAEcl8UaaI+pjElw60DVVOgBiDbigZFEzyntxTRvsjdLM7gGuLc7TEKNcrozrcScJ8CSSCYIc4cty3/4TBMjbDD8ra5bsbAl9Jts6fTnD/pPiQf95H4cfCpp19+XQ5fQzBAQcfgAAAIBMRqT6jZwsaIextRhm2Ezt2hrPPd4n8MpERHrItXsn5GiAbNXMf62Rhb76JQy/DzT0uSJDweUC4cazaRSUNDgxJjvX0xXuFv49Sf0yiibFYzmnJCvzISe+9AZe2eBWvm5sMKwzxz1cydyPUV8svvG79CapZlnWIPRrntKgDAOUtA== sshfp_dsa = SSHFP 2 1 356ca8ba949767942789cd6141c20244bfcbef70 SSHFP 2 2 ea0724f96bbf52c15d806ca3759e3cbc346bc9db0363d0cac700261c4bbfc03c sshfp_rsa = SSHFP 1 1 34e00d0846b32174b75c7f0b91443c4cc6e5604f SSHFP 1 2 9293219b21656b6647a7fdf19bf61aebe591b3c153b16017e69c440f7b885443 sshrsakey = B3NzaC1yc2EBIwAAAQEA0b1qlpz3m+Ul39u+sgzIdiQErIP7SOe6lr/FTKQyrGQMVaJq5uFx/OSQrLp4OPa62whDdqOW5HoLlHde4L2UclRHiz/PIMVi9b7h8MzysTlhZxu41GZLqwsmfHs0imILrSDOxDtbM0EhZfaQ/49r6QgMwiktTbOqUiQd1A4/Uu48Bfpkk1dRLKxZ/GyZxnVfGtIJrXsR1yfPkFYfkOiVwxG8ws85OjOPJPGI/Crug9Z9YDHEMWYmjMaMdTiybsb6DMITpMGXQjV1cDAQdaTDjhkdrj0OmeK25JRo40xe2M2c1X/uKhZLBTAtUmibLdTr0tXfGSwhREi5+r4tXpo8ZQ== swapfree = 471.99 MB swapfree_mb = 471.99 swapsize = 471.99 MB swapsize_mb = 471.99 timezone = CET type = Other uniqueid = 007f0101 uptime = 0:06 hours uptime_days = 0 uptime_hours = 0 uptime_seconds = 368 uuid = BEE1EE30-2D09-4D97-AF67-0207008DABE2 virtual = virtualbox
Jira (HI-127) Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Well... sort of.
For example, given the following Hiera data:
---
some_key: 'This string contains an %{%}{interpolation}'
One could define the key % to return % and thus turn % {%} into an escape:
# hiera some_key %=%
This string contains an %{interpolation}
However, this is mostly a hack and would be all sorts of messy to use from Puppet. The idea would be to update the Hiera interpolation code to treat %{%}
as an escape which would be pretty much backwards compatible as you would have to be doing something crazy to define % as a key for Hiera interpolation.
I'll look into re-organizing my escape function to achieve this.
Add Comment
Hiera / HI-127
Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
I have some data that contains Apache variables (such as %{SERVER_NAME}, %{QUERY_STRING}, etc ) in a Hiera file (Yaml backend). However, when I retrieve the value, the string is replaced with empty value. For instance, for: myserver: http://%{SERVER_NAME} I got the value http// I found out that during the lookup in the YAML backend, the answ...
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Validated on Ubuntu 12.04: architecture = amd64 bios_release_date = 12/01/2006 bios_vendor = innotek GmbH bios_version = VirtualBox blockdevice_sda_model = VBOX HARDDISK blockdevice_sda_size = 10632560640 blockdevice_sda_vendor = ATA blockdevice_sr0_model = CD-ROM blockdevice_sr0_size = 1073741312 blockdevice_sr0_vendor = VBOX blockdevice_sr1_model = CD-ROM blockdevice_sr1_size = 1073741312 blockdevice_sr1_vendor = VBOX blockdevices = sda,sr0,sr1 boardmanufacturer = Oracle Corporation boardproductname = VirtualBox boardserialnumber = 0 facterversion = 2.0.1-rc3 filesystems = ext2,ext3,ext4,vfat hardwareisa = x86_64 hardwaremodel = x86_64 hostname = ubuntu-server-12042-x64-vbox4210-nocm id = root interfaces = eth0,lo ipaddress = 10.0.2.15 ipaddress_eth0 = 10.0.2.15 ipaddress_lo = 127.0.0.1 is_virtual = true kernel = Linux kernelmajversion = 3.5 kernelrelease = 3.5.0-23-generic kernelversion = 3.5.0 lsbdistcodename = precise lsbdistdescription = Ubuntu 12.04.2 LTS lsbdistid = Ubuntu lsbdistrelease = 12.04 lsbmajdistrelease = 12 macaddress = 08:00:27:0f:67:ea macaddress_eth0 = 08:00:27:0f:67:ea manufacturer = innotek GmbH memoryfree = 425.84 MB memoryfree_mb = 425.84 memorysize = 491.21 MB memorysize_mb = 491.21 mtu_eth0 = 1500 mtu_lo = 16436 netmask = 255.255.255.0 netmask_eth0 = 255.255.255.0 netmask_lo = 255.0.0.0 network_eth0 = 10.0.2.0 network_lo = 127.0.0.0 operatingsystem = Ubuntu operatingsystemrelease = 12.04 osfamily = Debian path = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin physicalprocessorcount = 1 processor0 = Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount = 1 productname = VirtualBox ps = ps -ef rubysitedir = /usr/local/lib/site_ruby/1.8 rubyversion = 1.8.7 selinux = false serialnumber = 0 sshdsakey = B3NzaC1kc3MAAACBAM7xkV/4Q+vcuK0a6af7qVEoc6eSM6GbvFuzoTBV5op14wl0ajkxUlrOdXG0gQDsA+2j+5TyyKkdhD2Wdkkji1cagA1mUJFDcVSVeXipFibBtd7wmGNdbEbCjByL8ZM71AS3y6JywygpoX3k9l+qhuJdc01wwNRV937Md1+zmNF/FQCPEqcFfYRS0J9qxTkotkDb0ObF8wAAAIEAjteqq8MGXAejpufCbR5BF7992wo/naz6WOi1e5hcE53rQ/3GEBQhN7qEu+79wA1jZs2433xOoK9aA76pXIZs682pf022wDIN/RRa/8pjoH603asbY30NookmyD7CdRKGu1NJW2XgEYHHvypa3d2TEf1/B/zZCEG0Sf0x+MTFwuMAAACBAI3VHzREuRjdt+Pjv2UrXVtbuQYlAuXTzL5k3LPoCJX6bZWxB8ZkBH5TUVY0dm8+Z5jT8uyfOlez8rx6dSb5yCU/xtCYv6od9qvn1bRQGqwME9uRSKUuobu8lDD0sAaeHEhBskPbYQTiFImG51uW5K9uutTR7+sqs1TqWB/czPsw sshecdsakey = E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLBtSpI6A01NXAodidU0F2aFYsKsZS/w3TQC79BSBiIX7jkr61Sk5U9ui98DJ75yI1cu40m0U1UYyx6ic8YrmCw= sshfp_dsa = SSHFP 2 1 50660f826759a12fe1a9a798418936739b1e41cf SSHFP 2 2 d88a5eee3ca9e8c68f668ad7fd21f5feb8b324bd2efaa35b78fcdcf415496279 sshfp_ecdsa = SSHFP 3 1 5ac9d8a3d8d21350da19cd71d21b1cb4ddcd32e1 SSHFP 3 2 31425eee47ed3ae3e968f6bc48ab5a645f899744848d81d768b2ad38b43c289b sshfp_rsa = SSHFP 1 1 ff2e5147dbd06309221334e95182a2578376b99c SSHFP 1 2 a4fa733c8b80d653e1f7bde1a62aa32e7d3b011681ee59bfd014642d8900f744 sshrsakey = B3NzaC1yc2EDAQABAAABAQCXu5RlDOqQ9yghl+U0dkglhOQD6maadTZ34t8KlEwjFnhOx1jpbKVRG2vIJCDusHcIxYPS+uN4owEFbz7l9MtEwCMkzf9fg1imlzRnItAkFtcDZx/jV/PDWcESnTXhc2DRW51IM3pzyHoYThj/cQF4rRDlif1S0H6uj9soJRQi/ftoB62Zkme4j6/GMhY6iJzH3KifTAd3gxaRdp/28/Ym+Q1YZNXAq/BpnNSTEhg9kyHX6M9aTOfZ1K4jqtQaJSiJxZvVZMcWP2lbwIy3NR2uX6D27LK0vd57XOj49R6RjhAnFEKq1Hxa1qOdQrYEeGLuFqMEVwVT6NNuRgFIpyyx swapfree = 512.00 MB swapfree_mb = 512.00 swapsize = 512.00 MB swapsize_mb = 512.00 timezone = UTC type = Other uniqueid = 007f0101 uptime = 0:06 hours uptime_days = 0 uptime_hours = 0 uptime_seconds = 368 uuid = 75C8ECCC-682B-43BF-A6AE-F9A3BCC54931 virtual = virtualbox
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages If someone could validate Ubuntu 14.04 that would be fantastic, but I seriously doubt that anything on Ubuntu has changed since rc3 only contains solaris specific fixes. Add Comment Facter / FACT-398 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2016) Invalid Characters Allowed in Windows Paths for Puppet Resource Type 'file'
Title: Message Title Joshua Cooper moved an issue Puppet / PUP-2016 Invalid Characters Allowed in Windows Paths for Puppet Resource Type 'file' Change By: Joshua Cooper Component/s: Platform Component/s: PE Affects Version/s: 3.2.1 Affects Version/s: 3.x Workflow: PuppetEnterprise Platform Workflow Key: PE PUP - 3192 2016 Project: Puppet Enterprise[Internal] Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Validated on Solaris 10: architecture = i86pc bios_release_date = 12/01/2006 bios_vendor = innotek GmbH bios_version = 1.2 domain = corp.puppetlabs.net facterversion = 2.0.1-rc3 fqdn = solaris-10u11-i386-vbox4210-nocm.corp.puppetlabs.net hardwareisa = i386 hardwaremodel = i86pc hostname = solaris-10u11-i386-vbox4210-nocm id = root interfaces = lo0,e1000g0 ipaddress = 10.0.2.15 ipaddress_e1000g0 = 10.0.2.15 ipaddress_lo0 = 127.0.0.1 is_virtual = true kernel = SunOS kernelmajversion = Generic_147148-26 kernelrelease = 5.10 kernelversion = Generic_147148-26 macaddress = 08:00:27:b8:fd:d1 macaddress_e1000g0 = 08:00:27:b8:fd:d1 manufacturer = innotek GmbH memoryfree = 568.82 MB memoryfree_mb = 568.82 memorysize = 768.00 MB memorysize_mb = 768.00 mtu_e1000g0 = 1500 mtu_lo0 = 8232 netmask = 255.255.255.0 netmask_e1000g0 = 255.255.255.0 netmask_lo0 = 255.0.0.0 network_e1000g0 = 10.0.2.0 network_lo0 = 127.0.0.0 operatingsystem = Solaris operatingsystemmajrelease = 10 operatingsystemrelease = 10_u11 osfamily = Solaris path = /opt/csw/bin:/usr/sbin:/usr/bin:/usr/ucb physicalprocessorcount = 1 processor0 = Intel(r) Core(tm) i7-3520M CPU @ 2.90GHz processorcount = 1 productname = VirtualBox ps = ps -ef rubysitedir = /opt/csw/lib/ruby/site_ruby/1.8 rubyversion = 1.8.7 serialnumber = 0 sshdsakey = B3NzaC1kc3MAAACBAPKE7MH3vAlt8pLc4SaLX17wZsYHQsDhjtL34mGNEj5pkMhDgsAW+FYP6ZxelVeqrCRtg2OhIJafbzOzaPtAhAiChLbPKGPj/TD6tp8SswhDICZVv0Qypa8+LwpLPfrRzFcOWNchzc60UsO32gm7jKz6AnJFR4X9+zVjf08GP1zHFQDRSsTO2HeXm6Uk2vR8QjYtDlD+VQAAAIBtEMq+kGJhu7K6IuPE9Za032cypwXceuQa5kC5Pjq0a1JYRFQu5o1EOF8iBK+GCSaQiw/3dKwwGzAqwVBzP7fkkBlCltg4hmMFIN/apRWimEYZ5cnzkTsSA/ei46farQusCCQyvLjHwHGytY5W6+M6V0uu/zC8CWyouiTeI3ALzQAAAIEAkwW5Zb9GPL3ChezElANl6JPp9SVdQuK4OMfz+KiDkTniKViboOYVk3fw7BSquCawrx4P4zMvl0/BYzjgY3MXovE7WPIWiYBymjSwMFqKwNC796zGFJTIZAA+57UCIRvfi3w3TC3lijYOZz3xoR9cCE5culcA1O6dHwe+E7bPLmg= sshfp_dsa = SSHFP 2 1 25a3c71a6026fe985e68e59563082b9aa9345067 SSHFP 2 2 92f67d668778ae15f10cfa1a162b73e2de8aaf7fe762875fd92ba113e994acaf sshfp_rsa = SSHFP 1 1 b09a53331e31234bd8f142605376caafaed4adee SSHFP 1 2 97733b4cfa5a467da3ae03a34eec05b46420d4dec9d141f0cd2cf6a117a768d1 sshrsakey = B3NzaC1yc2EBIwAAAIEAnIFUhzpTYkJFYp1V1aRL0Il34QkXwQwio42dSon2v6HuJW0lSkEBu13Mbl3O4vqIwz1fe9JZ3JQpIXHt7ehRxpdd6Sl8PpgCLJ5nmKX6LWFXZ8ZRQPsxhObXnYDgYByXdArRDGb/sdxTGuF8wIDAQpE+PGZb28EW7aee05o7o9U= swapfree = 1.00 GB swapfree_mb = 1027.59 swapsize = 1.00 GB swapsize_mb = 1027.59 timezone = GMT type = 0x1 (other) uniqueid = 187a449e uptime = 1:02 hours uptime_days = 0 uptime_hours = 1 uptime_seconds = 3720 uuid = 55a87d42-11e7-4638-b7d8-b026fce2e647 virtual = virtualbox zfs_version = 5 zonename = global zones = 0 zpool_version = 32 Add Comment
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo assigned an issue to Unassigned Facter / FACT-398 Smoke test packages Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-398) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Validated on Solaris 11: architecture = i86pc bios_release_date = 12/01/2006 bios_vendor = innotek GmbH bios_version = 1.2 facterversion = 2.0.1-rc3 hardwareisa = i386 hardwaremodel = i86pc hostname = solaris id = root interfaces = lo0,net0 ipaddress = 10.0.2.15 ipaddress_lo0 = 127.0.0.1 ipaddress_net0 = 10.0.2.15 is_virtual = true kernel = SunOS kernelmajversion = 11.0 kernelrelease = 5.11 kernelversion = 11.0 macaddress = 08:00:27:8a:41:62 macaddress_net0 = 08:00:27:8a:41:62 manufacturer = innotek GmbH memoryfree = 387.61 MB memoryfree_mb = 387.61 memorysize = 1024.00 MB memorysize_mb = 1024.00 mtu_lo0 = 8232 mtu_net0 = 1500 netmask = 255.255.255.0 netmask_lo0 = 255.0.0.0 netmask_net0 = 255.255.255.0 network_lo0 = 127.0.0.0 network_net0 = 10.0.2.0 operatingsystem = Solaris operatingsystemmajrelease = 11 operatingsystemrelease = 11 11/11 osfamily = Solaris path = /usr/bin:/usr/sbin physicalprocessorcount = 1 processor0 = Intel(r) Core(tm) i7-3520M CPU @ 2.90GHz processor1 = Intel(r) Core(tm) i7-3520M CPU @ 2.90GHz processorcount = 2 productname = VirtualBox ps = ps -ef rubysitedir = /usr/ruby/1.8/lib/ruby/site_ruby/1.8 rubyversion = 1.8.7 serialnumber = 0 sshdsakey = B3NzaC1kc3MAAACBAKjqh8EliP+gGOJEiXylIiihdrpeeka8Hlm2YooM3kOHcXosMDyy5UkvyGS1vUQR6f1vwxsIisIRWXMJ5R3XkBPt0tVMh8IgNf09O3cHvVj/pKJNshL2svh3pxGI+FiG/qRGxlu9ffBE66LXEMiTTe6xUTGsUOuq58rYkFbkU+ArFQDUtk9HjEYD+se7Wc7uDzjndWNUDwAAAIEAj8RiMaJxWP3Oon4+psSeWQ3+EhnyoOnoKCI2SxRanH7OS/n94V4hBMampEGg3DYchClpPBTt2g5jOcwK3ZDwBEjmaLu1P2pHSSeuclCjIVOuYBd2CH84+RYe4W4GPQsW+n97spIcuOU/Pb2GCiwkKG8+cT3bzBxL8nVgyF8iYO8AAACAIRRmmU+0n1yjvlfZF2pg+E7ZaQZNg6EAfR31SYiFucaJTsW7AsuIZNo4OsS5VID/0jFYBX6dj+KXwbySOZeRh5wLSh6pCDAcLKvBWU1OjyhhSrCaRDGNAXRruoncjBZaihRfveeW6iC3qEAJYD7bJWwMs0ZBdtSZGEjgXnpTz9U= sshfp_dsa = SSHFP 2 1 d892956d51fc34fbf58b88fa936a08d728bbc313 SSHFP 2 2 66adde1d55811e7a3ada3cb6c35dd9f3ded3f155c7b6b2c58211b202268ab250 sshfp_rsa = SSHFP 1 1 068d79cfcd3712fb4d8b6361f48375cdbd15f3ee SSHFP 1 2 b05cf9c168ea66f0b90afef72070db584eb8d885d4c9119185147d8b4dd07471 sshrsakey = B3NzaC1yc2EBIwAAAQEA276CP3DYbSmbrvf0ITibks3LSvFm5UUOgIiBkmTPXlcGnohih+lGzIIZGEgezCylWW3yU4npdWN4pFvjd5iCQYiab/LPdJgc7Vc3dPiacmrTMVTQylVmsKmeCu/H70pZmAeNO4Iks2Qb5/gOmZZkxxVvk0OjtPpOEI7TbZKdRUNafKcabjpYKc7PhRx5stf0AjRbCyJEzn1noPNHKbUTTjO5+t3zUXo1tVlfI03Tsmho1UQ+NdR9x2wPHwEM5P3jLDHoZe8WsW83Vt9EsUZPx04+Pf+2VhovRvuHTeDrHjHdnb3M7WrMHYJHs8t7UxDMJFbk3JEFVINxgrg3OX0ycQ== swapfree = 1024.00 MB swapfree_mb = 1024.00 swapsize = 1024.00 MB swapsize_mb = 1024.00 timezone = PDT type = 0x1 (other) uniqueid = 008be47f uptime = 0:05 hours uptime_days = 0 uptime_hours = 0 uptime_seconds = 300 uuid = 509c74d0-4559-4134-be89-276fb193ff66 virtual = virtualbox zfs_version = 5 zone_global_brand = solaris zone_global_id = 0 zone_global_iptype = shared zone_global_name = global zone_global_path = / zone_global_status = running zone_global_uuid = zonename = global zones = 1 zpool_version = 33 Add Comment
Jira (FACT-378) Facter 1.7.5 on Windows Server 2012 R2: Can't parse first line of a YAML file
Title: Message Title
Joshua Cooper commented on an issue
Re: Facter 1.7.5 on Windows Server 2012 R2: Can't parse first line of a YAML file
Gerard Ryan for future reference, the characters you are seeing {{ }} are the byte order mark (BOM), which MS often uses to signify the encoding of the data that follows, e.g. UTF-8, UTF-16LE. Puppet (and ruby) do not automatically strip these off when trying to read a file, thereby causing the problem.
Add Comment
Facter / FACT-378
Facter 1.7.5 on Windows Server 2012 R2: Can't parse first line of a YAML file
This issue should be very easy to reproduce. I have tested it in two different server 2012 instances... one in VMware Workstation 10.0 running vSphere/ESXi and the other in AWS EC2. In both cases I have added a custom YAML file to C:\ProgramData\PuppetLabs\facter\facts.d and populated it with custom facts, thusly: app_project: sfa app_environment: ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 (FACT-378) Facter 1.7.5 on Windows Server 2012 R2: Can't parse first line of a YAML file
Title: Message Title Gerard Ryan commented on an issue Re: Facter 1.7.5 on Windows Server 2012 R2: Can't parse first line of a YAML file Yes, I realized that and simply now I rewrite the file in ASCII encoding to fix it; e.g.: $yaml = 'C:\ProgramData\PuppetLabs\Facter\facts.d\facts.yaml' (Get-Content $yamlfile) | Set-Content -Encoding ASCII $yamlfile Thanks! Add Comment Facter / FACT-378 Facter 1.7.5 on Windows Server 2012 R2: Can't parse first line of a YAML file This issue should be very easy to reproduce. I have tested it in two different server 2012 instances... one in VMware Workstation 10.0 running vSphere/ESXi and the other in AWS EC2. In both cases I have added a custom YAML file to C:\ProgramData\PuppetLabs\facter\facts.d and populated it with custom facts, thusly: app_project: sfa app_environment: ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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,
Jira (PUP-1796) File resource fails for root(/) directory.
Title: Message Title
Joshua Cooper commented on an issue
Re: File resource fails for root(/) directory.
This is coming from the title_patterns regexp:
[ [ /^(.*?)\/*\Z/m, [ [ :path ] ] ] ]
which attempts to strip trailing slashes. When the regexp is applied to the resource title, it resulting in the path being set to the empty string.
Add Comment
Puppet / PUP-1796
File resource fails for root(/) directory.
I know this is probably an extreme edge case, but I recently noticed that this fails: {code} file { '/': ensure = directory } with the error: Parameter path failed: File paths must be fully qualified, not '' at /tmp/test.pp:1 {code} A little background, This comes from a larger module that I have which uses the lvm module to create additional...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the
Jira (PUP-1986) Permissions for libdir are set arbitrarily
Title: Message Title Joshua Cooper commented on an issue Re: Permissions for libdir are set arbitrarily This behavior occurs because pluginsync is implemented as a file resource with a remote source and recursion set to true, and puppet has historically applied the permissions from the remote puppet master to the local agent (see https://projects.puppetlabs.com/issues/5240). The latter behavior is problematic, and in Puppet 3.4, we added the ability to disable it. See https://projects.puppetlabs.com/issues/18931 and http://docs.puppetlabs.com/references/latest/type.html#file-attribute-source_permissions We also changed the downloader to ignore source permissions on Windows: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/configurer/downloader.rb#L62. We could just do the same for *nix, unless modules rely on this, e.g. if a module contains a shared library that needs to be executable? Add Comment Puppet / PUP-1986 Permissions for libdir are set arbitrarily It appears that the mode for libdir is set during pluginsync, to the mode of the lib/ directory of some module being synced (apparently whichever comes first). However, the owner and group are always set to root. This means that a module which is readable only by puppet in the modulepath becomes readable only by root in the libdir. That causes problems fo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Joshua Cooper commented on an issue Re: Pre/Post-run commands don't work under Windows Ken Johnson I suspect it works fine on *nix, because there are two different exec code paths for *nix and Windows as described in PUP-1435 Add Comment Puppet / PUP-1431 Pre/Post-run commands don't work under Windows If a postrun or prerun command is specified in puppet.conf on a Windows host it will fail to execute with a message like the following: Debug: Executing 'C:\Windows\System32\cmd.exe /c type NUL C:\from_postrun.txt' Error: Could not run command from postrun_command: CreateProcess() failed: The system cannot find the file specified.Example postr... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-127) Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Pull request submitted: https://github.com/puppetlabs/hiera/pull/185
Add Comment
Hiera / HI-127
Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
I have some data that contains Apache variables (such as %{SERVER_NAME}, %{QUERY_STRING}, etc ) in a Hiera file (Yaml backend). However, when I retrieve the value, the string is replaced with empty value. For instance, for: myserver: http://%{SERVER_NAME} I got the value http// I found out that during the lookup in the YAML backend, the answ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Ken Johnson commented on an issue Re: Pre/Post-run commands don't work under Windows Joshua Cooper That makes sense. Add Comment Puppet / PUP-1431 Pre/Post-run commands don't work under Windows If a postrun or prerun command is specified in puppet.conf on a Windows host it will fail to execute with a message like the following: Debug: Executing 'C:\Windows\System32\cmd.exe /c type NUL C:\from_postrun.txt' Error: Could not run command from postrun_command: CreateProcess() failed: The system cannot find the file specified.Example postr... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-127) Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Also worth noting is that the prior workaround of:
foo: %%{THIS_DOESNT_EXIST}{BAR}
Now works again under Hiera 1.3.2 due to way
HI-115
was resolved.
Add Comment
Hiera / HI-127
Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
I have some data that contains Apache variables (such as %{SERVER_NAME}, %{QUERY_STRING}, etc ) in a Hiera file (Yaml backend). However, when I retrieve the value, the string is replaced with empty value. For instance, for: myserver: http://%{SERVER_NAME} I got the value http// I found out that during the lookup in the YAML backend, the answ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1951) Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed
Title: Message Title Joshua Cooper commented on an issue Re: Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed is there a way to run the elevated puppet agent from the command line? It's complicated... The common scenario is that the user is a member of the local Administrators group, but is not the Administrator, and UAC is enabled. They have opened a shell running with their restricted process token, and want to execute the analog of sudo puppet agent. In that scenario, the answer is no, there is no official Windows way to elevate privileges, and that is why we vendor the aptly named elevate.exe. The one thing that users can do is to run a command as the Administrator user with full privileges: runas /User:Administrator \C:\Program Files (x86)\Puppet Labs\Puppet\bin\puppet.bat\ agent Note this isn't sudo in the *nix sense, instead it's login as a different user and execute a command. So you have to know the Administrator password, not your own password. The other option, which is more like sudo, is to select Start Command Prompt with Puppet, right-click, and Run as administrator. This will execute a shell as you, but with full privileges. This is functionality we support today, but people often forget to right-click. It's the number 1 or 2 question we get on the mailing lists, along with filesystem redirection. So having the Run Puppet menu item that automatically elevates is a nice shortcut, though it does introduce a dependency, but only if you attempt to use the start menu item. We could just remove the Run Puppet menu item, switch Run Facter to run not elevated, and document how to do elevate puppet agent -td on the command line. Ethan Brown Rob Reynolds thoughts? Add Comment Puppet / PUP-1951 Unable to Run Facter or Run
Jira (PUP-1827) Permission denied when installing modules on Windows
Title: Message Title
Joshua Cooper updated an issue
Puppet / PUP-1827
Permission denied when installing modules on Windows
Change By:
Joshua Cooper
Whentryingtoinstallamodulespecifyingthe--modulepathIgetthis: {code} #puppetmoduleinstalljoshcooper/powershell--modulepath./modules--debug--traceNotice:Preparingtoinstallintoe:/dev/vagrant-teamcity/modules...Notice:Downloadingfromhttps://forge.puppetlabs.com...Failedtoadd/C=ZA/ST=WesternCape/L=Durbanville/O=Thawte/OU=ThawteCertification/CN= Thawte Thawte TimestampingCAFailedtoadd/C=US/ST=Washington/L=Redmond/O=MicrosoftCorporation/CN=MicrosoftRoot Certificate Certificate Authority2010Failedtoadd/C=ZA/ST=WesternCape/L=Durbanville/O=Thawte/OU=ThawteCertification/CN= Thawte Thawte TimestampingCAFailedtoadd/C=US/ST=Washington/L=Redmond/O=MicrosoftCorporation/CN=MicrosoftRoot Certificate Certificate Authority2010Notice:Installing--donotinterrupt...Debug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/Debug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/GemfileDebug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/Gemfile.lockDebug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/lib/Debug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/metadata.jsonDebug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/ModulefileDebug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/README.mdDebug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/spec/Debug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/tests/Debug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/tests/init.ppDebug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e /joshcooper-powershell-0.0.6/spec/spec_helper.rbDebug:extractingC:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker- 5f1b23f2a94f96094dc13e51ddc08349f3157c2e 5f1b23f2a94f96094dc13e51ddc08349f3157c2e
Jira (PUP-1827) Permission denied when installing modules on Windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1827 Permission denied when installing modules on Windows Change By: Joshua Cooper Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-127) Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
And finally, I just noticed that a % sign followed by an empty interpolation works:
---
some_key: 'This string contains an %%{}{interpolation}'
That makes me wonder if we should just add some unit tests that enforce that behavior for %%{} and call this ticket solved.
Add Comment
Hiera / HI-127
Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
I have some data that contains Apache variables (such as %{SERVER_NAME}, %{QUERY_STRING}, etc ) in a Hiera file (Yaml backend). However, when I retrieve the value, the string is replaced with empty value. For instance, for: myserver: http://%{SERVER_NAME} I got the value http// I found out that during the lookup in the YAML backend, the answ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1827) Permission denied when installing modules on Windows
Title: Message Title
Joshua Cooper commented on an issue
Re: Permission denied when installing modules on Windows
Failed to add /C=ZA/ST=Western Cape/L=Durbanville/O=Thawte/OU=Thawte Certification/CN=Thawte Timestamping CA
Are you running as a standard user, not as an administrator?
Error: Permission denied - (C:/ProgramData/PuppetLabs/puppet/var/puppet-module/cache/tmp-unpacker-5f1b23f2a94f96094dc13e51ddc08349f3157c2e/joshcooper-powershell-0.0.6, e:/dev/vagrant-teamcity/modules/powershell)
This is likely https://bugs.ruby-lang.org/issues/8109. Ruby 1.9.3 FileUtils.mv calls MoveFile on Windows, which doesn't work across devices. Ruby fixed the issue in 35cc29c872, first released in v2_1_0.
Add Comment
Puppet / PUP-1827
Permission denied when installing modules on Windows
When trying to install a module specifying the --modulepath I get this: {code} #puppet module install joshcooper/powershell --modulepath ./modules --debug --trace Notice: Preparing to install into e:/dev/vagrant-teamcity/modules ... Notice: Downloading from https://forge.puppetlabs.com ... Failed to add /C=ZA/ST=Western Cape/L=Durbanville/O=Thawte/...
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-510 ERROR: duplicate key value violates unique constraint catalogs_pkey Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-514) Add optional type to parameters
Title: Message Title
Henrik Lindberg commented on an issue
Re: Add optional type to parameters
That syntax is what I also expect it to have (not that you have to assign to it to make it typed - in fact, in that case it could be automatically typed to the type of the given value if we want to, the user could widen the type if required)
define foo($var = 1) { ... }
foo { 'this_is_my_foo':
var = 'batman'
}
Would fail with an error with something like: 'String batman not assignable to Integer foo::var'
Which could be widened:
define foo(Scalar $var = 1) { ... }
foo { 'this_is_my_foo':
var = 'batman'
}
Now it works because String and Integer are both Scalar. (And you would use Object to widen to anything).
On second thought though, users can then not opt out of typing when they use defaults... ah - well... guess this type inference is off the table for that reason.
Add Comment
Puppet / PUP-514
Add optional type to parameters
It is of great value to be able to optionally type the parameters of defines and classes (as well as types). This is quite easy to implement as there now is a type system. The default type is Data.
Jira (PDB-144) Ability to query embedded hsqldb database
Title: Message Title Kenneth Barber commented on an issue Re: Ability to query embedded hsqldb database These instructions are quite raw, but seem to work for me: Grab a copy of 2.2.8 from: http://sourceforge.net/projects/hsqldb/files/hsqldb/hsqldb_2_2/ You'll need an rc file: # cat /root/sqltool.rc # A personal, local, persistent database. urlid puppetdb url jdbc:hsqldb:file:/var/lib/puppetdb/db;hsqldb.tx=mvcc;sql.syntax_pgs=true username SA password driver org.hsqldb.jdbcDriver Unpack the zip file in /root (for example) Then use: # java -jar /root/hsqldb-2.2.8/hsqldb/lib/sqltool.jar Once the cli tool opens, use \j puppetdb to connect to the puppetdb database. Add Comment PuppetDB / PDB-144 Ability to query embedded hsqldb database
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title
Kenneth Barber commented on an issue
Re: ERROR: duplicate key value violates unique constraint catalogs_pkey
WIP PR is here: https://github.com/puppetlabs/puppetdb/pull/890
Add Comment
PuppetDB / PDB-510
ERROR: duplicate key value violates unique constraint catalogs_pkey
We receive these errors every few minutes. Our logs indicate that these error began to occurring once our puppetdb instance was upgraded from 1.5.2 - 1.6.2. {code} 2014-03-12 15:33:03,107 ERROR [command-proc-82] [puppetdb.command] [7b979257-dda8-4d46-b8b2-242b88611523] [replace catalog] Retrying after attempt 12, due to: org.postgresql.util.PSQLEx...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
