Jira (PUP-11321) Warning: #
Title: Message Title Stefan commented on PUP-11321 Re: Warning: # We have a similar problem. Our yaml looks like this: our::variables: error_level: 0 intervals: 86400: older_than: number: 1 interval: 86400 keep_per: number: 1 interval: 604800 And we get this message: Warning: #0x5608a7a72eb0> ... contains a hash with an Integer key. It will be converted to the String '7'
Jira (PDB-4643) unable to connect puppetmaster with puppetdb
Title: Message Title Stefan commented on PDB-4643 Re: unable to connect puppetmaster with puppetdb FWIW, puppet lookup --node ... only works for me when -Djdk.tls.ephemeralDHKeySize=2048 is set, even with java-11. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.345012.1580837021000.102787.1594221720032%40Atlassian.JIRA.
Jira (PDB-4643) unable to connect puppetmaster with puppetdb
Title: Message Title Stefan commented on PDB-4643 Re: unable to connect puppetmaster with puppetdb FWIW switching to java 11 solved the problem for me: dnf install java-11-openjdk-headless update-alternatives --config java And selecting "java-11-openjdk.x86_64", then restart puppetdb and puppetserver. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.345012.1580837021000.30971.1586184780283%40Atlassian.JIRA.
Jira (PUP-2305) atboot time => false always creates /etc/fstab entry
Title: Message Title Stefan commented on PUP-2305 Re: atboot time => false always creates /etc/fstab entry Would it make sense to have atboot => false be an alias for options => noauto? I don't thinks so, as having the ability to not update /etc/fstab but mount a filesystem is useful. 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-6114) Add support for Artifactory checksum headers to puppet agent and enable SHA1 checksum type
Title: Message Title Stefan commented on PUP-6114 Re: Add support for Artifactory checksum headers to puppet agent and enable SHA1 checksum type FWIW, the original PR was closed, but there is a different one https://github.com/puppetlabs/puppet/pull/5707. 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-6114) Add support for Artifactory checksum headers to puppet agent and enable SHA1 checksum type
Title: Message Title Stefan commented on PUP-6114 Re: Add support for Artifactory checksum headers to puppet agent and enable SHA1 checksum type I'd really like to see this implemented, is it still planned to get this merged? 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-6624) File resource with source=http:// not updating on url change
Title: Message Title
Stefan commented on PUP-6624
Re: File resource with source=http:// not updating on url change
A workaround is to force md5 checksumming:
With apache, set ContentDigest On and use:
puppet apply -e 'file { "/tmp/foo": source => "http://localhost/bar", checksum => md5 }'
...
Notice: /Stage[main]/Main/File[/tmp/foo]/content: content changed '{md5}d3b07384d113edec49eaa6238ad5ff00' to '{md5}c157a79031e1c40f85931829bc5fc552'
puppet apply -e 'file { "/tmp/foo": source => "http://localhost/foo", checksum => md5 }'
...
Notice: /Stage[main]/Main/File[/tmp/foo]/content: content changed '{md5}c157a79031e1c40f85931829bc5fc552' to '{md5}d3b07384d113edec49eaa6238ad5ff00'
Add Comment
Jira (PUP-6624) File resource with source=http:// not updating on url change
Title: Message Title Stefan commented on PUP-6624 Re: File resource with source=http:// not updating on url change Can I get an update on that issue? Is it confirmed? Do you have an idea on how to fix it? Is it on the roadmap? Do you need anything from me? 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-6624) File resource with source=http:// not updating on url change
Title: Message Title Stefan commented on PUP-6624 Re: File resource with source=http:// not updating on url change FWIW, this also seems to happen if you change the target file on the node. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6624) File resource with source=http:// not updating on url change
Title: Message Title Stefan created an issue Puppet / PUP-6624 File resource with source=http:// not updating on url change Issue Type: Bug Assignee: Unassigned Created: 2016/08/17 6:01 AM Priority: Normal Reporter: Stefan It seems that puppet misses a changed source URL when the new URL points to a file that has an mtime which is older than the local file: in $HTTPROOT date > old.txt; sleep 1; date > new.txt; sleep 1 AFTER that has finished, run: /opt/puppetlabs/bin/puppet resource --verbose file /tmp/sample.txt ensure=present source=http://foo/old.txt
Jira (PUP-6624) File resource with source=http:// not updating on url change
Title: Message Title
Stefan updated an issue
Puppet / PUP-6624
File resource with source=http:// not updating on url change
Change By:
Stefan
It seems that puppet misses a changed source URL when the new URL points to a file that has an mtime which is older than the local file:in $HTTPROOT{noformat}date > old.txt; sleep 1; date > new.txt; sleep 1{noformat}*AFTER* that has finished, run:{noformat}/opt/puppetlabs/bin/puppet resource --verbose file /tmp/sample.txt ensure=present source=http://foo/old.txt Notice: /File[/tmp/sample.txt]/ensure: defined content as '{mtime}2016-08-17 13:45:40 +0200'file { '/tmp/sample.txt': ensure => 'file', content => '{mtime}2016-08-17 13:45:47 +0200',}{noformat}Now although new.txt has an mtime > than that of old.txt, sample.txt has an mtime > new.txt and puppet doesn't download new.txt:{noformat}/opt/puppetlabs/bin/puppet resource --verbose file /tmp/sample.txt ensure=present source=http://foo/new.txtfile { '/tmp/sample.txt': ensure => 'file', content => '{mtime}2016-08-17 13:45:47 +0200',}{noformat}in $HTTPROOT{noformat}date > new.txt{noformat}and now it's detected:{noformat}/opt/puppetlabs/bin/puppet resource --verbose file /tmp/sample.txt ensure=present source=http://foo/new.txtInfo: Computing checksum on file /tmp/sample.txtInfo: /File[/tmp/sample.txt]: Filebucketed /tmp/sample.txt to puppet with sum 9ea341e9d8f827cdbb014fb16aeee949Notice: /File[/tmp/sample.txt]/content: content changed '{mtime}2016-08-17 13:45:47 +0200' to '{mtime}2016-08-17 13:47:02 +0200'file { '/tmp/sample.txt': ensure => 'file', content => '{mtime}2016-08-17 13:47:13 +0200',}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
