Jira (PUP-8115) Puppet randomly corrupts files (it puts json/pson instead of file content)
Title: Message Title Ivan Bayan commented on PUP-8115 Re: Puppet randomly corrupts files (it puts json/pson instead of file content) I could run puppet with option -debug , but as i said before it happens rarely, here is very low chance that puppet will corrupt anything when i will run it manually. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8115) Puppet randomly corrupts files (it puts json/pson instead of file content)
Title: Message Title Ivan Bayan commented on PUP-8115 Re: Puppet randomly corrupts files (it puts json/pson instead of file content) Sorry for that mistake, i fixed log from puppetserver.log I put info in 'environment' description, here is it: client: puppet 3.8.7 CentOS release 6.6 (Final) ruby 1.8.7 server: puppetserver version: 2.8.0 Ubuntu 16.04.3 LTS foreman 1.15.6-1 openjdk-8-jdk-headless 8u131-b11-2ubuntu1.16.04.3 openjdk-8-jre-headless 8u131-b11-2ubuntu1.16.04.3 ruby 2.3.1 Also i found one similar bug: https://projects.puppetlabs.com/issues/1010 It's very old, but it's very close to problem which occurred in our environment. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8115) Puppet randomly corrupts files (it puts json/pson instead of file content)
Title: Message Title
Ivan Bayan updated an issue
Puppet / PUP-8115
Puppet randomly corrupts files (it puts json/pson instead of file content)
Change By:
Ivan Bayan
Few weeks ago we have started to notice corrupted files which managed by puppet.Every time content of file changed to something like json. It happens rarely and unpredictable.For example, file resource definition:{code} file { '/etc/puppet/etckeeper-commit-pre':mode => '755',owner => root,group => root,source => 'puppet:///modules/amoeba/etckeeper-commit-pre', }{code}It was regular shell script, but content changed to:{code}{"path":"/etc/puppetlabs/code/environments/fcc_production/modules/amoeba/files/etckeeper-commit-pre","relative_path":null,"links":"manage","owner":0,"group":752,"mode":420,"checksum":{"type":"md5","value":"{md5}20814627a1afc8495d264bd1403b498c"},"type":"file","destination":null}Last modification date:~# ls -l /etc/puppet/etckeeper-commit-pre-rwxr-xr-x 1 root root 279 Oct 30 09:35 /etc/puppet/etckeeper-commit-pre{code}For that puppet run, syslog contains next:{code}Oct 30 09:30:50 lou-webproxy puppet-agent[16977]: Local environment: "production" doesn't match server specified node environment "fcc_production", switching agent to "fcc_production".Oct 30 09:33:30 lou-webproxy puppet-agent[16977]: Could not retrieve catalog from remote server: execution expiredOct 30 09:33:30 lou-webproxy puppet-agent[16977]: Using cached catalogOct 30 09:33:35 lou-webproxy puppet-agent[16977]: (/Stage[main]/Security_updates/File[/etc/yum/yum-cron.conf]) Could not evaluate: Could not retrieve file metadata for puppet:///modules/security_updates/yum-cron.conf: Could not intern from text/pson: Paths must be fully qualifiedOct 30 09:34:48 lou-webproxy puppet-agent[16977]: (/Stage[main]/Bash::Logout/File[/etc/bash.bash_logout_fcc]/content) content changed '{md5}c3b5264e7fe471a18f30f8468af159ea' to '{md5}93b20bfff221414cdbaf45bedc8db6f2'Oct 30 09:34:56 lou-webproxy puppet-agent[16977]: (/Stage[main]/Amoeba::Etckeeper/Epel/File[/etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6]) Could not evaluate: Could not retrieve file metadata for puppet:///modules/epel/RPM-GPG-KEY-EPEL-6: Could not intern from application/octet-stream: No format match the given format name or mime-type (application/octet-stream)Oct 30 09:35:20 lou-webproxy puppet-agent[16977]: (/Stage[main]/Amoeba::Etckeeper/File[/etc/puppet/etckeeper-commit-pre]/content) content changed '{md5}20814627a1afc8495d264bd1403b498c' to '{md5}d865e6b948a74cb03bc3401c0b01b785'Oct 30 09:35:21 lou-webproxy puppet-agent[16977]: (/Stage[main]/Amoeba::Etckeeper/Epel/Epel::Rpm_gpg_key[EPEL-6]/Exec[import-EPEL-6]) Dependency File[/etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6] has failures: trueOct 30 09:35:21 lou-webproxy puppet-agent[16977]: (/Stage[main]/Amoeba::Etckeeper/Epel/Epel::Rpm_gpg_key[EPEL-6]/Exec[import-EPEL-6]) Skipping because of failed dependenciesOct 30 09:35:21 lou-webproxy puppet-agent[16977]: (/Stage[main]/Amoeba::Etckeeper/Epel/Yumrepo[epel-testing-debuginfo]) Dependency File[/etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6] has failures: trueOct 30 09:35:21 lou-webproxy puppet-agent[16977]: (/Stage[main]/Amoeba::Etckeeper/Epel/Yumrepo[epel-testing-debuginfo]) Skipping because of failed dependenciesOct 30 09:35:21 lou-webproxy puppet-agent[16977]: (/
Jira (PUP-8066) Failing acceptance tests in FIPS mode
Title: Message Title Jayant Sane commented on PUP-8066 Re: Failing acceptance tests in FIPS mode Once there is proper platform support for FIPS the above set of passing tests would need to be adjusted to have their fips mode of operation based on the platform. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (FACT-1795) Add whereami executable
Title: Message Title Casey Williams created an issue Facter / FACT-1795 Add whereami executable Issue Type: New Feature Assignee: Casey Williams Created: 2017/11/06 8:47 PM Fix Versions: whereami 0.2.0 Priority: Normal Reporter: Casey Williams It would be helpful at least for debugging to eventually have a whereami executable to build along with libwhereami. This could just print detection results and accept a --debug argument. Add Comment This
Jira (PUP-4368) Allow loading file_serving terminii from modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4368 Allow loading file_serving terminii from modules Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8003) Update and test rubocop performance complaints Performance/Caller and Performance/CompareWithBlock
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8003 Update and test rubocop performance complaints Performance/Caller and Performance/CompareWithBlock Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title Josh Cooper commented on PUP-8041 Re: Replace FACTER_url with --target for puppet resource with devices Based on Thomas' last comment, I'm going to close this. Please reopen if I'm mistaken. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7940) Support task diagnostics in a plan
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7940 Support task diagnostics in a plan Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-2928) Puppet tries to update the group for user when he is listed as its member twice.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2928 Puppet tries to update the group for user when he is listed as its member twice. Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7999) Puppet Lookup should be easily used as a library in other applications
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7999 Puppet Lookup should be easily used as a library in other applications Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-2968) Make it possible to namespace ruby-defined custom types
Title: Message Title Josh Cooper assigned an issue to Henrik Lindberg Puppet / PUP-2968 Make it possible to namespace ruby-defined custom types Change By: Josh Cooper Assignee: Kylo Ginsberg Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-2968) Make it possible to namespace ruby-defined custom types
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2968 Make it possible to namespace ruby-defined custom types Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7677 Create a feature flag setting for puppet 6 features during puppet 5 lifetime Change By: Jorie Tappa Sprint: Platform Core KANBAN Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (HI-368) Update AIO acceptance setup to skip puppetlabs-release
Title: Message Title Josh Cooper updated an issue Hiera / HI-368 Update AIO acceptance setup to skip puppetlabs-release Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8014) Create an environment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8014 Create an environment_ttl setting to clear short-lived puppet environments from memory Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-4568) Puppet agent does not resend certificate request to master
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4568 Puppet agent does not resend certificate request to master Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1542) Puppet::Util::Log requires a message
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1542 Puppet::Util::Log requires a message Change By: Josh Cooper Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1542) Puppet::Util::Log requires a message
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1542 Puppet::Util::Log requires a message Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDB-3750) (PDB 3654) bump version to 6.0.2
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3750 (PDB 3654) bump version to 6.0.2 Issue Type: Bug Assignee: Unassigned Created: 2017/11/06 3:43 PM Priority: Normal Reporter: gepetto-bot bumps version and adds changelog docs Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8051) puppet agent option to wait for lock
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8051 puppet agent option to wait for lock Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8073) (Re)move the execution functions from puppet (to a "module" in bolt)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8073 (Re)move the execution functions from puppet (to a "module" in bolt) Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8075) tickets merged from feature branch should be made up to date
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8075 tickets merged from feature branch should be made up to date Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-4644) puppet tells you to read man pages that aren't installed
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4644 puppet tells you to read man pages that aren't installed Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8074) Make trial merge of feature_puppet-tasks branch and run acceptance
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8074 Make trial merge of feature_puppet-tasks branch and run acceptance Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8076) language specification needs to be updated with changes from feature_puppet-tasks
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8076 language specification needs to be updated with changes from feature_puppet-tasks Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-4284) Puppet module install does not fully honour --target-dir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4284 Puppet module install does not fully honour --target-dir Change By: Josh Cooper Team: Modules Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-4095) As a user I don't want PMT to pollute my metadata.json with a dependency on stdlib.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4095 As a user I don't want PMT to pollute my metadata.json with a dependency on stdlib. Change By: Josh Cooper Team: Modules Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7978) PMT Should Install Modules as pe-puppet / create the modules directory as pe-puppet
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7978 PMT Should Install Modules as pe-puppet / create the modules directory as pe-puppet Change By: Craig Gomes Team: Modules Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-2928) Puppet tries to update the group for user when he is listed as its member twice.
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-2928
Puppet tries to update the group for user when he is listed as its member twice.
Change By:
Josh Cooper
When a user is found in several nss group backends ralsh shows it as being included into a group more than once and puppet continually tries to remove the user from that group.To clarify:I have a following resource in my manifest: {code:puppet} user { 'tomcat7': groups => 'ssl-user',} {code} Until recently everything was just fine but lately the following actions began to appear: {noformat} notice: /Stage[main]/Tomcat/User[tomcat7]/groups: groups changed 'ssl-user,ssl-user' to 'ssl-user' {noformat} The reason for that behaviour turned out to be the following line in /etc/nsswitch.conf: {noformat} root@susegrp1:~# cat /etc/nsswitch.conf | grep groupgroup: files ldap compat {noformat} When I remove the line everything returns back to normal way. Here is the output of actual state of resource on the system and as seen by puppet: {noformat} root@susegrp1:~# id tomcat7uid=108(tomcat7) gid=114(tomcat7) groups=301(ssl-user),114(tomcat7)root@susegrp1:~# getent group | grep ssl-userssl-user:x:301:tomcat7ssl-user:x:301:tomcat7root@susegrp1:~# ralsh user tomcat7warning: User tomcat7 found in both useradd and useradd; skipping the useradd versionuser { 'tomcat7': ensure => 'present', gid => '114', groups => ['ssl-user', 'ssl-user'], home => '/usr/share/tomcat7', password => '*', password_max_age => '9', password_min_age => '0', shell=> '/bin/false', uid => '108',} {noformat} I've reproduced this on puppet version 2.7.11-13 and not tested others.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-7977) Add a password_script attribute to user resource
Title: Message Title Eric Sorenson commented on PUP-7977 Re: Add a password_script attribute to user resource We're working adding end-to-end support for encrypted data in puppet, by marking them using the Sensitive type. Read more here: https://puppet.com/docs/puppet/5.3/lang_data_sensitive.html would that solve the problem you're running into? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7968) group resource doesn't default to ensure=>present
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7968 group resource doesn't default to ensure=>present Change By: Craig Gomes Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7968) group resource doesn't default to ensure=>present
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7968 group resource doesn't default to ensure=>present Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7972) Change in groups attribute of User resource only adds group membership but does not remove any
Title: Message Title Eric Sorenson commented on PUP-7972 Re: Change in groups attribute of User resource only adds group membership but does not remove any This is not entirely unexpected. You need to set the auth_membership attribute on your user: https://puppet.com/docs/puppet/5.3/type.html#user-attribute-auth_membership Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7972) Change in groups attribute of User resource only adds group membership but does not remove any
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-7972 Change in groups attribute of User resource only adds group membership but does not remove any Change By: Eric Sorenson Security: Internal Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7999) Puppet Lookup should be easily used as a library in other applications
Title: Message Title Eric Sorenson commented on PUP-7999 Re: Puppet Lookup should be easily used as a library in other applications It should look up the same thing as you'd get from the command line or from inside Puppet, using an on-disk hierarchy. This seems pretty useful but it's hard to tell whether it would be used widely enough to be worth the effort. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8115) Puppet randomly corrupts files (it puts json/pson instead of file content)
Title: Message Title Josh Cooper commented on PUP-8115 Re: Puppet randomly corrupts files (it puts json/pson instead of file content) It'd also be useful to run the agent with - http_debug and -debug to see what REST requests it's making. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8048) puppet / facter fails randomly in low memory situations
Title: Message Title Eric Sorenson commented on PUP-8048 Re: puppet / facter fails randomly in low memory situations Florian - this will be a bit hard to reproduce, and you're right that it's not really "supported" to run puppet in 128mb RAM. Ruby is probably going to fail in bizarre ways that Puppet does not have visibility into. Can you confirm that running facter --debug by itself fails on this system? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8048) puppet / facter fails randomly in low memory situations
Title: Message Title Eric Sorenson assigned an issue to Florian Klink Puppet / PUP-8048 puppet / facter fails randomly in low memory situations Change By: Eric Sorenson Assignee: Florian Klink Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8055) Mount command on FreeBSD inaccurate for some fs types.
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-8055 Mount command on FreeBSD inaccurate for some fs types. Change By: Eric Sorenson Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8050) puppet agent -e environment
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-8050 puppet agent -e environment Change By: Eric Sorenson Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8115) Puppet randomly corrupts files (it puts json/pson instead of file content)
Title: Message Title Eric Sorenson commented on PUP-8115 Re: Puppet randomly corrupts files (it puts json/pson instead of file content) Hi Ivan - this is going to be really hard to dig into without a stand-alone reproduction case. The content of that file is the puppet server's HTTP response for file metadata - so something has gone awry where it put that response into the content instead of using it to determine whether to retrieve the actual file content. The errors from the agent are interesting: Oct 30 09:35:51 lou-webproxy puppet-agent[16977]: (/Stage[main]/Amoeba::Etckeeper/File[/etc/puppet/etckeeper-commit-post]) Could not evaluate: Could not retrieve file metadata for puppet:///modules/amoeba/etckeeper-commit-post: Could not intern from application/octet-stream: No format match the given format name or mime-type (application/octet-stream) I think the second log is not actually your puppetserver, maybe a mis-paste? It's the same content as the agent one. This suggests the agent and the server are not talking the same language - what version of puppet is on your master? Add Comment Thi
Jira (PUP-8106) "mount" type should autorequire its mountpoint
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8106 "mount" type should autorequire its mountpoint Change By: Craig Gomes Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8106) "mount" type should autorequire its mountpoint
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8106 "mount" type should autorequire its mountpoint Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8107) Ability to specify source IP for the agent
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8107 Ability to specify source IP for the agent Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8115) Puppet randomly corrupts files (it puts json/pson instead of file content)
Title: Message Title Eric Sorenson assigned an issue to Ivan Bayan Puppet / PUP-8115 Puppet randomly corrupts files (it puts json/pson instead of file content) Change By: Eric Sorenson Assignee: Ivan Bayan Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (FACT-1349) testing custom fact via RUBYLIB causes segfaults
Title: Message Title Garrett Guillotte commented on FACT-1349 Re: testing custom fact via RUBYLIB causes segfaults Linking DOC-2596; I'm concerned about documenting the use of RUBYLIB to test custom facts while this is open. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (FACT-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1781 Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 Change By: Geoff Nichols Sprint: Platform OS 2017-10-31 , Platform OS Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8065) puppet acceptance test server_list_setting.rb fails on AIX and Solaris
Title: Message Title Geoff Nichols assigned an issue to Casey Williams Puppet / PUP-8065 puppet acceptance test server_list_setting.rb fails on AIX and Solaris Change By: Geoff Nichols Assignee: Casey Williams Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8065) puppet acceptance test server_list_setting.rb fails on AIX and Solaris
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8065 puppet acceptance test server_list_setting.rb fails on AIX and Solaris Change By: Geoff Nichols Sprint: Platform OS Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDB-3654) Bump puppetlabs-inifile dep upper range to 3.0.0
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3654 Bump puppetlabs-inifile dep upper range to 3.0.0 Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (FACT-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title Maggie Dreyer commented on FACT-1781 Re: Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 These errors don't seem to be coming from unit tests, it looks like the problem may be bigger than just a bad test. Unfortunately the original job where these failures showed up is gone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8065) puppet acceptance test server_list_setting.rb fails on AIX and Solaris
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8065
puppet acceptance test server_list_setting.rb fails on AIX and Solaris
Change By:
Maggie Dreyer
Link to the overall list of jobs:https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/master/view/Non-Standard/job/platform_puppet-agent_intn-van-sys_suite-secondary-puppet-master/30/https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/master/view/Suite/job/platform_puppet-agent_integration-vanagon-suite-daily-master/12/COMPONENT=puppet,SLAVE_LABEL=beaker,TEST_TARGET=solaris10-64a/Relevant part of the output (using the AIX 6.1 job as reference):{code}Debug: Facter: resolving hypervisors facts.Debug: Facter: dmidecode executable not foundDebug: Facter: /sys/class/dmi/id/ not found.Error: Facter: Facter.to_hash uncaught exception: boost::too_many_args: format-string referred to less arguments than were passedError: Could not retrieve local facts: undefined method `[]=' for nil:NilClassError: Failed to apply catalog: Could not retrieve local facts: undefined method `[]=' for nil:NilClassDebug: Failed to load library 'msgpack' for feature 'msgpack': cannot load such file -- msgpackDebug: Puppet::Network::Format[msgpack]: feature msgpack is missingDebug: report supports formats: json pson yamlDebug: Failed to load library 'msgpack' for feature 'msgpack': cannot load such file -- msgpackDebug: Puppet::Network::Format[msgpack]: feature msgpack is missingDebug: report supports formats: json pson yamlDebug: Failed to load library 'msgpack' for feature 'msgpack': cannot load such file -- msgpackDebug: Puppet::Network::Format[msgpack]: feature msgpack is missingDebug: report supports formats: json pson yamlDebug: Using cached connection for https://u7tzaige52d694t.delivery.puppetlabs.net:8140Debug: Caching connection for https://u7tzaige52d694t.delivery.puppetlabs.net:8140Debug: Closing connection for https://u7tzaige52d694t.delivery.puppetlabs.net:8140{code} This is also causing many failures in the Facter tests:{code}Beaker::Host::CommandFailure: Host 'aix-61-agent2.delivery.puppetlabs.net' exited with 1 running: env TERM="xterm-256color" facter --debug --color Last 10 lines of output were:2017-11-05 17:06:16.801647 DEBUG leatherman.execution:476 - completed processing output: closing child pipes.2017-11-05 17:06:16.801832 DEBUG leatherman.execution:558 - process exited with status code 0.2017-11-05 17:06:16.801951 DEBUG puppetlabs.facter - fact "augeasversion" has resolved to "1.8.1".2017-11-05 17:06:16.802022 DEBUG puppetlabs.facter - fact "augeas" has resolved to { version => "1.8.1"}.2017-11-05 17:06:16.802088 DEBUG puppetlabs.facter - resolving hypervisors facts.2017-11-05 17:06:16.802216 DEBUG puppetlabs.whereami - dmidecode executable not found2017-11-05 17:06:16.802269 DEBUG puppetlabs.whereami
Jira (PUP-8065) puppet acceptance test server_list_setting.rb fails on AIX and Solaris
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8065
puppet acceptance test server_list_setting.rb fails on AIX and Solaris
Change By:
Maggie Dreyer
Link to the overall list of jobs:https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/master/view/Non-Standard/job/platform_puppet-agent_intn-van-sys_suite-secondary-puppet-master/30/https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/master/view/Suite/job/platform_puppet-agent_integration-vanagon-suite-daily-master/12/COMPONENT=puppet,SLAVE_LABEL=beaker,TEST_TARGET=solaris10-64a/Relevant part of the output (using the AIX 6.1 job as reference):{code} 21 Debug : 13 Facter : 02 Failed Tests Cases: resolving hypervisors facts. 21 Debug : 13 Facter : 02 Errored Tests Cases: dmidecode executable not found 21 Debug : 13 Facter : 02 Test Case tests / server_list_setting sys/class/dmi/id/ not found . rb reported Error : # Facter : PuppetAcceptance Facter.to_hash uncaught exception : boost : DSL : too_many_args : Helpers.with_puppet_running_on failed (check backtrace format-string referred to less arguments than were passedError: Could not retrieve local facts: undefined method `[]=' for location) because nil : Host NilClassError: Failed to apply catalog: Could not retrieve local facts: undefined method `[]= ' pe-aix-61-spec.delivery.puppetlabs.net' exited with 1 running for nil : NilClass 21 Debug : 13 Failed to load library 'msgpack' for feature 'msgpack' : 02 puppet agent cannot load such file - t - -config /tmp/puppet_conf_test.14296 --server notvalid --server_list tqgqq3oxkg5t4ww.delivery.puppetlabs.net:8140 --debug msgpack 21 Debug : 13 Puppet : 02 Last 10 lines of output were : 21 Network : 13 : 02 Format[msgpack]: feature msgpack is missing Debug: report supports formats: json pson yaml 21:13:02 Debug: Failed to load library 'msgpack' for feature 'msgpack': cannot load such file -- msgpack 21:13:02 Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing 21:13:02 Debug: report supports formats: json pson yaml 21:13:02 Debug: Failed to load library 'msgpack' for feature 'msgpack': cannot load such file -- msgpack 21:13:02 Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing 21:13:02 Debug: report supports formats: json pson yaml 21:13:02 Debug: Using cached connection for https:// tqgqq3oxkg5t4ww u7tzaige52d694t .delivery.puppetlabs.net:8140 21:13:02 Debug: Caching connection for https:// tqgqq3oxkg5t4ww u7tzaige52d694t .delivery.puppetlabs.net:8140 21:13:02 Debug: Closing connection for https:// tqgqq3oxkg5t4ww u7tzaige52d694t .delivery.puppetlabs.net:8140{code}
Jira (FACT-1794) os.family.major incorrectly returns a number with a decimal point for Ubuntu
Title: Message Title garrett honeycutt commented on FACT-1794 Re: os.family.major incorrectly returns a number with a decimal point for Ubuntu You can use os.release.full to get 16.04 or 16.10 so having .major mirror .full is not useful. I want to support Ubuntu x.04 LTS along with the x.10. In the past this was done with os.release.major and now that fails. It seems wrong to go back to using regex matching against the data instead of dictating that .major would just be number before a separator. This behavior is intuitive and the current behavior violates least surprise. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8125) Hiera 5 Custom Backends don't work with puppet apply
Title: Message Title Robert Brooks commented on PUP-8125 Re: Hiera 5 Custom Backends don't work with puppet apply you are correct! uggh, sorry, I cloned the repo as a test case. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (FACT-1794) os.family.major incorrectly returns a number with a decimal point for Ubuntu
Title: Message Title Michael Smith commented on FACT-1794 Re: os.family.major incorrectly returns a number with a decimal point for Ubuntu 16 is not an Ubuntu release, so that would be misleading. Ubuntu uses two-part codes to denote a release, i.e. 16.04 and 16.10. This was an intentional change as part of FACT-976 to treat e.g. 16.04 as the major release version for an Ubuntu release. Windows has similar constraints: Windows 8, 8.1, 2012, and 2012 R2 are all treated as major versions. Facter 3 does not provide a guarantee of the acceptance criteria you included. Is there some reason that's untenable? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-151) Display results as they occur, instead of when all nodes finish
Title: Message Title Jenny Mahmoudi commented on BOLT-151 Re: Display results as they occur, instead of when all nodes finish Ah ok, that makes sense. This should help it feel like Bolt is running faster then. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-151) Display results as they occur, instead of when all nodes finish
Title: Message Title Josh Cooper commented on BOLT-151 Re: Display results as they occur, instead of when all nodes finish Currently, bolt does not output any results until all nodes are finished. To see this run a command, e.g. sleep 1, on multiple nodes and set concurrency to 1. This ticket makes it possible for bolt to output results as each node finishes. Note there is a related ticket BOLT-118 for streaming results when using the oneline output format. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-151) Display results as they occur, instead of when all nodes finish
Title: Message Title Jenny Mahmoudi commented on BOLT-151 Re: Display results as they occur, instead of when all nodes finish Will bolt be displaying node results as each node finishes? As in, all of nodeX's output, then the all of the output for the next node that finishes? (I thought that's how it was operating already, so I probably either misunderstood that behavior, or this ticket). Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDB-3654) Bump puppetlabs-inifile dep upper range to 3.0.0
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3654 Bump puppetlabs-inifile dep upper range to 3.0.0 Change By: Rob Browning Summary: Bumped Bump puppetlabs-inifile dep upper range to 3.0.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8102) Add a 'call_function' to the PAL API
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8102 Add a 'call_function' to the PAL API Change By: Kenn Hussey Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8086) Provide PAL API to use a modulepath and environment name
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8086 Provide PAL API to use a modulepath and environment name Change By: Kenn Hussey Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8070) cannot extract partial result from errors in plans
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8070 cannot extract partial result from errors in plans Change By: Kenn Hussey Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8020 Add data types Nodes and Node to puppet for tasks/plans Change By: Kenn Hussey Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-202) When running bolt task on a WIndows node without Puppet installed, the error message is very obscure.
Title: Message Title Kenn Hussey updated an issue Puppet Task Runner / BOLT-202 When running bolt task on a WIndows node without Puppet installed, the error message is very obscure. Change By: Kenn Hussey Sprint: Tasks ELP (1.0) Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (FACT-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title Casey Williams commented on FACT-1781 Re: Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 Hmm, yeah, here's the offending test in the commit 5.3.x points to: https://github.com/puppetlabs/facter/blob/73e53be0eb4656140cc8d192d6c6949dd67f8f51/lib/tests/util/string.cc#L278 And master's commit: https://github.com/puppetlabs/facter/blob/8338d91781cd228e9eb60de7b71e8df231739911/lib/tests/util/string.cc#L278 Looks exactly the same Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title Eric Delaney commented on PUP-8122 Re: I18n strings that include repeated lists of sentence fragments can be hard to translate Larissa Lane The description lists the cases I could find where we build a list of something and want to include it in the output. The one line code example above each code section is the line that is repeats to make up the list. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8122
I18n strings that include repeated lists of sentence fragments can be hard to translate
Change By:
Eric Delaney
We need to review the PO file and source code of pupppet looking for strings where we build up a list of things where we include sentence fragment in the repeated list and determine if this should be change to allow for better translationsFor example the below code includes a sentence fragment "which depends on" which will be hard to translate into Japanese, We should create a list of cases, review them and determine which ones we want to change string in. lib/puppet/module_tool/errors/shared.rb{code}_("which depends on '%{name}' (%{version})") % { name: m[:name], version: v(m[:version]) }{code}{code} dependency_list = @source[1..-1].map do |m|#TRANSLATORS This message repeats as separate lines as a list under the heading "You specified '%{name}' (%{version})\n"_("which depends on '%{name}' (%{version})") % { name: m[:name], version: v(m[:version]) } end.join(",\n") msg_variables = { requested_module: @requested_module, version: v(@requested_version), module_name: @module_name,name: @source.first[:name], dependency_list: dependency_list } _(<<-EOM).chomp % msg_variablesCould not install module '%{requested_module}' (%{version}) No version of '%{module_name}' will satisfy dependenciesYou specified '%{name}' (%{version})%{dependency_list}Use `puppet module install --force` to install this module anyway EOM{code}{code}_("You may have meant `puppet module %{action} %{suggestion}`") % { action: @action, suggestion: suggestion }{code}{code} suggestion_list = @suggestions.map do |suggestion|_("You may have meant `puppet module %{action} %{suggestion}`") % { action: @action, suggestion: suggestion } end.join("\n") if @action == :upgrade# TRANSLATORS `puppet module install` is a command line and should not be translated_(<<-EOM).chomp % { action: @action, module_name: @module_name, suggestion_list: suggestion_list }Could not %{action} module '%{module_name}' Module '%{module_name}' is not installed%{suggestion_list}Use `puppet module install` to install this moduleEOM else_(<<-EOM).chomp % { action: @action, module_name: @module_name, suggestion_list: suggestion_list }Could not %{action} module '%{module_name}' Module '%{module_name}' is not installed%{suggestion_list}EOM end{code}{code}_("'%{module_name}' (%{version}) was found in %{path}") % { module_name: @module_name, version: v(mod.version), path: mod.modulepath }{code}{code} module_path_list = @modules.map do |mod|#TRANSLATORS This is repeats as separate lines as a list under "Module '%{module_name}' appears multiple places in the module path"_("'%{module_name}' (%{version}) was found in %{path}") % { module_name: @module_name, version: v(mod.version), path: mod.modulepath } end.join("\n") # TRANSLATORS `--modulepath` is command line option and should not be translated _(<<-EOM).chomp % { action: @action, module_name: @module_name, module_path_list: module_path_list }Could not %{action} module '%{module_name}' Modu
Jira (PUP-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8122
I18n strings that include repeated lists of sentence fragments can be hard to translate
Change By:
Eric Delaney
We need to review the PO file and source code of pupppet looking for strings where we build up a list of things where we include sentence fragment in the repeated list and determine if this should be change to allow for better translationsFor example the below code includes a sentence fragment "which depends on" which will be hard to translate into Japanese, We should create a list of cases, review them and determine which ones we want to change string in. lib/puppet/module_tool/errors/shared.rb {code} _("which depends on '%{name}' (%{version})") % { name: m[:name], version: v(m[:version]) }{code} def multiline {code} dependency_list = @source[1..-1].map do |m|#TRANSLATORS This message repeats as separate lines as a list under the heading "You specified '%{name}' (%{version})\n"_("which depends on '%{name}' (%{version})") % { name: m[:name], version: v(m[:version]) } end.join(",\n") msg_variables = { requested_module: @requested_module, version: v(@requested_version), module_name: @module_name,name: @source.first[:name], dependency_list: dependency_list } _(<<-EOM).chomp % msg_variablesCould not install module '%{requested_module}' (%{version}) No version of '%{module_name}' will satisfy dependenciesYou specified '%{name}' (%{version})%{dependency_list}Use `puppet module install --force` to install this module anyway EOM {code}{code}_("You may have meant `puppet module %{action} %{suggestion}`") % { action: @action, suggestion: suggestion }{code}{code} suggestion_list = @suggestions.map do |suggestion|_("You may have meant `puppet module %{action} %{suggestion}`") % { action: @action, suggestion: suggestion } end .join("\n") if @action == :upgrade# TRANSLATORS `puppet module install` is a command line and should not be translated_(<<-EOM).chomp % { action: @action, module_name: @module_name, suggestion_list: suggestion_list }Could not %{action} module '%{module_name}' Module '%{module_name}' is not installed%{suggestion_list}Use `puppet module install` to install this moduleEOM else_(<<-EOM).chomp % { action: @action, module_name: @module_name, suggestion_list: suggestion_list }Could not %{action} module '%{module_name}' Module '%{module_name}' is not installed%{suggestion_list}EOM end{ code} {code}_("'%{module_name}' (%{version}) was found in %{path}") % { module_name: @module_name, version: v(mod.version), path: mod.modulepath }{code}{code} module_path_list = @modules.map do |mod|#TRANSLATORS This is repeats as separate lines as a list under "Module '%{module_name}' appears multiple places in the module path"_("'%{module_name}' (%{version}) was found in %{path}") % { module_name: @module_name, version: v(mod.version), path: mod.modulepath } end.join("\n") # TRANSLATORS `--modulepath` is command line option and should not be translated _(<<-EOM).chomp % { action: @action, module_name: @module_name, module_path_list: module_path_list }Could not %{action} m
Jira (PDB-3749) (PDB- 3723) jsonb fact storage
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3749 (PDB- 3723) jsonb fact storage Issue Type: Bug Assignee: Unassigned Created: 2017/11/06 8:28 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (FACT-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title Casey Williams commented on FACT-1781 Re: Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 Yeah, the mergeup definitely happened (and it looks like the fix is an ancestor of PA master's current facter commit), so I'm kind of at a loss to describe why this is still happening, since it's not there on 5.3.x. I'll do some more digging today. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (FACT-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title Maggie Dreyer commented on FACT-1781 Re: Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 This is still showing up, in a job that ran Sunday night. Did that new merge-up happen? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8113) Remove incorrect deprecation warning for `audit` metaparam
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8113 Remove incorrect deprecation warning for `audit` metaparam Change By: Eric Delaney QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-207) a folder in the tasks folder generates an error in Puppet console
Title: Message Title Adam Buxton created an issue Puppet Task Runner / BOLT-207 a folder in the tasks folder generates an error in Puppet console Issue Type: Bug Assignee: Unassigned Created: 2017/11/06 7:05 AM Priority: Normal Reporter: Adam Buxton /tasks/subdir when deployed in Puppet Enterprise generates the following error Error loading metadata: java.io.IOException: HTTP GET to https://master.puppetlabs.vm:8140/puppet/v3/tasks//:500: Internal Server Error: java.io.FileNotFoundException: /etc/puppetlabs/code/modules//tasks/(Is a directory) relates to https://tickets.puppetlabs.com/browse/BOLT-190 not supporting subdirs, but the documentation suggests it does. Add Comment This
Jira (BOLT-190) Tasks in subfolders of a module are not found
Title: Message Title Adam Buxton commented on BOLT-190 Re: Tasks in subfolders of a module are not found Alex Dreyer then the doco is written from an incorrect spec as the doco sets the expectation of this being the behavior https://puppet.com/docs/bolt/0.x/writing_tasks.html#naming-tasks We should update the doco if this is not supported as yet. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8121) Init[T] close to unusuable due to relaxed signatures in several core data types
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8121
Init[T] close to unusuable due to relaxed signatures in several core data types
Change By:
Henrik Lindberg
Release Notes Summary:
We have never released the The {{Init \[T] }} data type so it is introduced in 5.1.0 did not work as expected with some of the core data types as they were to relaxed in use except inside the specifications of also unreleased Pcore the arguments they accept when creating new instances . As a consequence {{Init}} could match invalid values.
Release Notes:
Not Needed Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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-8121) Init[T] close to unusuable due to relaxed signatures in several core data types
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8121 Init[T] close to unusuable due to relaxed signatures in several core data types Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8110) Certificate signing request using sha384, sha512 spec test fail
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8110 Certificate signing request using sha384, sha512 spec test fail Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8122 I18n strings that include repeated lists of sentence fragments can be hard to translate Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8123) Upper Case in class names is not working correctly
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8123 Upper Case in class names is not working correctly Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8124) Puppet 5 Release Notes Missed a Language Deprecation
Title: Message Title Craig Gomes assigned an issue to Henrik Lindberg Puppet / PUP-8124 Puppet 5 Release Notes Missed a Language Deprecation Change By: Craig Gomes Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8124) Puppet 5 Release Notes Missed a Language Deprecation
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8124 Puppet 5 Release Notes Missed a Language Deprecation Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8123) Upper Case in class names is not working correctly
Title: Message Title Martin Ewings commented on PUP-8123 Re: Upper Case in class names is not working correctly Just retested, keeping the classname serVice but change the pp serVice.pp to service.pp seems to make this work, so looks like the case is only an issue in the filenames rather than the class names Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8123) Upper Case in class names is not working correctly
Title: Message Title Henrik Lindberg commented on PUP-8123 Re: Upper Case in class names is not working correctly Martin Ewings Does it work in the serVice case if the autoloaded for this class is in a file with lower case name? (I cannot reproduce this on latest puppet with simple self contained code snippet, and hence suspect auto loading) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8125) Hiera 5 Custom Backends don't work with puppet apply
Title: Message Title Thomas Hallgren assigned an issue to Robert Brooks Puppet / PUP-8125 Hiera 5 Custom Backends don't work with puppet apply Change By: Thomas Hallgren Assignee: Thomas Hallgren Robert Brooks Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8125) Hiera 5 Custom Backends don't work with puppet apply
Title: Message Title Thomas Hallgren commented on PUP-8125 Re: Hiera 5 Custom Backends don't work with puppet apply I see that the module is named hiera_mysql (stated in its metadata) but the description says it's installed in a directory named hiera-mysql. Using a dash '-' in the directory name of a module name is AFAIK, not permitted. Is this a typo in the report or the real source of the problem? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8121) Init[T] close to unusuable due to relaxed signatures in several core data types
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8121 Init[T] close to unusuable due to relaxed signatures in several core data types Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8123) Upper Case in class names is not working correctly
Title: Message Title
Martin Ewings updated an issue
Puppet / PUP-8123
Upper Case in class names is not working correctly
Change By:
Martin Ewings
Since 4.10, upper case chars have been allowed in classnames so long as they match the following regex:\A[a-z][a-z0-9_]*\Zthe only stipulation on case is that the class must start with a lowercase letter, see the documentation below:https://puppet.com/docs/puppet/4.10/lang_reserved.html#classes-and-defined-resource-typesHowever in testing, i have modified the service class within the puppetlabs-ntp module, including filename and all class calls and declarations to ntp::serVice, when applying the init.pp example in this module i am presented with:{code}Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::ntp::service for hoytrc at /etc/puppetlabs/code/environments/production/modules/ntp/manifests/init.pp:132:3 on node hoytrc{code}note the reference to :ntp::service for line 132 of init.pp which is declared as:{code} contain ntp::serVice{code}it looks like there is some backend downcasing which is in conflict with expected behaviour.tested in PE2017.2.2 and PE2017.3.1 Original case reported from the field:{code} Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Could not find declared class splunk::apps::windows_TA_ad at /var/puppet/svn/env/modules/splunk/manifests/init_search.pp:25:6 on node itu302.acs.kadaster.nl Warning: Not using cache on failed catalog {code} {code} This is a class that defines a Splunk search-node. The last step is the installation of additional Splunk apps. The array $splunk_apps contains the names of Splunk apps to be installed (e.g., [ "unix_app", "sa_nix", "pa_nmon_light", "windows_TA_ad" ]). The apps have corresponding puppet-class. ``` {code} # Class splunk::init_search class splunk::init_search ($splunk_apps=hiera(splunk_server_apps)) {# include the params file so the there defined variables are available throughout the module include splunk::params $ar = prefix( $splunk_apps, 'splunk::apps::' )# flow control anchor{'splunk::init_search::begin':} -> class{'splunk::prereq_storage':} -> class{'splunk::swap':} -> class{'splunk::prereq':} -> class{'splunk::packages':} -> class{'splunk::install_proxy':} -> class{'splunk::search::install':} -> class{'splunk::splunk_nonroot':} -> class{'splunk::install':} -> class{'splunk::install_deplclient':} -> class{'splunk::search::config':} ~> class{'splunk::service':} -> anchor{'splunk::init_search::end':}Anchor['splunk::init_search::begin'] -> Class['splunk::search::config'] -> class{$ar: } -> Anchor['splunk::init_search::end']} {code}
Jira (PUP-8123) Upper Case in class names is not working correctly
Title: Message Title
Martin Ewings updated an issue
Puppet / PUP-8123
Upper Case in class names is not working correctly
Change By:
Martin Ewings
Since 4.10, upper case chars have been allowed in classnames so long as they match the following regex:\A[a-z][a-z0-9_]*\Zthe only stipulation on case is that the class must start with a lowercase letter, see the documentation below:https://puppet.com/docs/puppet/4.10/lang_reserved.html#classes-and-defined-resource-typesHowever in testing, i have modified the service class within the puppetlabs-ntp module, including filename and all class calls and declarations to ntp::serVice, when applying the init.pp example in this module i am presented with:{code}Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::ntp::service for hoytrc at /etc/puppetlabs/code/environments/production/modules/ntp/manifests/init.pp:132:3 on node hoytrc{code}note the reference to :ntp::service for line 132 of init.pp which is declared as:{code} contain ntp::serVice{code}it looks like there is some backend downcasing which is in conflict with expected behaviour.tested in PE2017.2.2 and PE2017.3.1 Original case reported from the field:{code} Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Could not find declared class splunk::apps::windows_TA_ad at /var/puppet/svn/env/modules/splunk/manifests/init_search.pp:25:6 on node itu302.acs.kadaster.nl Warning: Not using cache on failed catalog {code }{code} This is a class that defines a Splunk search-node. The last step is the installation of additional Splunk apps. The array $splunk_apps contains the names of Splunk apps to be installed (e.g., [ "unix_app", "sa_nix", "pa_nmon_light", "windows_TA_ad" ]). The apps have corresponding puppet-class.``` # Class splunk::init_search class splunk::init_search ($splunk_apps=hiera(splunk_server_apps)) {# include the params file so the there defined variables are available throughout the module include splunk::params $ar = prefix( $splunk_apps, 'splunk::apps::' )# flow control anchor{'splunk::init_search::begin':} -> class{'splunk::prereq_storage':} -> class{'splunk::swap':} -> class{'splunk::prereq':} -> class{'splunk::packages':} -> class{'splunk::install_proxy':} -> class{'splunk::search::install':} -> class{'splunk::splunk_nonroot':} -> class{'splunk::install':} -> class{'splunk::install_deplclient':} -> class{'splunk::search::config':} ~> class{'splunk::service':} -> anchor{'splunk::init_search::end':}Anchor['splunk::init_search::begin'] -> Class['splunk::search::config'] -> class{$ar: } -> Anchor['splunk::init_search::end']} {code}
Jira (PUP-8123) Upper Case in class names is not working correctly
Title: Message Title
Martin Ewings updated an issue
Puppet / PUP-8123
Upper Case in class names is not working correctly
Change By:
Martin Ewings
Since 4.10, upper case chars have been allowed in classnames so long as they match the following regex:\A[a-z][a-z0-9_]*\Zthe only stipulation on case is that the class must start with a lowercase letter, see the documentation below:https://puppet.com/docs/puppet/4.10/lang_reserved.html#classes-and-defined-resource-typesHowever in testing, i have modified the service class within the puppetlabs-ntp module, including filename and all class calls and declarations to ntp::serVice, when applying the init.pp example in this module i am presented with:{code}Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::ntp::service for hoytrc at /etc/puppetlabs/code/environments/production/modules/ntp/manifests/init.pp:132:3 on node hoytrc{code}note the reference to :ntp::service for line 132 of init.pp which is declared as:{code} contain ntp::serVice{code}it looks like there is some backend downcasing which is in conflict with expected behaviour.tested in PE2017.2.2 and PE2017.3.1 Original case reported from the field:{code} Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Could not find declared class splunk::apps::windows_TA_ad at /var/puppet/svn/env/modules/splunk/manifests/init_search.pp:25:6 on node itu302.acs.kadaster.nl Warning: Not using cache on failed catalog {code }{code} This is a class that defines a Splunk search-node. The last step is the installation of additional Splunk apps. The array $splunk_apps contains the names of Splunk apps to be installed (e.g., [ "unix_app", "sa_nix", "pa_nmon_light", "windows_TA_ad" ]). The apps have corresponding puppet-class.``` # Class splunk::init_search class splunk::init_search ($splunk_apps=hiera(splunk_server_apps)) {# include the params file so the there defined variables are available throughout the module include splunk::params $ar = prefix( $splunk_apps, 'splunk::apps::' )# flow control anchor{'splunk::init_search::begin':} -> class{'splunk::prereq_storage':} -> class{'splunk::swap':} -> class{'splunk::prereq':} -> class{'splunk::packages':} -> class{'splunk::install_proxy':} -> class{'splunk::search::install':} -> class{'splunk::splunk_nonroot':} -> class{'splunk::install':} -> class{'splunk::install_deplclient':} -> class{'splunk::search::config':} ~> class{'splunk::service':} -> anchor{'splunk::init_search::end':}Anchor['splunk::init_search::begin'] -> Class['splunk::search::config'] -> class{$ar: } -> Anchor['splunk::init_search::end']} {code}
