Jira (FACT-2267) Implement NilFact to solve the no fact found issue
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2267
Implement NilFact to solve the no fact found issue
Change By:
Bogdan Irimie
Right now cfacter outputs {code:java} ``` cfacter abc cdeabc =>cde => {code} ``` and facter NG does not output anything {code:java} ``` ./bin/facter-ng abc cde ``` {code}If we create a NillFact that will return nil for any fact that is not found, we can implement the same behaviour as cfacter with minimum changes (probably only in QueryParser)
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341632.1578642875000.19011.1578643140046%40Atlassian.JIRA.
Jira (FACT-2267) Implement NilFact to solve the no fact found issue
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2267 Implement NilFact to solve the no fact found issue Change By: Bogdan Irimie Right now cfacter outputs ```cfacter abc cdeabc =>cde =>``` and facter NG ```./bin/facter-ng abc cde``` Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341632.1578642875000.19008.1578643020092%40Atlassian.JIRA.
Jira (FACT-2267) Implement NilFact to solve the no fact found issue
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2267 Implement NilFact to solve the no fact found issue Issue Type: Task Assignee: Unassigned Created: 2020/01/09 11:54 PM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2266) Implement catch exception mechanism in all resolvers
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2266 Implement catch exception mechanism in all resolvers Change By: Bogdan Irimie Team: Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341631.157864270.19005.1578642780055%40Atlassian.JIRA.
Jira (FACT-2266) Implement catch exception mechanism in all resolvers
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2266 Implement catch exception mechanism in all resolvers Issue Type: Task Assignee: Unassigned Created: 2020/01/09 11:51 PM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2266) Implement catch exception mechanism in all resolvers
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2266 Implement catch exception mechanism in all resolvers Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341631.157864270.19003.1578642720206%40Atlassian.JIRA.
Jira (PUP-10229) Puppet 6 (agent) is noticeably slower on Windows than Puppet 5
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-10229 Puppet 6 (agent) is noticeably slower on Windows than Puppet 5 Change By: Glenn Sarti Attachment: puppet6-slow1.gif Attachment: puppet6-slow2.gif Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341629.1578624899000.18983.1578625020093%40Atlassian.JIRA.
Jira (PUP-10229) Puppet 6 (agent) is noticeably slower on Windows than Puppet 5
Title: Message Title Glenn Sarti commented on PUP-10229 Re: Puppet 6 (agent) is noticeably slower on Windows than Puppet 5 Ruby versions used 2.4.3-2-x64 : ruby 2.4.3p205 (2017-12-14 revision 61247) [x64-mingw32] 2.5.1-2-x64 : ruby 2.5.1p57 (2018-03-29 revision 63029) [x64-mingw32] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341629.1578624899000.18984.1578625020144%40Atlassian.JIRA.
Jira (PUP-10229) Puppet 6 is noticeably slower on Windows than Puppet 5
Title: Message Title Glenn Sarti created an issue Puppet / PUP-10229 Puppet 6 is noticeably slower on Windows than Puppet 5 Issue Type: Bug Assignee: Unassigned Created: 2020/01/09 6:54 PM Priority: Normal Reporter: Glenn Sarti Puppet Version: 6.11.1, 5.x Puppet Server Version: N/A OS Name/Version: Windows 10 1903 Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: When running seemingly simple CLI tasks like --version Puppet 6 and Puppet 5 should be fast and have similar response times Actual Behavior: Puppet 6 is significantly slower I've attached screen casts Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10229) Puppet 6 (agent) is noticeably slower on Windows than Puppet 5
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-10229 Puppet 6 (agent) is noticeably slower on Windows than Puppet 5 Change By: Glenn Sarti Summary: Puppet 6 (agent) is noticeably slower on Windows than Puppet 5 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341629.1578624899000.18982.1578624960218%40Atlassian.JIRA.
Jira (PUP-9932) [SPIKE] Can we make 3x functions loaders thread-safe?
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9932 [SPIKE] Can we make 3x functions loaders thread-safe? Change By: Maggie Dreyer need details We should investigate what it would take to make the 3x function loaders threadsafe, and then decide whether or not it's worth it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306743.1556579117000.18931.1578615960215%40Atlassian.JIRA.
Jira (PUP-9932) [SPIKE] Can we make 3x functions loaders thread-safe?
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9932 [SPIKE] Can we make 3x functions loaders thread-safe? Change By: Maggie Dreyer Summary: Make [SPIKE] Can we make 3x functions loaders thread-safe ? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306743.1556579117000.18926.1578615900196%40Atlassian.JIRA.
Jira (PDOC-294) Improve Type Alias Docs - Parameter Support
Title: Message Title Randell Pelak commented on PDOC-294 Re: Improve Type Alias Docs - Parameter Support I think you may have used the wrong template for this ticket... This template is for requesting a performance experiment. Let me know if I am wrong, otherwise I will clear out the stuff that is making this show up on SLV. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.329108.1570847885000.18913.1578614460183%40Atlassian.JIRA.
Jira (PDB-4094) Investigate query unexpectedly returning 500
Title: Message Title
Robert Roland commented on PDB-4094
Re: Investigate query unexpectedly returning 500
Okay cool - here's what happened when I ran it:
rroland@rroland-t470p:~$ curl -f -X POST http://localhost:8080/pdb/query/v4/nodes -H 'Content-Type:application/json' -d '{"query":["=","certname","unknowncertname"]}'
[]
rroland@rroland-t470p:~$ echo $?
0
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4094) Investigate query unexpectedly returning 500
Title: Message Title Justin Stoller commented on PDB-4094 Re: Investigate query unexpectedly returning 500 No idea if this is still an issue. Scott doesn't work here anymore, btw. I think the idea was that querying for the certname field with a value that would not match would return a 500 vs an empty result set. If you're saying that no longer causes a 500 then I'm happy to see this closed as "Cannot Reproduce". I don't know if the "a node that has submitted its cert but not had it signed yet" is applicable (I don't think fact or report submission happens until after a cert is acquired). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276170.153728876.18857.1578613140192%40Atlassian.JIRA.
Jira (PDB-4094) Investigate query unexpectedly returning 500
Title: Message Title Robert Roland commented on PDB-4094 Re: Investigate query unexpectedly returning 500 Wow, this has been open for a while. Scott Garman Justin Stoller - do you know if this still an issue? The query doesn't seem to 500 - but I don't have a lot of data to work with. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276170.153728876.18845.1578612480643%40Atlassian.JIRA.
Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances
Title: Message Title Ryan McKern commented on FACT-1903 Re: facter doesn't recognize EC2 i3.metal instances Also, y'all saw that this sat opened and unacknowledged for almost a year, right? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.291000.1547052341000.18786.1578610920239%40Atlassian.JIRA.
Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances
Title: Message Title Ryan McKern commented on FACT-1903 Re: facter doesn't recognize EC2 i3.metal instances Looks like the fix for us would be to roll forward then: mckern ~ $ dpkg -l | grep puppet ii puppet-agent1.8.3-1jessieamd64The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective. mckern ~ $ facter -v 3.5.1 (commit 4dd3423921c3e46906942fa76bebff7afbc1c0e7) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10222) Puppet lookup invocation recursion detection not thread-safe
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10222 Puppet lookup invocation recursion detection not thread-safe Change By: Maggie Dreyer Fix Version/s: PUP 6.12.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341337.157842233.18764.1578610140269%40Atlassian.JIRA.
Jira (PUP-10222) Puppet lookup invocation recursion detection not thread-safe
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10222 Puppet lookup invocation recursion detection not thread-safe Change By: Maggie Dreyer Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341337.157842233.18765.1578610140276%40Atlassian.JIRA.
Jira (PUP-10148) Include X-Puppet-Profiling header
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10148 Include X-Puppet-Profiling header Change By: Josh Cooper Release Notes: Enhancement Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335811.157412461.18747.1578609300516%40Atlassian.JIRA.
Jira (PUP-10038) Add Report HTTP service
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10038 Add Report HTTP service Change By: Josh Cooper Release Notes: Enhancement Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326131.1569367572000.18745.1578609300427%40Atlassian.JIRA.
Jira (PUP-10034) Implement DELETE, HEAD, POST
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10034 Implement DELETE, HEAD, POST Change By: Josh Cooper Release Notes: Enhancement Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326122.1569365544000.18743.1578609300215%40Atlassian.JIRA.
Jira (PUP-10145) Add Puppet HTTP service
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10145 Add Puppet HTTP service Change By: Josh Cooper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335806.1574123423000.18739.1578609240347%40Atlassian.JIRA.
Jira (PUP-10145) Add Puppet HTTP service
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10145 Add Puppet HTTP service Change By: Josh Cooper Fix Version/s: PUP 6.13.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335806.1574123423000.18736.1578609240214%40Atlassian.JIRA.
Jira (PUP-10163) Evaluate remaning singleton classes for thread safety
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10163 Evaluate remaning singleton classes for thread safety Change By: Maggie Dreyer Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338277.1575658473000.18505.1578600120123%40Atlassian.JIRA.
Jira (PUP-10163) Evaluate remaning singleton classes for thread safety
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10163 Evaluate remaning singleton classes for thread safety Change By: Maggie Dreyer Fix Version/s: PUP 6.12.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338277.1575658473000.18500.157860294%40Atlassian.JIRA.
Jira (PUP-10219) Unable to create local user when username already exists in Windows domain
Title: Message Title Josh Cooper commented on PUP-10219 Re: Unable to create local user when username already exists in Windows domain Passed 5.5.x CI in 342e48a9, 6.4.x CI in 0cef459424 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341094.157829589.18490.1578599820299%40Atlassian.JIRA.
Jira (PUP-10219) Unable to create local user when username already exists in Windows domain
Title: Message Title Josh Cooper commented on PUP-10219 Re: Unable to create local user when username already exists in Windows domain Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/342e48a94a4b8e095c652114e03187f3829cd657 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341094.157829589.18487.1578599760175%40Atlassian.JIRA.
Jira (PUP-10213) Do not create exceptions for stacktrace information when we know we won't use that information
Title: Message Title Josh Cooper commented on PUP-10213 Re: Do not create exceptions for stacktrace information when we know we won't use that information Passed 6.4.x CI in 0cef459424 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340907.1578000208000.18484.1578599700455%40Atlassian.JIRA.
Jira (PUP-10150) Ruby stacktraces no longer interleave Puppet Code stacktraces
Title: Message Title Josh Cooper commented on PUP-10150 Re: Ruby stacktraces no longer interleave Puppet Code stacktraces Passed 6.4.x CI in 0cef459424 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.336155.1574344871000.18481.1578599700251%40Atlassian.JIRA.
Jira (PUP-10228) Puppet 6 daemons do not release ssl_lockfile
Title: Message Title Josh Cooper commented on PUP-10228 Re: Puppet 6 daemons do not release ssl_lockfile Yeah, this was intentionally done this way as originally the state machine didn't start over from the very beginning, instead it just tried to generate the CSR and submit it each time. Later I realized that the ca cert/crl may have been wiped, so we now start over from the beginning https://github.com/puppetlabs/puppet/blob/605187329a42e200d011cbccfd9e79eb4de02145/lib/puppet/ssl/state_machine.rb#L283-L286 in which case it would be safe to release the lock before sleeping and try to reacquire after. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341497.1578522774000.18116.1578589860111%40Atlassian.JIRA.
Jira (PUP-10216) Failure to fetch node definition may result in bad pluginsync and cascading failure
Title: Message Title Josh Cooper commented on PUP-10216 Re: Failure to fetch node definition may result in bad pluginsync and cascading failure It would be possible to read the environment from the Puppet[:lastrunreport], but it would probably be better performance-wise to add the environment to the Puppet[:lastrunfile summary, and read that in instead. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341077.1578089491000.18111.1578589560143%40Atlassian.JIRA.
Jira (FACT-2265) Implement wildcard legacy facts
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2265 Implement wildcard legacy facts Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341536.1578577166000.17946.1578577200223%40Atlassian.JIRA.
Jira (FACT-2265) Implement wildcard legacy facts
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2265 Implement wildcard legacy facts Issue Type: Task Assignee: Unassigned Created: 2020/01/09 5:39 AM Priority: Normal Reporter: Oana Tanasoiu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PUP-10225) Puppetserver 6 performance regression
Title: Message Title Iain Buclaw updated an issue Puppet / PUP-10225 Puppetserver 6 performance regression Change By: Iain Buclaw Attachment: puppet5-breakdown.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341411.1578473781000.17890.1578572940255%40Atlassian.JIRA.
Jira (PUP-10225) Puppetserver 6 performance regression
Title: Message Title Iain Buclaw updated an issue Puppet / PUP-10225 Puppetserver 6 performance regression Change By: Iain Buclaw Attachment: puppet6-breakdown.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341411.1578473781000.17891.1578572940299%40Atlassian.JIRA.
Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-1903 facter doesn't recognize EC2 i3.metal instances Change By: Gabriel Nagy Attachment: facter.txt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.291000.1547052341000.17810.1578562560243%40Atlassian.JIRA.
Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances
Title: Message Title Gabriel Nagy commented on FACT-1903 Re: facter doesn't recognize EC2 i3.metal instances Tested this on a i3.metal instance with Debian Stretch with puppet-agent 6.11.1 and it works fine for me, see facter output: facter.txt # facter --version 3.14.6 (commit 47c91659d7220d0b5c536f7e5fb1a541c1f0d36c) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.291000.1547052341000.17812.1578562560331%40Atlassian.JIRA.
Jira (PUP-10219) Unable to create local user when username already exists in Windows domain
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-10219 Unable to create local user when username already exists in Windows domain Change By: Gabriel Nagy Release Notes Summary: When domain-joined and checking for a local account on Windows, ignore case on the domain/computer name comparison. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341094.157829589.17758.1578561480147%40Atlassian.JIRA.
Jira (PUP-10219) Unable to create local user when username already exists in Windows domain
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10219 Unable to create local user when username already exists in Windows domain Change By: Dorin Pleava Fix Version/s: PUP 6.12.0 Fix Version/s: PUP 6.4.5 Fix Version/s: PUP 5.5.18 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341094.157829589.17754.1578561000240%40Atlassian.JIRA.
Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-1903 facter doesn't recognize EC2 i3.metal instances Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.291000.1547052341000.17747.1578560760245%40Atlassian.JIRA.
Jira (PUP-10225) Puppetserver 6 performance regression
Title: Message Title Iain Buclaw commented on PUP-10225 Re: Puppetserver 6 performance regression If it's of any use, there are currently 222 servers being managed by this puppetserver, the agents are running once every 30 minutes. PuppetDB is present, as well Foreman. Looking at top, it's only the puppetserver process that is consuming high CPU resources. It's hard to tell, however puppet agent run times have increased between 25-50% across the board, for instance on one node it went from a pretty consistent 9 seconds config retrieval; 25 seconds runtime, to an erratic 8-14 seconds config retrieval, 28-50 seconds runtime. However that started occurring only after the agents were updated from version 5.5.17 to 6.11.1. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341411.1578473781000.17726.1578557880299%40Atlassian.JIRA.
Jira (PUP-10225) Puppetserver 6 performance regression
Title: Message Title Iain Buclaw updated an issue Puppet / PUP-10225 Puppetserver 6 performance regression Change By: Iain Buclaw Attachment: puppet-agent-runtimes.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341411.1578473781000.17725.1578557880255%40Atlassian.JIRA.
