Jira (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Tim Meusel commented on PUP-3483 Re: Systemd provider doesn't scan for changed units I had the same thoughts as Tom, we currently run into several issues because every module defines their own exec. We need a global solution to trigger a systemd daemon-reload, but I'm not sure if a simple module that defines the exec is the best solution (but I also can't think of something better). Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5343) Triage Solaris 11 failures
Title: Message Title
John Duarte commented on PUP-5343
Re: Triage Solaris 11 failures
I am presuming that most of the failures above are the result of running the test suite against a zone instance. Commands like the following simply fail in this environment.
root@beaker-sol11:~# zpool create tstpool /ztstpool/dsk
Unable to build pool from specified devices: cannot open '/ztstpool/dsk': No such file or directory
...
root@beaker-sol11:~# /opt/puppetlabs/bin/puppet apply -e "zone {tstzone : ensure=>running, path=>'/tstzones/mnt', }"
Notice: Compiled catalog for beaker-sol11.delivery.puppetlabs.net in environment production in 0.97 seconds
Error: Failed to apply configuration
Error: /Stage[main]/Main/Zone[tstzone]/ensure: change from absent to running failed: Failed to apply configuration
Notice: Applied catalog in 0.20 seconds
I will re-run this suite on the LDOM instance of Solaris 11 SPARC to confirm when OPS has granted me access to it.
Jira (PDB-2034) schema error on replace facts insert-facts-pv-pairs!
Title: Message Title Josh Behrends commented on PDB-2034 Re: schema error on replace facts insert-facts-pv-pairs! Heh, yup we are now in a good state now. Just commented here to make sure you guys knew the symptoms I found, and that this was happening in puppetdb v3.1 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 (PDB-2034) schema error on replace facts insert-facts-pv-pairs!
Title: Message Title Wyatt Alt commented on PDB-2034 Re: schema error on replace facts insert-facts-pv-pairs! Josh Behrends yes, thanks for chiming in. To bring you up to speed with the status of this, I've found four cases so far where you'll encounter this issue, each with a distinct cause but apparently similar: an escape-quoted fact name a fact name that begins with an escaped quote (this case spurred the ticket) a fact name containing the string "#~" somewhere other than the end a fact name ending with the string "#~" I've got a fix that covers the first three cases, and I'm hoping to nail the fourth down tomorrow. If you'd be willing to send me one of the failed replace-facts commands in your dead letter directory (/opt/puppetlabs/server/data/puppetdb/mq/localhost/discarded/replace-facts) I can either confirm that it's a known case, or identify another cause. My email is wy...@puppetlabs.com – if you're willing, I'd recommend sending it there rather than attaching it to this public ticket. Wyatt Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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
Jira (PUP-5352) PMT progress display
Title: Message Title Geoff Williams created an issue Puppet / PUP-5352 PMT progress display Issue Type: Improvement Assignee: Eric Sorenson Components: PMT, UX Created: 2015/10/11 10:25 PM Priority: Normal Reporter: Geoff Williams Unless PMT is run in debug mode, there is no visible indication as to whether it is encountering network problems (eg proxy server) or is simply downloading a large module or lots of dependencies. The current behaviour can leave users chasing non-existing problems (eg network working but slow) or can leave users with an unexpected failure several minutes after starting the command (eg network timeout due to proxy). It would be great if PMT could give the user an indication of what it is currently doing as sometimes downloading modules can take several minutes unless invoked with the `--debug` option. Add Comment
Jira (PDB-2034) schema error on replace facts insert-facts-pv-pairs!
Title: Message Title Wyatt Alt commented on PDB-2034 Re: schema error on replace facts insert-facts-pv-pairs! Ok good to hear, and thanks again. We'll get the fix in in the next few days and put it out in the next release. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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.
