Jira (PDB-4974) Wait on schedulers to shut down
Title: Message Title Issue Updates updated an issue PuppetDB / PDB-4974 Wait on schedulers to shut down Address not found ** Your message wasn't delivered to wy...@puppet.com because the address couldn't be found, or is unable to receive mail. Learn more here: https://support.google.com/mail/?p=NoSuchUser The response was: 550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser o8sor1623465plk.56 - gsmtp - Message truncated - Change By: Issue Updates Attachment: icon.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4986) Instrument pdb to capture details when sync or shutdown hangs
Title: Message Title Issue Updates updated an issue PuppetDB / PDB-4986 Instrument pdb to capture details when sync or shutdown hangs Address not found ** Your message wasn't delivered to wy...@puppet.com because the address couldn't be found, or is unable to receive mail. Learn more here: https://support.google.com/mail/?p=NoSuchUser The response was: 550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser y3sor926215plk.71 - gsmtp - Message truncated - Change By: Issue Updates Attachment: icon.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4986) Instrument pdb to capture details when sync or shutdown hangs
Title: Message Title Issue Updates updated an issue PuppetDB / PDB-4986 Instrument pdb to capture details when sync or shutdown hangs Address not found ** Your message wasn't delivered to k...@puppet.com because the address couldn't be found, or is unable to receive mail. Learn more here: https://support.google.com/mail/?p=NoSuchUser The response was: 550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser g8sor1464038pgg.50 - gsmtp - Message truncated - Change By: Issue Updates Attachment: icon.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4974) Wait on schedulers to shut down
Title: Message Title Issue Updates updated an issue PuppetDB / PDB-4974 Wait on schedulers to shut down Address not found ** Your message wasn't delivered to k...@puppet.com because the address couldn't be found, or is unable to receive mail. Learn more here: https://support.google.com/mail/?p=NoSuchUser The response was: 550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser j205sor1292587pfd.41 - gsmtp - Message truncated - Change By: Issue Updates Attachment: icon.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4989) puppetdb : raises deprecation warning The method 'Puppet::Network::HttpPool.http_instance' is deprecated. Use Puppet.runtime[:http] instead
Title: Message Title Issue Updates updated an issue PuppetDB / PDB-4989 puppetdb : raises deprecation warning The method 'Puppet::Network::HttpPool.http_instance' is deprecated. Use Puppet.runtime[:http] instead Address not found ** Your message wasn't delivered to wy...@puppet.com because the address couldn't be found, or is unable to receive mail. Learn more here: https://support.google.com/mail/?p=NoSuchUser The response was: 550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser h5sor19069pfq.50 - gsmtp - Message truncated - Change By: Issue Updates Attachment: icon.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4989) puppetdb : raises deprecation warning The method 'Puppet::Network::HttpPool.http_instance' is deprecated. Use Puppet.runtime[:http] instead
Title: Message Title Issue Updates updated an issue PuppetDB / PDB-4989 puppetdb : raises deprecation warning The method 'Puppet::Network::HttpPool.http_instance' is deprecated. Use Puppet.runtime[:http] instead Address not found ** Your message wasn't delivered to k...@puppet.com because the address couldn't be found, or is unable to receive mail. Learn more here: https://support.google.com/mail/?p=NoSuchUser The response was: 550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser j5sor115789pld.57 - gsmtp - Message truncated - Change By: Issue Updates Attachment: icon.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
<<< text/html; charset="UTF-8": Unrecognized >>>
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
<<< text/html; charset="UTF-8": Unrecognized >>>
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
<<< text/html; charset="UTF-8": Unrecognized >>>
Jira (PUP-4530) FreeBSD specific Service provider fix
Title: Message Title Issue Updates updated an issue Puppet / PUP-4530 FreeBSD specific Service provider fix Done. Cheers, Matthew Change By: Issue Updates Attachment: signature.asc Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-850) Puppet 3.x Deprecations in Preparation for Puppet 4
Title: Message Title Issue Updates commented on an issue Re: Puppet 3.x Deprecations in Preparation for Puppet 4 Kylo Ginsberg updated an issue [1]Puppet / [2][3]PUP-850 [4]Puppet 3.x Deprecations in Preparation for Puppet 4 Change By: [5]Kylo Ginsberg Epic Status: ToDo Done [6] [7]Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) [1] https://tickets.puppetlabs.com/browse/PUP [2] https://tickets.puppetlabs.com/browse/PUP-850 [3] https://tickets.puppetlabs.com/browse/PUP-850 [4] https://tickets.puppetlabs.com/browse/PUP-850 [5] https://tickets.puppetlabs.com/secure/ViewProfile.jspa?name=kylo [6] https://tickets.puppetlabs.com/browse/PUP-850#add-comment [7] https://tickets.puppetlabs.com/browse/PUP-850#add-comment Add Comment Puppet / PUP-850 Puppet 3.x Deprecations in Preparation for Puppet 4 In order to get ready for removing unused or unwanted functionality in Puppet 4 we need to issue deprecation warnings in a puppet 3.x release. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
