Jira (PUP-5624) Properties (in resource types) should allow a read-only designation
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5624
Properties (in resource types) should allow a read-only designation
Change By:
Josh Cooper
Properties exist which are read-only. Examples include the "mtime" property of the File resource and the "power_state" property of the Vsphere_vm resource. Today, these read-only properties are implemented by making the validate method fail. This is a hack.In order to support better automatic documentation and validation there should exist a way to designate a property as read-only when defining them. A possible implementation would be a flag that can be passed when defining the property, similar to {{:array_matching}}.{code}newproperty(:minute, : ready_only read_only => true){code}A property defined as read-only should not need a custom validate function, and it should be possible to enumerate read-only properties for a type so as to separate them from read-write properties. This can be useful in auto documentation, pretty-print generation of Puppet code, or editing tools that integrate with Puppet's RAL.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-5607) Providers are loaded on server and may cause compilation to fail if confine fails
Title: Message Title Josh Cooper commented on PUP-5607 Re: Providers are loaded on server and may cause compilation to fail if confine fails This issue should be resolved in SERVER-2240, as puppetserver will no longer load types and providers. 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.109410.1450097496000.125762.1611731820101%40Atlassian.JIRA.
Jira (PUP-5298) file function doesn't support serving of files from mount point
Title: Message Title
Josh Cooper commented on PUP-5298
Re: file function doesn't support serving of files from mount point
If the file is in a module, you can do something like:
file(find_file("/"))
Or write a custom function to resolve the path for a custom mount point. That said, due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. As such we are closing this as “Won’t Fix.” We may revisit it at a later time, and if so will re-open this ticket.
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.100067.1443625533000.125754.1611731340156%40Atlassian.JIRA.
Jira (PUP-5200) Remove Solaris 10 conditional logic from beaker tests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5200 Remove Solaris 10 conditional logic from beaker tests Change By: Josh Cooper Summary: Enable stat tests on Remove Solaris 10 conditional logic from beaker tests 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.96887.1441389711000.125750.1611731100091%40Atlassian.JIRA.
Jira (PUP-4795) smf.rb provider for service - manifest does not work for S11.x
Title: Message Title Josh Cooper commented on PUP-4795 Re: smf.rb provider for service - manifest does not work for S11.x This ticket has not been updated in some time and is now being closed due to inactivity. This isn’t necessarily a statement that this ticket isn’t important - other issues may have demanded precedence since it was filed, or it may have simply slipped through the cracks. If any viewer/watcher feels closing this ticket is an error, please re-open it and add a comment explaining. Our apologies in advance for any mistake on this. 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.86601.1435600569000.125743.1611730560131%40Atlassian.JIRA.
Jira (PUP-4716) Add option to pass transaction_uuid into agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4716 Add option to pass transaction_uuid into agent Change By: Josh Cooper Labels: beginner help_wanted 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.83870.1433882434000.125740.1611730500045%40Atlassian.JIRA.
Jira (PUP-4406) Corrupt /etc/shadow entry when password hash contains newline
Title: Message Title Josh Cooper commented on PUP-4406 Re: Corrupt /etc/shadow entry when password hash contains newline Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch to the repository for this project at https://github.com/puppetlabs/puppet, please open a pull request and re-open this ticket. Pending that, we are closing this as “Won’t Fix.” We may revisit it at a later time, and if so will re-open this ticket. 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.75834.1428999528000.125737.1611730380033%40Atlassian.JIRA.
Jira (PUP-2931) Puppet CA sometimes resets certificate serial counter
Title: Message Title Josh Cooper commented on PUP-2931 Re: Puppet CA sometimes resets certificate serial counter All of the CA functionality has been removed from puppet and now resides in puppetserver. There have been a number of improvements to the latter to protect CA related files from concurrent updates. Could you try to reproduce with puppetserver, and file a SERVER ticket? In the meantime, I'm going to close this issue. 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.41965.1405334634000.125729.1611729540029%40Atlassian.JIRA.
Jira (PUP-2413) Attempting to log the output of service initialization on CentOS 6.5 causes SELinux violations
Title: Message Title Josh Cooper commented on PUP-2413 Re: Attempting to log the output of service initialization on CentOS 6.5 causes SELinux violations This ticket has not been updated in some time and is now being closed due to inactivity. This isn’t necessarily a statement that this ticket isn’t important - other issues may have demanded precedence since it was filed, or it may have simply slipped through the cracks. If any viewer/watcher feels closing this ticket is an error, please re-open it and add a comment explaining. Our apologies in advance for any mistake on this. 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.33904.1398957162000.125724.1611729180022%40Atlassian.JIRA.
Jira (PUP-1572) useradd provider should support usermod's move-home option if managehome is enabled
Title: Message Title Josh Cooper commented on PUP-1572 Re: useradd provider should support usermod's move-home option if managehome is enabled As noted in PUP-2387, puppet's managehome parameter only works if puppet creates or deletes the user account. It doesn't currently support moving the home directory for an existing user. 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.25238.139144304.125723.1611729000164%40Atlassian.JIRA.
Jira (PUP-2387) Remote users, specifically AD-LDAP, do not have their home directories created with managehome set to true
Title: Message Title Josh Cooper commented on PUP-2387 Re: Remote users, specifically AD-LDAP, do not have their home directories created with managehome set to true Puppet's managehome parameter only works if puppet creates or deletes the user account. It unfortunately doesn't support changing the home directory of an existing user The useradd provider has a similar problem, see PUP-1572. Puppet could be made to pass the correct arguments though it would be good to fix this consistently across the most commonly used user providers. 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.33668.1398810879000.125722.1611728880039%40Atlassian.JIRA.
Jira (PUP-2301) puppet module list --tree output shows dependencies incorrectly
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2301 puppet module list --tree output shows dependencies incorrectly Change By: Josh Cooper Team: Puppet Developer Experience Night's Watch 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.27587.1393543664000.125719.1611728340037%40Atlassian.JIRA.
Jira (PUP-2293) mode 'ug+w' affects other bits
Title: Message Title Josh Cooper commented on PUP-2293 Re: mode 'ug+w' affects other bits Puppet works this way because it applies symbolic modes relative to Puppet::Util::DEFAULT_POSIX_MODE which is defined as. Puppet doesn't apply the symbolic mode relative to the source file's mode. See https://github.com/puppetlabs/puppet/blob/6.20.0/lib/puppet/type/file.rb#L908. Puppet has always worked this way since symbolic modes were introduced in https://github.com/puppetlabs/puppet/commit/2ac94f94b9af6d8025ee0e771c4c7141ca9705c6#diff-909c0342abb4e713d05ed12ca713a199fd7fb79bc68927cef4e9b2e14726a684R740. In theory, puppet could be modified to retrieve the source file's mode, and apply the symbolic mode relative to that. However, it's non-trivial due to local vs remote sources, managing file content via the content or source parameter, and source_permissions defaults to ignore. Given that, I'm going to close this issue as won't do. 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.32153.1397743974000.125718.1611728220035%40Atlassian.JIRA.
Jira (PUP-1800) Ruby downcase does not handle all unicode letters
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-1800
Ruby downcase does not handle all unicode letters
Change By:
Josh Cooper
In the puppet language, {{" A" == "a"}} is true and {{" Ä" == "ä"}} should be true, but it is false . :{noformat}bx puppet apply -e 'notice("A" == "a") notice("Ä" == "ä")'Notice: Scope(Class[main]): trueNotice: Scope(Class[main]): false{noformat} Ruby doesn't properly handle changing from upper to lower case letters for all unicode glyphs in the letters category.Other interesting cases to look at are things like "ß" which has no upper/lower-case distinction.
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
Jira (PUP-1641) Solaris 10 packages not versionable?
Title: Message Title Josh Cooper commented on PUP-1641 Re: Solaris 10 packages not versionable? We dropped Solaris 10 support in Puppet 7 and the pkg provider (which is the default on Solaris 11) is versionable, upgradeable, etc. So I'm going to close this as won't do. 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.26061.1392132549000.125690.1611723660029%40Atlassian.JIRA.
Jira (PUP-1460) Puppet hangs trying to replace a FIFO
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-1460
Puppet hangs trying to replace a FIFO
Change By:
Josh Cooper
Puppet does some stupid things trying to replace a FIFO, including opening it and trying to MD5 the content.This allows a DoS for any managed file that can be replaced with a disconnected FIFO, at least.To reproduce: {noformat} mkfifo /tmp/boompuppet apply<< EOTfile { "/tmp/boom": ensure = > file, content = > "Hello, World" }EOT {noformat}
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.23952.1389949607000.125664.1611712320029%40Atlassian.JIRA.
Jira (PUP-1357) Class names that match the node name are not evaluated
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-1357 Class names that match the node name are not evaluated Change By: Josh Cooper Assignee: Henrik Lindberg Josh Cooper 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.22927.138877787.125649.1611711960108%40Atlassian.JIRA.
Jira (PUP-1357) Class names that match the node name are not evaluated
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1357 Class names that match the node name are not evaluated Change By: Josh Cooper Team: Froyo Coremunity 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.22927.138877787.125648.1611711960054%40Atlassian.JIRA.
Jira (PUP-1357) Class names that match the node name are not evaluated
Title: Message Title Josh Cooper commented on PUP-1357 Re: Class names that match the node name are not evaluated I verified this issue still exists in 6.19.1, but does not occur when using an ENC. As Nick Lewis said, the node scope is set in https://github.com/puppetlabs/puppet/blob/5d6412cf5de9ed93d80439c539c1416ecf3216b2/lib/puppet/resource/type.rb#L237. And then later we see if a class scope with that name has already been added https://github.com/puppetlabs/puppet/blob/5d6412cf5de9ed93d80439c539c1416ecf3216b2/lib/puppet/parser/scope.rb#L420. And since there's already a node scope with that name, we skip including the class in https://github.com/puppetlabs/puppet/blob/5d6412cf5de9ed93d80439c539c1416ecf3216b2/lib/puppet/parser/compiler.rb#L308-L313 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.22927.138877787.125635.1611710520035%40Atlassian.JIRA.
Jira (PUP-1357) Class names that match the node name are not evaluated
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-1357
Class names that match the node name are not evaluated
Change By:
Josh Cooper
If I setup: {code:puppet} class subversion { warning("I am class subversion")} {code} and in my nodes.pp I have {code} node subversion { include subversion } {code} When i run puppet in verbose mode on subversion, I never see that warning.
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.22927.138877787.125534.1611704220083%40Atlassian.JIRA.
Jira (PUP-1226) puppet breaking setuid bit on group change
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1226 puppet breaking setuid bit on group change Change By: Josh Cooper Team: Coremunity Night's Watch 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.22453.1387796518000.125523.1611703980132%40Atlassian.JIRA.
Jira (PUP-1226) puppet breaking setuid bit on group change
Title: Message Title Josh Cooper commented on PUP-1226 Re: puppet breaking setuid bit on group change The problem is that puppet retrieves the mode 06555 prior to changing the group and puppet assumes the group and mode can be set independently (and in any order). But as Daniel Dreier mentioned above, the chgrp results in the mode changing without puppet realizing it. The issue of interdependent file properties has come up before. Luke introduced the property_fix method in https://github.com/puppetlabs/puppet/commit/d145aae53ddf43de1a5140ce9226e1b2f383376f to ensure owner, group, mode, etc are correct. However it is only called if the file is created or written to. So one possible fix is to call property_fix after changing the group in the posix provider: https://github.com/puppetlabs/puppet/blob/5d6412cf5de9ed93d80439c539c1416ecf3216b2/lib/puppet/provider/file/posix.rb#L120 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.22453.1387796518000.125520.1611703920044%40Atlassian.JIRA.
Jira (PUP-6038) Puppet sets GID
Title: Message Title
Josh Cooper commented on PUP-6038
Re: Puppet sets GID
chmod results in the directory having permissions 444:
[root ~]# rm -rf /tmp/test/
[root ~]# mkdir /tmp/test
[root ~]# chmod u=rwx,g=rw,a=r /tmp/test
[root ~]# stat -c '%a' /tmp/test
444
puppet (6.19.1) behaves the same:
[root ~]# rm -rf /tmp/test/
[root ~]# cat sticky.pp
file { '/tmp/test':
ensure => 'directory',
mode=> 'u=rwx,g=rw,a=r',
}
[root ~]# puppet apply sticky.pp
Jira (PUP-1226) puppet breaking setuid bit on group change
Title: Message Title
Josh Cooper commented on PUP-1226
Re: puppet breaking setuid bit on group change
I can reproduce this issue on redhat as well. It takes two runs to converge:
[root ~]# puppet --version
6.19.1
[root ~]# facter os
{
architecture => "x86_64",
family => "RedHat",
hardware => "x86_64",
name => "RedHat",
release => {
full => "7.2",
major => "7",
minor => "2"
},
selinux => {
Jira (PUP-1226) puppet breaking setuid bit on group change
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-1226
puppet breaking setuid bit on group change
Change By:
Josh Cooper
We have a puppet module that's trying to manage owner, groupand setuid bit on /bin/nice: {code:puppet} file { "/bin/nice":owner => root,group => root,mode=> " 6555 " ,} {code} If the mode is correct, but group is wrong, puppet will fix thegroup and lose the setuid bit: {noformat} # chgrp bin /bin/nice# chmod 6555 /bin/nice# ls -l /bin/nice-r-sr-sr-x 1 root bin 23424 Jan 26 17:12 /bin/nice# pkill -USR1 puppetJun 29 22:26:29 xsp4 puppetd[21024]: Caught USR1; calling reloadJun 29 22:26:32 xsp4 puppetd[21024]: (/Stage[main]/SomeSystem::Nice/File[/bin/nice]/group) group changed 'bin' to 'root'Jun 29 22:26:33 xsp4 puppetd[21024]: Finished catalog run in 1.86 seconds# ls -l /bin/nice-r-xr-xr-x 1 root root 23424 Jan 26 17:12 /bin/nice {noformat} And puppet then needs a second run to fix the setuid bit: {noformat} # pkill -USR1 puppetJun 29 22:26:44 xsp4 puppetd[21024]: (/Stage[main]/SomeSystem::Nice/File[/bin/nice]/mode) mode changed '555' to '6555'# ls -l /bin/nice-r-sr-sr-x 1 root root 23424 Jan 26 17:12 /bin/nice {noformat} This has only been tested on v0.25.4 on RHEL5.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-1055) "invalid byte sequence" with service provider upstart
Title: Message Title Josh Cooper commented on PUP-1055 Re: "invalid byte sequence" with service provider upstart Per http://upstart.ubuntu.com/, upstart is in maintenance mode only and public support will end April 2021 for 16.04. Support has already ended for 14.04. Given the workaround above (seeing LC_ALL/LANG in the script that launches puppet as a service) I'm going to close this. 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.21373.138720113.125195.1611696120079%40Atlassian.JIRA.
Jira (PUP-1042) Change --write-catalog-summary option into a config setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1042 Change --write-catalog-summary option into a config setting Change By: Josh Cooper Team: Coremunity Night's Watch 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.21360.1387191693000.125142.1611693000119%40Atlassian.JIRA.
Jira (PUP-908) Refactor grammar validations to validation
Title: Message Title Josh Cooper commented on PUP-908 Re: Refactor grammar validations to validation Given the current state of things, I'm going to close this as won't do. Feel free to reopen if needed. 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.19870.1385947723000.125129.1611692880276%40Atlassian.JIRA.
Jira (PUP-684) Namevar over 1024 characters is not caught and results in invalid yaml with accompanying errors
Title: Message Title Josh Cooper commented on PUP-684 Re: Namevar over 1024 characters is not caught and results in invalid yaml with accompanying errors This is no longer reproducible given 6.19. We've also moved to JSON in puppet 7, so I'm going to close this: ? Notify[] Add Comment
Jira (FACT-1838) Additional support for cfacter (things like JNI support and curl)
Title: Message Title Josh Cooper updated an issue Facter / FACT-1838 Additional support for cfacter (things like JNI support and curl) Change By: Josh Cooper Epic Status: To Do Done 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.241404.1521069995000.125037.1611689880095%40Atlassian.JIRA.
Jira (FACT-1840) Add facter binary to cfacter gem
Title: Message Title Josh Cooper commented on FACT-1840 Re: Add facter binary to cfacter gem Given facterng, I'm going to close this. 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.242197.1521574538000.125036.1611689880052%40Atlassian.JIRA.
Jira (FACT-1826) Add JNI support to Facter gem
Title: Message Title Josh Cooper commented on FACT-1826 Re: Add JNI support to Facter gem Given facterng, I'm going to close this. 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.238978.1519864869000.125035.1611689820146%40Atlassian.JIRA.
Jira (PUP-7466) Attempt to redefine entity error while evaluating a Virtual Query
Title: Message Title
Greg Dubicki commented on PUP-7466
Re: Attempt to redefine entity error while evaluating a Virtual Query
In my case quick upgrade from Puppet 5 to 6 is not an option, but I did work around the issue by replacing code like:
resource { 'foo':
ensure => present,
require => My_failing_resource['bar'],
}
with something like:
my_failing_resource { 'bar':
ensure => present,
}
-> resource { 'foo':
ensure => present,
}
Jira (FACT-1383) Azure Instance Metadata
Title: Message Title Josh Cooper updated an issue Facter / FACT-1383 Azure Instance Metadata Change By: Josh Cooper Team: Platform OS Night's Watch 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.125281.1459963292000.124769.1611683700124%40Atlassian.JIRA.
Jira (FACT-1902) Facter should validate that external/custom/executable facts output proper UTF-8
Title: Message Title Josh Cooper commented on FACT-1902 Re: Facter should validate that external/custom/executable facts output proper UTF-8 I believe Facter 4 does this https://github.com/puppetlabs/facter/blob/33586eca494cc05fd6f0afb1eea15f6f690ef594/lib/facter/custom_facts/util/normalization.rb#L59-L70. Maybe it is still an issue for facter 3.x? Thoughts Bogdan Irimie? 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.290197.1546471789000.124765.1611683580024%40Atlassian.JIRA.
Jira (FACT-1902) Facter should validate that external/custom/executable facts output proper UTF-8
Title: Message Title Josh Cooper updated an issue Facter / FACT-1902 Facter should validate that external/custom/executable facts output proper UTF-8 Change By: Josh Cooper Team: Platform OS Night's Watch 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.290197.1546471789000.124757.1611683340244%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Josh Cooper commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails Jarret Lavallee sounds good. Also to summarize this issue, the current 6.x behavior matches how 5.x worked. It just so happened that 6.14.0 would process server_list for every REST request, regardless of whether the previous request succeeded or not. 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.381638.1608653215000.124632.1611678600261%40Atlassian.JIRA.
Jira (PUP-10859) Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode
Title: Message Title Morgan Rhodes assigned an issue to Unassigned Puppet / PUP-10859 Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode Change By: Morgan Rhodes Assignee: Morgan Rhodes 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.384622.1611426826000.124614.1611677820028%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Jarret Lavallee commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails Josh Cooper and Dorin Pleava Thank you for looking into this deeper and providing some great analysis. I think you are correct with the desired behavior and we should close this ticket. 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.381638.1608653215000.124613.1611677640119%40Atlassian.JIRA.
Jira (PUP-10860) 'startup_time' metric should not include splay time
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10860 'startup_time' metric should not include splay time Change By: Josh Cooper Team: Night's Watch 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.384844.1611673048000.124576.1611675660183%40Atlassian.JIRA.
Jira (PUP-10860) 'startup_time' metric should not include splay time
Title: Message Title Josh Cooper commented on PUP-10860 Re: 'startup_time' metric should not include splay time Thanks Adam Winberg. Seems like we could record the amount of time spent splaying (in https://github.com/puppetlabs/puppet/blob/5d6412cf5de9ed93d80439c539c1416ecf3216b2/lib/puppet/scheduler/splay_job.rb#L6), yield that time to the block starts the splayed run: https://github.com/puppetlabs/puppet/blob/5d6412cf5de9ed93d80439c539c1416ecf3216b2/lib/puppet/daemon.rb#L158, and pass that time into the `agent.run` method. Then we can leave the "startup_time" as is, or subtract the "splay_time"? 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.384844.1611673048000.124575.1611675660139%40Atlassian.JIRA.
Jira (PUP-10860) 'startup_time' metric should not include splay time
Title: Message Title Josh Cooper moved an issue Puppet / PUP-10860 'startup_time' metric should not include splay time Change By: Josh Cooper Key: PA PUP - 3547 10860 Affects Version/s: puppet-agent 6.19.0 Affects Version/s: PUP 6.19.0 Project: Puppet Agent 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
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Dorin Pleava commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails After some digging around on versions 5.5 21, 6.13.0, 6.14.0 and the newly released 6.20.0, only 6.14.0 did some things different. On 6.14.0, when a server failed midrun, the current running part would fail (like Retrieving pluginfacts, or Retrieving facts) and the code would continue to the next part(Retrieving locales) where it would check again for an available server, choosing the next functional server from server_list. I think this is not the intended functionality, as it could cause some sort of mix between catalogs from different servers. [root@blue-bumper ~]# puppet --version 6.14.0 [root@blue-bumper ~]# puppet agent -t --debug ... Debug: Creating new connection for https://past-medication.delivery.puppetlabs.net:8140 Debug: Starting connection for https://past-medication.delivery.puppetlabs.net:8140 Error: Could not retrieve catalog from remote server: Request to https://past-medication.delivery.puppetlabs.net:8140/puppet/v3/catalog/blue-bumper.delivery.puppetlabs.net?environment=production failed after 0.001 seconds: Failed to open TCP connection to past-medication.delivery.puppetlabs.net:8140 (Connection refused - connect(2) for "past-medication.delivery.puppetlabs.net" port 8140) Wrapped exception: Failed to open TCP connection to past-medication.delivery.puppetlabs.net:8140 (Connection refused - connect(2) for "past-medication.delivery.puppetlabs.net" port 8140)
Jira (PUP-10854) apt provider does not work with local packages
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Puppet / PUP-10854 apt provider does not work with local packages Change By: Ciprian Badescu Assignee: Ciprian Badescu 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.383202.1610630264000.124409.1611661320295%40Atlassian.JIRA.
