Jira (FACT-1387) Google Cloud instances are not recognised as virtual on Windows
Title: Message Title Lee Packham created an issue Facter / FACT-1387 Google Cloud instances are not recognised as virtual on Windows Issue Type: Bug Assignee: Unassigned Created: 2016/04/08 11:56 PM Priority: Normal Reporter: Lee Packham As per title. Launch a windows VM in Google and run facter it'll claim it's a physical machine. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-4503) systemd should be the default for Debian Jessie
Title: Message Title Lee Packham commented on PUP-4503 Re: systemd should be the default for Debian Jessie Any service that has a systemd AND sysvinit profile. So, Docker is a good example. 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-4503) systemd should be the default for Debian Jessie
Title: Message Title Lee Packham created an issue Puppet / PUP-4503 systemd should be the default for Debian Jessie Issue Type: Bug Assignee: Unassigned Created: 2015/04/30 9:25 AM Priority: Normal Reporter: Lee Packham There is, unfortunately, a bug in systemd on Debian Jessie where older sysvinit scripts can't detect the enabled status. Therefore you should not just enable that as the default. I wrote a version of a provider based on systemd that can check enabled via both systemd AND sysvinit and then the enable/disable in systemd does the right thing. https://gist.github.com/leepa/9818b46b29b161413824 This is a bug because Puppet 3.7.5 does not work correctly at all on Debian Jessie because of this. Add Comment
Jira (PUP-1635) "current thread not owner" after Puppet Agent receives USR1 signal
Title: Message Title Lee Packham commented on PUP-1635 Re: "current thread not owner" after Puppet Agent receives USR1 signal I'm running this version of lib/puppet/daemon.rb (which I cobbled together based on the issue and how it's best to get out of the context of the trap). https://gist.github.com/leepa/bf5ab312fbdb94750f49 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
