Jira (PDB-4256) Installing with PuppetDB module creates dependency cycle with latest apt module
Title: Message Title Helen Campbell commented on PDB-4256 Re: Installing with PuppetDB module creates dependency cycle with latest apt module Hey everyone, I've made a fix which I was able to test out using Austins environment he provided (thanks Austin!). The release with the fix is now out and Postgresql 5.12.0 should work for you, would someone be able to confirm this and close out these tickets if so? Don't want to resolve anything until I know it's fixed on your side, thanks! 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Helen Campbell commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 So this issue seems to crop up every once in a while, and similarly to those occasions within a few days of us seeing these errors they go away. This bug currently cannot be reproduced, and we are not entirely sure how to reproduce it. The closest guess to reproduce would be to keep an eye out after stdlib or apt is released, though we would have quite a short amount of time in which to diagnose the problem, and thats if we can actually reproduce it. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6470) EPP - Syntax error raised in wrong location after attempting .empty? in template
Title: Message Title
Helen Campbell created an issue
Puppet / PUP-6470
EPP - Syntax error raised in wrong location after attempting .empty? in template
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/07/04 7:33 AM
Environment:
Puppet 4.2.0
Priority:
Minor
Reporter:
Helen Campbell
When attempting to translate a .erb file to a .epp file for the ntp module I ran into a syntax error on a specific line while running epp validate. As can be seen below, the syntax error claims to be at line 3, and is complaining about a '['. But what is actually apparent, is that the syntax error should be two lines before, at the attempted use of '.empty?'.
Error: ➜ puppetlabs-ntp git:(factsUpdate) ✗ puppet epp validate templates/tmp.epp Error: Syntax error at '[' at templates/tmp.epp:3:4 Error: Errors while validating epp Error: Try 'puppet help epp validate' for usage
EPP Code:
1 <% unless $peers.empty? {-%>
2 # Peers
Jira (PUP-5686) The addition of the output of "systemctl status (service)" in reports
Title: Message Title Helen Campbell created an issue Puppet / PUP-5686 The addition of the output of "systemctl status (service)" in reports Issue Type: Improvement Assignee: Unassigned Created: 2016/01/11 6:48 AM Environment: redhat-7-x86_64-master - sles-12-x86_64-agent - full PE 3.8 Priority: Normal Reporter: Helen Campbell When running module tests on Jenkins a couple of times I've had to investigate the following failure: Error: /Stage[main]/Ntp::Service/Service[ntp]: Failed to call refresh: Could not restart Service[ntp]: Execution of '/usr/bin/systemctl restart ntpd' returned 1: Job for ntpd.service failed. See "systemctl status ntpd.service" and "journalctl -xn" for details. Instead of simply having "See systemctl status ntpd.service for details" it would benefit the customer, and the modules team, for the output of this command to be available in the report. Especially since it is often the case the testing environment no
