Jira (PUP-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Josh Cooper commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run Merged to master in https://github.com/puppetlabs/puppet/commit/4f448a3e3149b9d0ce7fae6d4eac0fb5d6cb0074. This will be backported to 5.5.x in a future PR. 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.117656.1455921098000.29751.1573616940718%40Atlassian.JIRA.
Jira (PUP-9994) External/Extended trusted data
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9994 External/Extended trusted data Change By: Josh Cooper Assignee: David Schmitt Josh Cooper 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.323248.1567522563000.29686.1573609260391%40Atlassian.JIRA.
Jira (PUP-10040) Convert ssl state machine and application to using http client
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10040 Convert ssl state machine and application to using http client Change By: Josh Cooper Release Notes Summary: Modifies the "puppet ssl", "puppet device" and "puppet agent" applications to use the new http client in puppet to bootstrap SSL certificates on the node. Release Notes: Enhancement 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.326145.1569368598000.29678.1573609260354%40Atlassian.JIRA.
Jira (PUP-9994) External/Extended trusted data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9994 External/Extended trusted data Change By: Josh Cooper Team: Coremunity 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.323248.1567522563000.29684.1573609260384%40Atlassian.JIRA.
Jira (PUP-10037) Add CA HTTP service
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10037 Add CA HTTP service Change By: Josh Cooper Release Notes Summary: This feature isn't activated yet, so no user facing changes. 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.326128.156936681.29673.1573609140049%40Atlassian.JIRA.
Jira (PUP-10033) Implement basic HTTP client
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10033 Implement basic HTTP client Change By: Josh Cooper Release Notes Summary: This feature isn't activated yet, so no user facing changes. 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.326121.156936547.29672.1573609080146%40Atlassian.JIRA.
Jira (PUP-10033) Implement basic HTTP client
Title: Message Title Kris Bosland commented on PUP-10033 Re: Implement basic HTTP client Merged to master at https://github.com/puppetlabs/puppet/commit/5405b2f176712d19da4c58ec3a70e758b864bae1 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.326121.156936547.29667.1573608720171%40Atlassian.JIRA.
Jira (PUP-9186) Deferred doesn't work in 'notify' resource
Title: Message Title Ben Ford commented on PUP-9186 Re: Deferred doesn't work in 'notify' resource Henrik Lindberg before I re-open or open a new ticket, is there work towards making client side templates easier to do? It's a very similar problem, and I solved it the same way you did above, but Eric Sorenson thought that it was a dirty approach. 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.278010.1538087632000.29593.1573606500449%40Atlassian.JIRA.
Jira (PUP-9994) External/Extended trusted data
Title: Message Title Josh Cooper commented on PUP-9994 Re: External/Extended trusted data Thomas Honey I think we do want to document this experimental feature in the release notes, yeah? /cc Jean Bond 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.323248.1567522563000.29578.1573606020368%40Atlassian.JIRA.
Jira (PUP-10121) Could not request certificate
Title: Message Title Melissa Stone commented on PUP-10121 Re: Could not request certificate In progress since I need to backport these changes to the 5.5.x branch 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.333915.1573136473000.29549.1573605120115%40Atlassian.JIRA.
Jira (PUP-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5934 Updated fact values should be submitted after each Puppet run Change By: Josh Cooper Sprint: Platform Core KANBAN 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.117656.1455921098000.29446.1573603081562%40Atlassian.JIRA.
Jira (PUP-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-5934 Updated fact values should be submitted after each Puppet run Change By: Josh Cooper Assignee: Josh Cooper 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.117656.1455921098000.29448.1573603081581%40Atlassian.JIRA.
Jira (PUP-10137) HTTP Retry after 408 request timeout or 504 gateway timeout
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10137 HTTP Retry after 408 request timeout or 504 gateway timeout Change By: Josh Cooper HTTP 408 says the server should close the connection and the client should make a new connection and retry on that. But I don't see any mention of an `Retry-After` header. https://tools.ietf.org/html/rfc7231#section-6.5.7Similarly HTTP 504 doesn't mention that header. https://tools.ietf.org/html/rfc7231#section-6.6.5It also looks like `Retry-After` can be included in any 3xx response: https://tools.ietf.org/html/rfc7231#section-7.1.3 but our http code assumes they are exclusive. 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-10137) HTTP Retry after 408 request timeout or 504 gateway timeout
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10137 HTTP Retry after 408 request timeout or 504 gateway timeout Change By: Josh Cooper Team: Coremunity 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.334641.1573589453000.29293.1573601340166%40Atlassian.JIRA.
Jira (PUP-10121) Could not request certificate
Title: Message Title Josh Cooper commented on PUP-10121 Re: Could not request certificate Merged to master in https://github.com/puppetlabs/puppet/commit/52060634192e98199e0e4de4c0dac7b7960d3567 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.333915.1573136473000.29290.1573600620124%40Atlassian.JIRA.
Jira (PUP-9994) External/Extended trusted data
Title: Message Title Kris Bosland commented on PUP-9994 Re: External/Extended trusted data Merged to master in https://github.com/puppetlabs/puppet/commit/43abd2d4fc03b0ef0eee6e845ff70e4dd63151f3 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.323248.1567522563000.29276.1573598700200%40Atlassian.JIRA.
Jira (PUP-10135) Have a command to stop and start all puppet services
Title: Message Title Joshua Partlow commented on PUP-10135 Re: Have a command to stop and start all puppet services Ah, sorry, didn't see this. We could add an action to puppet-infra, and/or possibly a bolt plan. I'll switch this to the PE project and it'll flow into our backlog, though I'm not certain what priority it will end up with. The installer uses [pe_install::upgrade::stop_services|https://github.com/puppetlabs/puppet-enterprise-modules/blob/master/modules/pe_install/manifests/upgrade/stop_services.pp]. 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.334488.1573557533000.28991.1573589640225%40Atlassian.JIRA.
Jira (PUP-10137) HTTP Retry after 408 request timeout or 504 gateway timeout
Title: Message Title Josh Cooper created an issue Puppet / PUP-10137 HTTP Retry after 408 request timeout or 504 gateway timeout Issue Type: Bug Assignee: Unassigned Created: 2019/11/12 12:10 PM Priority: Normal Reporter: Josh Cooper HTTP 408 says the server should close the connection and the client should make a new connection and retry on that. But I don't see any mention of an `Retry-After` header. https://tools.ietf.org/html/rfc7231#section-6.5.7 Similarly HTTP 504 doesn't mention that header. https://tools.ietf.org/html/rfc7231#section-6.6.5 It also looks like `Retry-After` can be included in any 3xx response: https://tools.ietf.org/html/rfc7231#section-7.1.3 Add Comment This message was
Jira (PUP-10135) Have a command to stop and start all puppet services
Title: Message Title Josh Cooper commented on PUP-10135 Re: Have a command to stop and start all puppet services Thoughts Joshua Partlow? 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.334488.1573557533000.28949.1573588320248%40Atlassian.JIRA.
Jira (PUP-10135) Have a command to stop and start all puppet services
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10135 Have a command to stop and start all puppet services Change By: Josh Cooper Team: InfraCore Installer and Management 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.334488.1573557533000.28951.1573588320278%40Atlassian.JIRA.
Jira (PUP-10135) Have a command to stop and start all puppet services
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10135
Have a command to stop and start all puppet services
Change By:
Josh Cooper
Hi Guys, Would it be possible to have a command baked into PE that can be run to stop, start and restart all puppet services in the correct order ie puppet infra run stopservices , startservices, restartservices? This would mean we would not need to ask customers to run several commands to stop and start all services related to puppet.I put something together with a rough idea of how I could achieve this but it would need a touch from the pros!I was thinking something like the following would work, but it may need some more logic to handle mcollective and pe-activemq... ``` {code:bash} #!/bin/bash declare -a arrPuppetServiceStop=("puppet" "pe-puppetserver" "pe-activemq" "mcollective" "pe-puppetdb" "pe-console-services" "pe-nginx" "pe-orchestration-services") declare -a arrPuppetServiceStart=("pe-postgresql" "pe-puppetserver" "pe-activemq" "mcollective" "pe-puppetdb" "pe-console-services" "pe-nginx" "pe-orchestration-services" "puppet") function puppetstop(){ servicesarr=("$@") for service in ${servicesarr[@]} do echo "Attempting to stop $service" puppet resource service $service ensure=stopped done } function puppetstart(){ servicesarr=("$@") for service in ${servicesarr[@]} do echo "Attempting to start $service" puppet resource service $service ensure=running done } function puppetstatuscheck(){ servicesarr=("$@") status=("$1") for service in ${servicesarr[@]} do echo "Checking status of $service" puppet resource service pe-puppetserver | grep ensure | sed -e 's|[",'\'']||g' | awk ' \ {split($0,s," "); print s[3];}' done } state="$1" echo $state case "$state" in stop) echo "Trigger Stop action" puppetstop "${arrPuppetServiceStop[@]}" ;; start) echo "Trigger Start Action" puppetstart "${arrPuppetServiceStart[@]}" ;; check) echo "checking" puppetstatuscheck "${arrPuppetServiceStop[@]}" ;; *) echo "Only accepts Stop and Start" exit 1 esac {code} ```
Jira (PDB-4587) docs: clarify connect Puppet master page
Title: Message Title Jean Bond updated an issue PuppetDB / PDB-4587 docs: clarify connect Puppet master page Change By: Jean Bond Summary: [ docs issue] : clarify connect Puppet master page 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.334513.1573567979000.28536.1573578900188%40Atlassian.JIRA.
Jira (PDB-4587) [docs issue]
Title: Message Title Jean Bond moved an issue PuppetDB / PDB-4587 [docs issue] Change By: Jean Bond Method Found: Needs Assessment Scrum Team: PuppetDB Team: PuppetDB Component/s: installer Component/s: DOCS Workflow: Documentation Scrum Team Workflow Key: DOCUMENT PDB - 1053 4587 Project: Documentation PuppetDB Add Comment
Jira (PUP-10097) Protect against binary diffs
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10097 Protect against binary diffs Change By: Mihai Buzgau Sprint: PR - Triage 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.328673.1570644934000.28204.1573572240411%40Atlassian.JIRA.
Jira (FACT-2118) Implement hyper-V fact for Windows
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2118 Implement hyper-V fact for Windows Issue Type: Task Assignee: Oana Tanasoiu Created: 2019/11/12 5:50 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-10136) premature loading of module-provided facts under `-p`
Title: Message Title Dorin Pleava moved an issue Puppet / PUP-10136 premature loading of module-provided facts under `-p` Change By: Dorin Pleava Affects Version/s: FACT 3.13.2 Affects Version/s: PUP 6.4.0 Affects Version/s: PUP 6.10.1 Key: FACT PUP - 2059 10136 Project: Facter Puppet Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed
Jira (PUP-10135) Have a command to stop and start all puppet services
Title: Message Title
Jason Stewart created an issue
Puppet / PUP-10135
Have a command to stop and start all puppet services
Issue Type:
Improvement
Assignee:
Unassigned
Attachments:
stopstartexample.rtf
Created:
2019/11/12 3:18 AM
Priority:
Normal
Reporter:
Jason Stewart
Hi Guys, Would it be possible to have a command baked into PE that can be run to stop, start and restart all puppet services in the correct order ie puppet infra run stopservices , startservices, restartservices? This would mean we would not need to ask customers to run several commands to stop and start all services related to puppet. I put something together with a rough idea of how I could achieve this but it would need a touch from the pros! I was thinking something like the following would work, but it may need some more logic to handle mcollective and pe-activemq... ``` #!/bin/bash declare -a arrPuppetServiceStop=("puppet" "pe-puppetserver" "pe-activemq" "mcollective" "pe-puppetdb" "pe-console-services" "pe-nginx" "pe-orchestration-services") declare -a arrPuppetServiceStart=("pe-postgresql" "pe-puppetserver" "pe-activemq" "mcollective" "pe-puppetdb" "pe-console-services" "pe-nginx" "pe-orchestration-services" "puppet") function puppetstop(){ servicesarr=("$@") for service in ${servicesarr[@]} do echo "Attempting to stop $service" puppet resource service $service ensure=stopped done } function puppetstart(){ servicesarr=("$@") for service in ${servicesarr[@]} do echo "Attempting to start $service" puppet resource service $service ensure=running done } function puppetstatuscheck(){ servicesarr=("$@") status=("$1") for service in ${servicesarr[@]} do echo "Checking status of $service" puppet resource service pe-puppetserver | grep ensure | sed -e 's|[",'\'']||g' | awk '{split($0,s," "); print s[3];}' done } state="$1" case "$state" in stop)
Jira (FACT-2117) Implement filesystems facts for fedora
Title: Message Title Gheorghe Campean created an issue Facter / FACT-2117 Implement filesystems facts for fedora Issue Type: Task Assignee: Gheorghe Campean Created: 2019/11/12 1:37 AM Priority: Normal Reporter: Gheorghe Campean 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-2116) Implement dmi facts for fedora
Title: Message Title Gheorghe Campean created an issue Facter / FACT-2116 Implement dmi facts for fedora Issue Type: Task Assignee: Gheorghe Campean Created: 2019/11/12 1:33 AM Priority: Normal Reporter: Gheorghe Campean 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
