Jira (FACT-1455) id fact -- getgrgid_r failed: Numerical result out of range (34)
Title: Message Title Alex Jurkiewicz created an issue Facter / FACT-1455 id fact -- getgrgid_r failed: Numerical result out of range (34) Issue Type: Bug Affects Versions: FACT 3.1.8 Assignee: Unassigned Components: PE Created: 2016/07/10 6:44 PM Environment: Linux 2.6.32-504.el6.x86_64 Priority: Normal Reporter: Alex Jurkiewicz This occurs with 3.1.3 (eg PE 2015.3) and 3.2.0 (eg PE 2016.02): [root@semapp-devr102 ~]# facter --version
Jira (FACT-1455) id fact -- getgrgid_r failed: Numerical result out of range (34)
Title: Message Title
Alex Jurkiewicz updated an issue
Facter / FACT-1455
id fact -- getgrgid_r failed: Numerical result out of range (34)
Change By:
Alex Jurkiewicz
This occurs with 3.1.3 (eg PE 2015.3) and 3.2.0 (eg PE 2016.02):{code} [root@semapp-devr102 ~] # facter --version3.1.3 (commit 1aa380a82ec35b7f8e7e58fab627e74f93aaeff3)3.2.0 (commit 148948d795fbdcf6bcf51ed36a73f496775835dc){code}{code}# facter --log-level trace id2016-07-11 11:42:17.311364 INFO puppetlabs.facter - executed with command line: --log-level trace id.2016-07-11 11:42:17.312711 INFO leatherman.ruby:133 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2.1.0".2016-07-11 11:42:17.382841 INFO leatherman.ruby:182 - using ruby version 2.1.92016-07-11 11:42:17.382968 INFO puppetlabs.facter - requested queries: id.2016-07-11 11:42:17.383240 DEBUG puppetlabs.facter - fact "facterversion" has resolved to "3.2.0".2016-07-11 11:42:17.383318 DEBUG puppetlabs.facter - fact "aio_agent_version" has resolved to "1.5.2".2016-07-11 11:42:17.383701 DEBUG puppetlabs.facter - searching "/opt/puppetlabs/facter/facts.d" for external facts.2016-07-11 11:42:17.383862 DEBUG puppetlabs.facter - skipping external facts for "/etc/facter/facts.d": No such file or directory2016-07-11 11:42:17.383937 DEBUG puppetlabs.facter - skipping external facts for "/etc/puppetlabs/facter/facts.d": No such file or directory2016-07-11 11:42:17.383977 DEBUG puppetlabs.facter - no external facts were found.2016-07-11 11:42:17.384841 DEBUG puppetlabs.facter - loading all custom facts.2016-07-11 11:42:17.384930 DEBUG puppetlabs.facter - resolving id facts.2016-07-11 11:42:17.390609 WARN puppetlabs.facter - getgrgid_r failed: Numerical result out of range (34)2016-07-11 11:42:17.390710 DEBUG puppetlabs.facter - fact "id" has resolved to "root".2016-07-11 11:42:17.390790 DEBUG puppetlabs.facter - fact "identity" has resolved to { uid => 0, user => "root"}.root#{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2861) support case-insensitive regex
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2861 support case-insensitive regex Issue Type: New Feature Assignee: Unassigned Created: 2016/07/10 3:14 PM Priority: Normal Reporter: Wyatt Alt See discussion here: https://groups.google.com/forum/#!msg/puppet-users/LpV_b19lsHs/gkCN3lnECAAJ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6485) make it easier to require based on tag
Title: Message Title Henrik Lindberg commented on PUP-6485 Re: make it easier to require based on tag I probably mixed up require/before... Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6485) make it easier to require based on tag
Title: Message Title
Henrik Lindberg commented on PUP-6485
Re: make it easier to require based on tag
Queries cannot produce a value - they run very late in the compilation process. We need to change what queries are in that case.
You can also map, all of the produced resouces - like this:
$tmp = $packages.map |$package| {
package{$package:
ensure => present,
}
}
file{"/foo": }
$tmp -> File['/foo']
Add Comment
Jira (PUP-6485) make it easier to require based on tag
Title: Message Title
Henrik Lindberg commented on PUP-6485
Re: make it easier to require based on tag
While not exactly the same - you could do: {puppet:code}
$packages.each |$package| { package{$package: tag => bar, # not really needed ensure => present, before => File['/foo'], } }
file {"/foo": }
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6467) Fix Parallel Spec grouping for RSpec 3.5.0
Title: Message Title Glenn Sarti commented on PUP-6467 Re: Fix Parallel Spec grouping for RSpec 3.5.0 CI completed with success. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2018) `puppet certificate generate` Generates Two CSRs in One Run
Title: Message Title R.I.Pienaar commented on PUP-2018 Re: `puppet certificate generate` Generates Two CSRs in One Run Eric Sorenson repro steps..I dont think puppet cert can talk to remote CAs so not sure if it does the exact same thing Here I expect just one cert made but it makes the new one and then the fqdn one - which the master already have and so i get the wrong key error If I set --certname rip.mcollective (to match the requested cert) it attempts to make the same cert twice. % rm -rf .puppetlabs/etc/puppet/ssl % puppet --version 4.5.2 % ls /home/rip/.puppetlabs/etc/puppet/csr_attributes.yaml ls: cannot access /home/rip/.puppetlabs/etc/puppet/csr_attributes.yaml: No such file or directory % puppet certificate generate rip.mcollective --ca-location remote --ca_server dev5.devco.net --debug --verbose Info: Creating a new SSL key for rip.mcollective Info: csr_attributes file loading from /home/rip/.puppetlabs/etc/puppet/csr_attributes.yaml
