Jira (FACT-3001) Debug output shows facter gets called thousands of times
Title: Message Title Nathanael Cole updated an issue Facter / FACT-3001 Debug output shows facter gets called thousands of times Change By: Nathanael Cole Zendesk Ticket Count: 2 3 Zendesk Ticket IDs: 47112,49141 ,50054 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.393130.1617033494000.52999.1666818240037%40Atlassian.JIRA.
Jira (FACT-3135) YAML anchors no longer function properly in Facter 4
Title: Message Title
Nathanael Cole updated an issue
Facter / FACT-3135
YAML anchors no longer function properly in Facter 4
Change By:
Nathanael Cole
It appears that yaml anchors have stopped working in facter 4. In facter 3, this external yaml fact is processed correctly: {code:java} // "/opt/puppetlabs/facter/facts.d/test.yaml" 13L, 118C 9,7 All---one: ipam: a: - foo cname: - bartwo: IPAM: A: *a1 CNAME: *a2 {code} When running puppet facts --debug: {code:java} // ESC[0;36mDebug: Facter: resolving facts from YAML file "/opt/puppetlabs/facter/facts.d/test.yaml".ESC[0mESC[0;36mDebug: Facter: fact "one" has resolved to { ipam => { a => [ "foo" ], cname => [ "bar" ] }}.ESC[0m ESC[0;36mDebug: Facter: fact "two" has resolved to { IPAM => { A => [ "foo" ], CNAME => [ "bar" ] }}.ESC[0m{ code}In facter 4, this fails: {code:java} // c:Error: Facter: Failed to handle /opt/puppetlabs/facter/facts.d/test.yaml as LegacyFacter::Util::Parser::YamlParser facts: Unknown alias: a1{code}The expectation is that yaml anchors should function the same as they did in prior versions. Support has recommended their use on multiple prior occasions.
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (FACT-3135) YAML anchors no longer function properly in Facter 4
Title: Message Title Nathanael Cole created an issue Facter / FACT-3135 YAML anchors no longer function properly in Facter 4 Issue Type: Task Affects Versions: FACT 4.2.8 Assignee: Unassigned Components: Facter 4 Created: 2022/07/08 9:19 AM Priority: Normal Reporter: Nathanael Cole It appears that yaml anchors have stopped working in facter 4. In facter 3, this external yaml fact is processed correctly: // "/opt/puppetlabs/facter/facts.d/test.yaml" 13L, 118C 9,7 All --- one: ipam: a:
Jira (PUP-11520) Support for SMB authentication on the File resource
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-11520 Support for SMB authentication on the File resource Change By: Nathanael Cole With the sunset of the dsc_lite dsc module, customers who wish to use the previous dsc_file resource against authenticated SMB shares have no supported option to continue doing that. It makes sense to thus update the core file resource so that it supports SMB share authentication. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444747.1650906574000.17215.1650909420095%40Atlassian.JIRA.
Jira (PUP-11520) Support for SMB authentication on the File resource
Title: Message Title Nathanael Cole created an issue Puppet / PUP-11520 Support for SMB authentication on the File resource Issue Type: Improvement Affects Versions: PUP 7.14.0, PUP 6.26.0 Assignee: Unassigned Created: 2022/04/25 10:09 AM Priority: Normal Reporter: Nathanael Cole With the sunset of the dsc_lite module, customers who wish to use the previous dsc_file resource against authenticated SMB shares have no supported option to continue doing that. It makes sense to thus update the core file resource so that it supports SMB share authentication. Add Comment
Jira (PUP-9013) password_max_age is incorrectly set when using a value of -1
Title: Message Title
Nathanael Cole updated an issue
Puppet / PUP-9013
password_max_age is incorrectly set when using a value of -1
Change By:
Nathanael Cole
*Puppet Version:* 5.5.2 / PE 2018.1.2*OS Name/Version:* RHEL 7.5 / Centos 6.9*Desired Behavior:*Using -1 as the value for password_max_age should properly remove / unset password expiry on new / existing users.*Actual Behavior:*Using the following test: {code} user { ' bob blah ': ensure => present, forcelocal => true, managehome => true, password => '!!', password_max_age => '-1',}{code} Puppet repeatedly applies the value from 4294967295 to -1. After doing so, the calue is not properly reported by chage. {code} [root@testbox1802 blah]# puppet apply blah.ppNotice: Compiled catalog for testbox1802.doomfacenet.local in environment production in 0.02 secondsNotice: /Stage[main]/Main/User[blah]/ensure: createdNotice: Applied catalog in 1.16 seconds[root@testbox1802 blah]# chage -l blahLast password change : Jul 23, 2018Password expires : neverPassword inactive : neverAccount expires : neverMinimum number of days between password change : 0Maximum number of days between password change : 4294967295Number of days of warning before password expires : 7[root@testbox1802 blah]# puppet apply blah.ppNotice: Compiled catalog for testbox1802.doomfacenet.local in environment production in 0.02 secondsNotice: /Stage[main]/Main/User[blah]/password_max_age: password_max_age changed 4294967295 to -1Notice: Applied catalog in 0.74 seconds[root@testbox1802 blah]# chage -l blahLast password change : Jul 23, 2018Password expires : neverPassword inactive : neverAccount expires : neverMinimum number of days between password change : 0Maximum number of days between password change : 4294967295Number of days of warning before password expires : 7[root@testbox1802 blah]# grep blah /etc/shadowblah:!!:17735:0:-1:7:::[root@testbox1802 blah]# chage -l blahLast password change : Jul 23, 2018Password expires : neverPassword inactive : neverAccount expires : neverMinimum number of days between password change : 0Maximum number of days between password change : 4294967295Number of days of warning before password expires : 7[root@testbox1802 blah]# puppet apply blah.ppNotice: Compiled catalog for testbox1802.doomfacenet.local in environment production in 0.03 secondsNotice: /Stage[main]/Main/User[blah]/password_max_age: password_max_age changed 4294967295 to -1Notice: Applied catalog in 0.57 seconds[root@testbox1802 blah]# grep blah /etc/shadowblah:!!:17735:0:-1:7:::[root@testbox1802 blah]# chage -l blahLast password change : Jul 23, 2018Password expires : neverPassword inactive :
Jira (PUP-9013) password_max_age is incorrectly set when using a value of -1
Title: Message Title
Nathanael Cole created an issue
Puppet / PUP-9013
password_max_age is incorrectly set when using a value of -1
Issue Type:
Bug
Affects Versions:
PUP 5.5.2
Assignee:
Unassigned
Created:
2018/07/23 1:12 PM
Priority:
Normal
Reporter:
Nathanael Cole
Puppet Version: 5.5.2 / PE 2018.1.2 OS Name/Version: RHEL 7.5 / Centos 6.9 Desired Behavior: Using -1 as the value for password_max_age should properly remove / unset password expiry on new / existing users. Actual Behavior: Using the following test:
user { 'bob':
ensure => present,
forcelocal => true,
managehome => true,
password => '!!',
Jira (PUP-7326) Group resource (with auth_membership) failes if local Windows group contains not resolvable Domain accounts
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-7326 Group resource (with auth_membership) failes if local Windows group contains not resolvable Domain accounts Change By: Nathanael Cole Component/s: Windows 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-7326) Group resource (with auth_membership) failes if local Windows group contains not resolvable Domain accounts
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-7326 Group resource (with auth_membership) failes if local Windows group contains not resolvable Domain accounts Change By: Nathanael Cole Summary: Group resource (with auth_membership) failes if local Winows Windows group contains not resolvable Domain accounts 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-6863) Set max_nesting to prevent "Nesting Level Too Deep" errors in catalog
Title: Message Title
Nathanael Cole updated an issue
Puppet / PUP-6863
Set max_nesting to prevent "Nesting Level Too Deep" errors in catalog
Change By:
Nathanael Cole
When using hiera data code with 20+ levels of nesting nested data , puppet runs fail with error "Error: Could not retrieve catalog from remote server: Could not intern from text/pson: nesting of 20 is too deep"From agent debug trace:{code}...Debug: Facter: resolving Xen facts.Debug: Failed to load library 'msgpack' for feature 'msgpack'Debug: Puppet::Network::Format[msgpack]: feature msgpack is missingDebug: catalog supports formats: pson yaml dot binaryDebug: Using cached connection for https://ip-10-253-17-187:8140Debug: Caching connection for https://ip-10-253-17-187:8140Error: Could not retrieve catalog from remote server: Could not intern from text/pson: nesting of 20 is too deep/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:270:in `parse_object'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:225:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:246:in `parse_array'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:220:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:280:in `parse_object'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:225:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:246:in `parse_array'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:220:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:280:in `parse_object'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:225:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:246:in `parse_array'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:220:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:280:in `parse_object'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:225:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:246:in `parse_array'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:220:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:280:in `parse_object'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:225:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:246:in `parse_array'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:220:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:280:in `parse_object'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:225:in `parse_value'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:246:in `parse_array'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:220:in
Jira (PUP-6863) Modify max_nesting to prevent "Nesting Level Too Deep" errors with complex hiera
Title: Message Title Nathanael Cole created an issue Puppet / PUP-6863 Modify max_nesting to prevent "Nesting Level Too Deep" errors with complex hiera Issue Type: Bug Affects Versions: PUP 4.7.0 Assignee: Unassigned Created: 2016/11/02 9:10 AM Priority: Normal Reporter: Nathanael Cole When using hiera with 20+ levels of nesting, puppet runs fail with error "Error: Could not retrieve catalog from remote server: Could not intern from text/pson: nesting of 20 is too deep" From agent debug trace: ... Debug: Facter: resolving Xen facts. Debug: Failed to load library 'msgpack' for feature 'msgpack'
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-6382 Add "Automatic (delayed start)" as option for Service Resource on Windows Change By: Nathanael Cole CS Priority: Needs Priority Normal 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-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Nathanael Cole created an issue Puppet / PUP-6382 Add "Automatic (delayed start)" as option for Service Resource on Windows Issue Type: New Feature Assignee: Unassigned Components: Windows Created: 2016/06/02 12:43 PM Priority: Normal Reporter: Nathanael Cole The service resource does not currently support an option to set a Windows service to the "Automatic (delayed start)" status. Please add this support. Add Comment
Jira (PUP-6181) in the PE Console, the default basemodulepath doesn't inherit custom codedir from puppet.conf
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-6181 in the PE Console, the default basemodulepath doesn't inherit custom codedir from puppet.conf Change By: Nathanael Cole Summary: in the PE Console, the default basemodulepath doesn't inherit custom codedir in from puppet.conf 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-6181) in the PE Console, the default basemodulepath doesn't inherit custom codedir from puppet.conf
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-6181 in the PE Console, the default basemodulepath doesn't inherit custom codedir from puppet.conf Change By: Nathanael Cole h3. IssueIn 2015.3.3 (tested), if you specify a custom codedir in puppet.conf, without also specifying a specific basemodulepath, the basemodulepath within the Console itself does not update according to the default behaviour as described here: https://docs.puppet.com/puppet/latest/reference/configuration.html#basemodulepathClasses added to the assumed basemodulepath within that custom codedir will be available for use directly within other code, but the PE Console can not see or apply them.h3. Expected ResultsBased on the wording of the basemodulepath configuration (https://docs.puppet.com/puppet/latest/reference/configuration.html#basemodulepath), if you specify a custom "/path/to/code/" codedir, then the basemodulepath would default to "/path/to/code/modules/"Assumption of default based on documentation: "Default: $codedir/modules:/opt/puppetlabs/puppet/modules"h3. ReplicationTo replicate# spin up new 2015.3.3 directory# mkdir -p /path/to/code/modules# specify /path/to/code/ as codedir in puppet.conf# run puppet config print basemodulepath, notice expected /path/to/code/modules# create test module in /path/to/code/modules# refresh console classes listFAIL: test module is not available within the Console.h3. Work-AroundIf you specify /path/to/code as your codedir, you can also specify /path/to/code/modules as your basemodulepath, and the modules in the path will now be available in the console.To replicate:# spin up new 2015.3.3 directory# mkdir -p /path/to/code/modules# specify /path/to/code/ as codedir in puppet.conf# specify /path/to/code/modules as basemodulepath in puppet.conf# run puppet config print basemodulepath, notice expected /path/to/code/modules# create test module in /path/to/code/modules# refresh console classes listSUCCESS: Test class is now available to be added within the Console. Add Comment
Jira (PUP-6181) in the PE Console, the default basemodulepath doesn't inherit custom codedir in puppet.conf
Title: Message Title Nathanael Cole created an issue Puppet / PUP-6181 in the PE Console, the default basemodulepath doesn't inherit custom codedir in puppet.conf Issue Type: Improvement Affects Versions: PUP 4.3.2 Assignee: Unassigned Created: 2016/04/18 12:39 PM Priority: Major Reporter: Nathanael Cole Issue In 2015.3.3 (tested), if you specify a custom codedir in puppet.conf, without also specifying a specific basemodulepath, the basemodulepath does not update according to the default behaviour as described here: https://docs.puppet.com/puppet/latest/reference/configuration.html#basemodulepath Classes added to the assumed basemodulepath within that custom codedir will be available for use directly within other code, but the PE Console can not see or apply them. Expected Results Based on the wording of the basemodulepath configuration (https://docs.puppet.com/puppet/latest/reference/configuration.html#basemodulepath), if you specify a custom "/path/to/code/" codedir, then the basemodulepath would default to "/path/to/code/modules/" Assumption of default based on documentation: "Default: $codedir/modules:/opt/puppetlabs/puppet/modules" Replication To replicate spin up new 2015.3.3 directory
Jira (FACT-1365) Remove "Deprecated: use `puppet facts` instead" from facter --help output
Title: Message Title Nathanael Cole created an issue Facter / FACT-1365 Remove "Deprecated: use `puppet facts` instead" from facter --help output Issue Type: Improvement Affects Versions: FACT 3.1.4 Assignee: Unassigned Created: 2016/03/11 7:36 AM Priority: Normal Reporter: Nathanael Cole Current State: The help dump (facter --help) for the current version of Facter shows a deprecation warning next to the -p flag description. Requested Change: I have confirmed in the facter channel that this is misleading, and that deprecation is no longer valid. With customers contacting us regarding it, we hope that deprecation warning can be removed in coming versions until such a time as a functional replacement is offered again. Add Comment
Jira (HI-502) Improved error reporting for "segmented key lookup" failure
Title: Message Title Nathanael Cole updated an issue Hiera / HI-502 Improved error reporting for "segmented key lookup" failure Change By: Nathanael Cole Summary: Improved error reporting for " segmentd segmented key lookup" failure Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-6023) Improved error reporting for "segmentd key lookup" failure
Title: Message Title Nathanael Cole created an issue Puppet / PUP-6023 Improved error reporting for "segmentd key lookup" failure Issue Type: New Feature Affects Versions: PUP 4.3.2 Assignee: Unassigned Created: 2016/03/08 3:26 PM Priority: Normal Reporter: Nathanael Cole When a hash key contains a dot in its name (which is illegal in Puppet 4, as mentioend in HI-485 and HI-496 ), puppet runs return an error similar to the following: "Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, Resolution type :hash is illegal when doing segmented key lookups at /etc/puppetlabs/puppet/environments/../../../filename.pp:8:32 on node [node name]" This ticket is requesting better clarification to save time troubleshooting future issues. Perhaps inclusion of the erroneous key value in the error output.
Jira (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Nathanael Cole updated an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Nathanael Cole CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1278) Undefined method "match" when using "facter -p pe_build" in 2015.2.3
Title: Message Title
Nathanael Cole updated an issue
Facter / FACT-1278
Undefined method "match" when using "facter -p pe_build" in 2015.2.3
Change By:
Nathanael Cole
Customer reported this bug, and I was able to immediately replicate it using a fresh vagrant box: {{ [root@pe-201523-master vagrant]# facter -p pe_build2015-11-18 20:31:25.944869 ERROR puppetlabs.facter - error while resolving custom fact "pe_version": undefined method `match' for nil:NilClass2015.2.3 }}The fact is returned at the CLI, accompanied by the above error
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1278) Undefined method "match" when using "facter -p pe_build" in 2015.2.3
Title: Message Title
Nathanael Cole created an issue
Facter / FACT-1278
Undefined method "match" when using "facter -p pe_build" in 2015.2.3
Issue Type:
Bug
Affects Versions:
FACT 3.1.1
Assignee:
Unassigned
Created:
2015/11/18 12:33 PM
Priority:
Normal
Reporter:
Nathanael Cole
Customer reported this bug, and I was able to immediately replicate it using a fresh vagrant box:
{{ [root@pe-201523-master vagrant]# facter -p pe_build 2015-11-18 20:31:25.944869 ERROR puppetlabs.facter - error while resolving custom fact "pe_version": undefined method `match' for nil:NilClass 2015.2.3 }}
The fact is returned at the CLI, accompanied by the above error
Add Comment
Jira (FACT-1278) Undefined method "match" when using "facter -p pe_build" in 2015.2.3
Title: Message Title
Nathanael Cole updated an issue
Facter / FACT-1278
Undefined method "match" when using "facter -p pe_build" in 2015.2.3
Change By:
Nathanael Cole
Customer reported this bug, and I was able to immediately replicate it using a fresh vagrant box: {{ [root@pe-201523-master vagrant]# facter -p pe_build2015-11-18 20:31:25.944869 ERROR puppetlabs.facter - error while resolving custom fact "pe_version": undefined method `match' for nil:NilClass2015.2.3 }} The fact is returned at the CLI, accompanied by the above error
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title
Nathanael Cole commented on PUP-2782
Re: Yumrepo target attribute does not work
Still a bug in 3.8.2.
On CentOS 6.6:
{{ yumrepo {'repo1': baseurl => "http://yumreposerver/yum/OracleLinux/OL6/1/base/i386", descr => 'Bobs Happy Fun Oracle Linux Repo', target => '/etc/yum.repos.d/bob/repo1.repo', ensure => present, enabled => false, gpgcheck => false, }
}}
This creates a "repo1.repo" in /etc/yum.repos.d/ instead of the specified /etc/yum.repos.d/bob/
If reposdir is set to /etc/yum.repos.d/bob/ in yum.conf then it gets placed in that dir instead.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-2782 Yumrepo target attribute does not work Change By: Nathanael Cole Affects Version/s: PUP 3.8.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2313) Package resources should use $title rather than $name to determine uniqueness
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-2313 Package resources should use $title rather than $name to determine uniqueness Change By: Nathanael Cole CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2313) Package resources should use $title rather than $name to determine uniqueness
Title: Message Title Nathanael Cole commented on PUP-2313 Re: Package resources should use $title rather than $name to determine uniqueness Customer reporting this today with PE 2015.2.1, any action on this issue? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5271) Windows user resource should not manage password unless specified
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-5271 Windows user resource should not manage password unless specified Change By: Nathanael Cole CS Priority: Minor Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5271) Windows user resource should not manage password unless specified
Title: Message Title Nathanael Cole commented on PUP-5271 Re: Windows user resource should not manage password unless specified Updated one of those fields, but the others are a bit... vague. I'm not entirely familiar with those priorities, as number systems tend to be confusing. In the 1-5 system, is 1 the most crucial, or is 5 the most crucial? Same with frequencies, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
