Jira (PUP-3463) Remove tagmail
Title: Message Title Lindsey Smith PO updated an issue Puppet / PUP-3463 Remove tagmail Change By: Lindsey Smith PO Tagmailisnotagreatwaytohandlereportsforpuppet.Takingactiononreportsshouldbehandledbymonitoringsystemsinstead.Thetagmailsystemhasbeenaroundforalongtime,butpresentsseveralproblemsbecauseitforksaprocessinordertosendemails.Thismakesitincompatiblewiththepuppet-server,whichwilleventuallybetheonlywayofrunningthepuppetmaster.Therearemanysettingsthatgoalongwithtagmailthatwillneedtoberemovedaswell. Seealsohttps://docs.puppetlabs.com/puppet/latest/reference/config_file_tagmail.html Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-950) PuppetDB returns 500 error as HTML when query contains invalid regex
Title: Message Title Lindsey Smith PO commented on PDB-950 Re: PuppetDB returns 500 error as HTML when query contains invalid regex Thanks for the update Kenneth Barber. What trigger the comment was more learning that the PDB wasn't planning to do 2.x release in the near future, which would mean we wouldn't be able to get this into a PE 3.7.x unless went some route like cherrypicking a fix, etc. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-950) PuppetDB returns 500 error as HTML when query contains invalid regex
Title: Message Title Lindsey Smith PO commented on PDB-950 Re: PuppetDB returns 500 error as HTML when query contains invalid regex In any case, it's good that there's already a PR. Who would need to be involved with getting this into PE? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-950) PuppetDB returns 500 error as HTML when query contains invalid regex
Title: Message Title Lindsey Smith PO commented on PDB-950 Re: PuppetDB returns 500 error as HTML when query contains invalid regex Is this something that we could porentially cherrypick a fix for inclusion in PE 3.7.1? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-903) CSV output from the REST API
Title: Message Title Lindsey Smith PO commented on an issue Re: CSV output from the REST API Thanks Kenneth Barber. Also Verne Lindner FYI. Add Comment PuppetDB / PDB-903 CSV output from the REST API The PuppetDB REST API allows quick and easy queries but the output is only available comes as JSON, which is great if there’s a JSON aware API on the other end doing the query, but isn’t useable for ad-hoc queries destined for analysis in Excel or similar tools. So the framework is here for building your own reporting, but it isn’t something that I can ha... 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-903) CSV output from the REST API
Title: Message Title Lindsey Smith PO created an issue PuppetDB / PDB-903 CSV output from the REST API Issue Type: Bug Assignee: Unassigned Created: 01/Oct/14 9:41 AM Priority: Normal Reporter: Lindsey Smith PO The PuppetDB REST API allows quick and easy queries but the output is only available comes as JSON, which is great if there’s a JSON aware API on the other end doing the query, but isn’t useable for ad-hoc queries destined for analysis in Excel or similar tools. So the framework is here for building your own reporting, but it isn’t something that I can hand to a project manager without significant up front work. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title
Lindsey Smith PO commented on an issue
Re: Provide means to request events from latest report in timeframe
FYI Beth Cornils
Add Comment
PuppetDB / PDB-112
Provide means to request events from latest report in timeframe
h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des...
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-112) Provide means to request events from latest report in timeframe
Title: Message Title
Lindsey Smith PO commented on an issue
Re: Provide means to request events from latest report in timeframe
Ping Deepak Giridharagopal
Add Comment
PuppetDB / PDB-112
Provide means to request events from latest report in timeframe
h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des...
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-112) Provide means to request events from latest report in timeframe
Title: Message Title
Lindsey Smith PO commented on an issue
Re: Provide means to request events from latest report in timeframe
I don't think I know what the standard fashion is for PDB prioritization.
Add Comment
PuppetDB / PDB-112
Provide means to request events from latest report in timeframe
h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des...
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-3044) Expand Puppet File Permissions
Title: Message Title Lindsey Smith PO created an issue Puppet / PUP-3044 Expand Puppet File Permissions Issue Type: Improvement Assignee: Unassigned Created: 11/Aug/14 1:50 PM Labels: support Priority: Normal Reporter: Lindsey Smith PO Please consider expanding puppet file permissions beyond posix, specifically, linux-based setfacl extended users and groups, as well as permission inheritance. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2638) Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Title: Message Title Lindsey Smith PO created an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing Issue Type: Bug Assignee: Unassigned Created: 22/May/14 1:11 PM Priority: Normal Reporter: Lindsey Smith PO I was creating a masterless puppet agent on a fresh Windows 8 installation, so I installed the Puppet agent with the following command line; MSIEXEC /i source\puppet-enterprise-3.2.3.msi PUPPET_AGENT_STARTUP_MODE=Disabled REBOOT=ReallySuppress ALLUSERS=1 /qb- /l*v c:\PuppetAgent.Install.log Then I tried to run a Puppet Apply with the following command line; C:\Windows\SysWOW64\cmd.exe /E:ON /C C:\Program Files (x86)\Puppet Labs\Puppet Enterprise\bin\puppet.bat apply --modulepath=%LOCALSRC%\modules %LOCALSRC%\manifests\site.pp However i received an error that it could not created resources.dot. It was trying to create it in C:\ProgramData\PuppetLabs\puppet\var\state\graphs which looks like the expected place, however the directory structure was incomplete. Only C:\ProgramData\PuppetLabs\puppet\var existed. If I manually created this directory (MD C:\ProgramData\PuppetLabs\puppet\var\state\graphs) and then ran Puppet Apply it executed fine. It seems like that the code that creates the resources.dot file does not check for the existence of the dependent directory structure first.
Jira (PUP-2638) Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Title: Message Title
Lindsey Smith PO updated an issue
Puppet / PUP-2638
Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Change By:
Lindsey Smith PO
Iwascreating ViaENTERPRISE-181:Thisis a masterless general puppet agent platformissue.Itcanoccur( on afreshWindows8installation,soIinstalled anyplatform)whenallof the Puppetagentwiththe following commandline; aretrue: {noformat} #The`$vardir/state/graphs`directorydoesn'texist MSIEXEC #The`graph`settingistrue#TheagenthasneverrunbeforeExecuting`puppetapply`willfailtowritethecatalog.OnWindows,weset`graph`totrue:https: / isource\ /github.com/puppetlabs/puppet_for_the_win/blob/master/wix/ puppet .wxs#L302 - L306.On*nix(PEonly),weset`graph`totrue:https://github.com/puppetlabs/ enterprise- dist/blob/ 3. 2. 3. msiPUPPET_AGENT_STARTUP_MODE=DisabledREBOOT=ReallySuppressALLUSERS=1 x / qb- ext / l*v erb/puppet.conf.erb#L52{noformat}$bundleexecpuppetapply-e c notice'foo'--graphNotice : \PuppetAgent Scope(Class[main]):fooNotice:Compiledcatalogforarcturus . Install luna . log laninenvironmentproductionin0.01seconds Error:Nosuchfileordirectory-/Users/josh/.puppet/var/state/graphs/resources.dot {noformat} ThenItriedtorunaPuppetApplywiththefollowingcommandline; OnWindows: {noformat}C:\ Windows work \ SysWOW64\cmd puppet[stable+1~0-0!]bundleexecpuppetapply-enotice'foo'--graph--traceNotice:Scope(Class[main]):fooNotice:Compiledcatalogforwin-qp47voha2p4 . exe solar.laninenvironmentproductionin0.05secondsError:Nosuchfileordirectory-C: / E ProgramData/PuppetLabs/puppet/var/state/graphs/resources.dotC : ON / work/puppet/lib/puppet/graph/simple_graph.rb:474:in`initialize' C :/work/puppet/lib/puppet/graph/simple_graph.rb:474:in`open' C: \ProgramFiles(x86)\PuppetLabs\PuppetEnterprise\bin\ /work/ puppet /lib/puppet/graph/simple_graph . bat rb:474:in`write_graph'C:/work/puppet/lib/puppet/resource/catalog.rb:448:in`write_graph'C:/work/puppet/lib/puppet/resource/catalog.rb:231:in`finalize'C:/work/puppet/lib/puppet/application/ apply --modulepath=%LOCALSRC%\modules%LOCALSRC%\manifests\site . pp rb:219:in`blockinmain' {noformat} C:/work/puppet/lib/puppet/context.rb:56:in`override' C:/work/puppet/lib/puppet.rb:234:in`override' Howeverireceivedanerrorthatitcouldnotcreatedresources C:/work/puppet/lib/puppet/application/apply . dot rb:190:in`main'C:/work/puppet/lib/puppet/application/apply . Itwastryingtocreateit rb:151: in {{ `run_command' C: \ProgramData\PuppetLabs\ /work/ puppet \var\state\graphs}}whichlooksliketheexpectedplace,howeverthedirectorystructurewasincomplete /lib/puppet/application . Only{{ rb:371:in`block(4levels)inrun' C: \ProgramData\PuppetLabs\ /work/ puppet \var}}existed /lib/puppet/application . IfImanuallycreatedthisdirectory rb:479:in`plugin_hook'C:/work/puppet/lib/puppet/application.rb:371:in`block ( MD{{ 3levels)inrun' C: \ProgramData\PuppetLabs\ /work/ puppet \var\state\graphs}} /lib/puppet/util.rb:479:in`exit_on_fail'C:/work/puppet/lib/puppet/application.rb:371:in`block(2levels ) andthenranPuppetApplyitexecutedfine inrun'C:/work/puppet/lib/puppet/context . rb:56:in`override' C:/work/puppet/lib/puppet.rb:234:in`override' Itseemslike
Jira (FACT-470) Create a fact with a list of all zones
Title: Message Title Lindsey Smith PO created an issue Facter / FACT-470 Create a fact with a list of all zones Issue Type: Improvement Assignee: Eric Sorenson Created: 28/Apr/14 11:47 AM Labels: facter Priority: Normal Reporter: Lindsey Smith PO From a customer: Facter provides a wealth of zone information (below). Unfortunately, there is no fact which lists all zones, so we've had to result to a bit of ugliness in our Puppet manifest . FWIW, there is already precedent for this sort of fact, if you consider the interfaces fact. facter -p | grep '^zone' zone_global_brand = solaris zone_global_id = 0 zone_global_iptype = shared zone_global_name = global zone_global_path = / zone_global_status = running zone_examplehostname_brand = solaris zone_examplehostname_id = - zone_examplehostname_iptype = excl zone_examplehostname_name = examplehostname zone_examplehostname_path = /zones/examplehostname/zonepath zone_examplehostname_status = configured zonename = global zones = 2
Jira (PDB-182) Document backup and restoration advice
Title: Message Title
Lindsey Smith PO commented on an issue
Re: Document backup and restoration advice
Who owns this? Asking Mike Hall, assuming this is a docs task.
Add Comment
PuppetDB / PDB-182
Document backup and restoration advice
We always get asked about how to backup PuppetDB, we probably should write a formal doc. From notes after discussion with @glarizza, the following could be used for Postgres: {noformat} pg_dump -Z 9 -Fc puppetdb /tmp/backup.dump pg_restore -c --jobs=2 -Fc -d puppetdb /tmp/backup.dump {noformat} (be mindful this will not backup/restore the `p...
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-565) Support trusted facts in PuppetDB fact storage
Title: Message Title Lindsey Smith PO commented on an issue Re: Support trusted facts in PuppetDB fact storage Kenneth Barber If I understand correctly, until trusted facts are in PuppetDB then the NC service cannot make decisions based on them. And the same would be true when, eventually, structured facts were available to Puppet. Add Comment PuppetDB / PDB-565 Support trusted facts in PuppetDB fact storage Since Puppet 3.4, we've added a new top-scope, immutable hash called 'trusted' which is exposed in the DSL and populated with the authenticated certname from the SSL certificate that made the catalog request. In addition, custom attributes can be added to the certificate and will also show up in the trusted hash (see http://docs.puppetlabs.com/puppet/late... 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-389) Support ruby 2.0 x64 on windows
Title: Message Title
Lindsey Smith PO updated an issue
Puppet / PUP-389
Support ruby 2.0 x64 on windows
Change By:
Lindsey Smith PO
Rubyx64buildshavebeenavailableasofruby2.0,andthewin32gemcommunityiscatchingup.Itisimportanttosupportpuppetonx64,becauseiteliminatesthefilesystemredirectionnonsensethatcustomershavetodealwithwhenwritingmanifestsandmodulesonWindows. FromMonsanto:{quote}Thebigissuesarebeingabletoaccessthe64-bitareasoftheregistryandfilesystem.Whenrunninga32-bitagent,Windowswillbydefaultredirect:Registry“HKEY_LOCAL_MACHINE\SOFTWARE”to“HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node”Filesystem“C:\Windows\System32”to“C:\windows\SysWOW64”Thatmeanstherearedifficultiestryingaccessregistrysettingsfrom“HKEY_LOCAL_MACHINE\SOFTWARE”andfilesfrom“C:\Windows\System32”unlessitisa64-bitagent.Examples:Filecheck:HowdoIchecktheversionoffileC:\windows\system32\qmgr.dllona64-bitWindowsserverScriptLaunch:Launchingpowershell.exefroma32-bitprocessrunsthe32-bitversionofPowerShellwhichwouldalsohavetheredirectiongoingon.HowdoIlauncha64-bitpowershell.exeprocesssoitcanaccessthefullregistryandfilesystemfromthatPowerShellprocess.Facter:Iwastryingtoaddfactsforotheragentsinourenvironmentthatare64-biton64-bitserversand32-biton32-bitservers.ThisnormallyrequiresreadingregistrysettingsfromkeyssuchasHKLM\Software\Vendor\Product(thenativeHKLM\Softwareportionoftheregistry).IthinkIfinallygotthistoworkafterfishingthroughrubyscriptsuntilIfoundsomethingthatwashelpful.Butmysolutionwascompletelyundocumented,andrequiredmetojumpthroughhoopsthatwouldnotexistiftheagentwere64-bit.AlthoughIfoundasolutionforfacter,registryredirectionwillbeabigproblemforpowershellscriptsiftheyarealwaysoperatingina32-bitenvironment.{quote}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1210) authentication_authority key is not set when managing root's password using the puppet user provider
Title: Message Title Lindsey Smith PO updated an issue Puppet / PUP-1210 authentication_authority key is not set when managing root's password using the puppet user provider Change By: Lindsey Smith PO 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/groups/opt_out.
Jira (PUP-1210) authentication_authority key is not set when managing root's password using the puppet user provider
Title: Message Title Lindsey Smith PO updated an issue Puppet / PUP-1210 authentication_authority key is not set when managing root's password using the puppet user provider Change By: Lindsey Smith PO Component/s: PE 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/groups/opt_out.
