Jira (PUP-10859) Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode
Title: Message Title Trevor Vaughan commented on PUP-10859 Re: Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode Version 7.6.0-1 works properly in FIPS mode on EL8 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.384622.1611426826000.20610.1645390980046%40Atlassian.JIRA.
Jira (PUP-10859) Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode
Title: Message Title
Trevor Vaughan updated an issue
Puppet / PUP-10859
Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode
Change By:
Trevor Vaughan
*Puppet Version:* All *Puppet Server Version:* All *OS Name/Version:* CentOS and RHEL 8.3+ in FIPS modeCentOS and RHEL 8.3+, when running in FIPS mode, require SHA-256 signatures on both repository metadata and RPMs.StarLab has a [good summary of the issue|https://www.starlab.io/blog/adding-sha256-digests-to-rpms] and I can confirm that resigning the RPMs using a CentOS 8.3+ base container/image will allow for correct installation.*Desired Behavior:* Ability to install puppet RPMs on an EL8 system in FIPS mode.*Actual Behavior:* RPMs fail to install. *Docs:* An example of the failure can be found in the [pupmod-simp-pupmod beaker tests|https://gitlab.com/simp/pupmod-simp-pupmod/-/jobs/980280745#L4089]. *How To Test:*{code:java}fips-mode-setup --enablerebootfips-mode-setup --check (should say enabled)dnf -y install https://yum.puppet.com/puppet-release-el-8.noarch.rpmdnf -y install puppetserver{code}
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-10859) Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode
Title: Message Title Trevor Vaughan commented on PUP-10859 Re: Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode It looks like the solution was only a partial fix unfortunately: Error unpacking rpm package puppetserver-7.5.0-1.el8.noarch Cleanup : lua-libs-5.3.4-11.el8.x86_64 18/18 error: unpacking of archive failed on file /etc/puppetlabs/puppetserver/conf.d/auth.conf;61e5d5b8: cpio: Digest mismatch error: puppetserver-7.5.0-1.el8.noarch: install failed It is possible to work around this particular error by resigning things locally but that is not ideal since we lose the vendor signature. And, of course, you still can't install from the puppet repositories themselves. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11402) puppet lookup --explain fails out of the box starting with 7.13.1
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-11402 puppet lookup --explain fails out of the box starting with 7.13.1 Issue Type: Bug Affects Versions: PUP 7.13.1 Assignee: Unassigned Components: Hiera & Lookup Created: 2021/12/29 1:24 PM Priority: Major Reporter: Trevor Vaughan Starting with Puppet 7.13.1 (as installed via YUM for EL7) `puppet lookup --explain` now fails. puppet lookup --explain test Error: Failed to initialize SSL: The CA certificates are missing from '/etc/puppetlabs/puppet/ssl/certs/ca.pem' Error: Run `puppet agent -t` Error: Connection to https://puppet:8140/puppet-ca/v1 failed, trying next route: Request to https://puppet:8140/puppet-ca/v1 failed after 0.001 seconds: The CA certificates are missing from '/etc/puppetlabs/puppet/ssl/certs/ca.pem'
Jira (PUP-11402) puppet lookup --explain fails out of the box starting with 7.13.1
Title: Message Title Trevor Vaughan updated an issue Puppet / PUP-11402 puppet lookup --explain fails out of the box starting with 7.13.1 Change By: Trevor Vaughan Method Found: Needs Assessment Customer Feedback 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.428219.1640813061000.11057.1640813100153%40Atlassian.JIRA.
Jira (PUP-11001) puppet module install shows invalid message if existing modules are broken
Title: Message Title Trevor Vaughan updated an issue Puppet / PUP-11001 puppet module install shows invalid message if existing modules are broken Change By: Trevor Vaughan Affects Version/s: PUP 7.3.0 Affects Version/s: PUP 6.23.0 Affects Version/s: PUP 7.8.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.393444.1617202944000.99031.1628086620213%40Atlassian.JIRA.
Jira (PUP-11027) Filesync'd Augeas lenses should not overwrite system lenses
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-11027 Filesync'd Augeas lenses should not overwrite system lenses Issue Type: Bug Affects Versions: PUP 7.4.1 Assignee: Unassigned Components: Modules Created: 2021/04/15 7:17 AM Priority: Normal Reporter: Trevor Vaughan Puppet Version: All Puppet Server Version: All OS Name/Version: All It looks like augeas lenses that are filesync'd over to target nodes are placed into the default augeas path of /usr/share/augeas/lenses. Unfortunately, it doesn't seem to make them readable by all users which means that regular users may have augtool fail if the lens is not made world readable somehow. Desired Behavior: I would like Puppet sync'd lenses to be placed into a puppet-specific location and have the internal Augeas libraries use that path first so that system libraries are not altered. Add Comment
Jira (FACT-2929) Facter does not correctly detect that it is running inside of a podman container
Title: Message Title Trevor Vaughan created an issue Facter / FACT-2929 Facter does not correctly detect that it is running inside of a podman container Issue Type: Bug Affects Versions: FACT 4.0.44 Assignee: Unassigned Components: Facter 4 Created: 2021/01/28 7:02 AM Environment: Rootless podman EL8 instance. Priority: High Reporter: Trevor Vaughan Facter shows the system as physical even when running inside of a rootless podman container. The system should detect that it is inside of a container and, ideally, note that it is rootless/rootful. The following information seems relevant, but may not be a complete picture: There is a /run/.containerenv mountpoint The SELinux context of any of the root-level filesystems is container_file_t. The contents of /proc/self/cgroup contains libpod (rootful) The first two seem to be consistent and the third is the only way that I can tell to determine if you're rootful or rootless.
Jira (PUP-10859) Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-10859 Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode Issue Type: Bug Affects Versions: PUP 6.19.1, PUP 7.1.0, PUP 6.18.0 Assignee: Morgan Rhodes Created: 2021/01/23 10:33 AM Priority: Major Reporter: Trevor Vaughan Puppet Version: All Puppet Server Version: All OS Name/Version: CentOS and RHEL 8.3+ in FIPS mode CentOS and RHEL 8.3+, when running in FIPS mode, require SHA-256 signatures on both repository metadata and RPMs. StarLab has a good summary of the issue and I can confirm that resigning the RPMs using a CentOS 8.3+ base container/image will allow for correct installation. Desired Behavior: Ability to install puppet RPMs on an EL8 system in FIPS mode. Actual Behavior: RPMs fail to install. An example of the failure can be found in the pupmod-simp-pupmod beaker tests. Add Comment
Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title Trevor Vaughan commented on PUP-7541 Re: Explore removing export / collect / virtual / realize syntax Just found this ticket, but I also would like to be able to say X comes after all Packages without actually realizing them. Making this a set of functions might be more straightforward and non-breaking. It's not as puppet-y but I think people are pretty used to functions doing magic at this point. The only use cases that I've ever had for collectors are: Making things come before/after other things Performing resource overrides (key in many cases) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.191187.1494891335000.121336.1611259920031%40Atlassian.JIRA.
Jira (PUP-10847) "puppet facts show fact" output differs from "facter fact"
Title: Message Title Trevor Vaughan commented on PUP-10847 Re: "puppet facts show fact" output differs from "facter fact" I'd be happy with something more shell-friendly. For instance: Single Fact => Just the Value Complex Fact => JSON Multi Fact => Something easy to parse (single value separator would be good so it can be run through cut) It's a bit confusing, but the 90% use case is a single fact for scripting. Facter knows what it's returning so this shouldn't be too bad to implement. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.382201.1609880859000.108598.1609891200157%40Atlassian.JIRA.
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title Trevor Vaughan commented on PUP-10627 Re: write public information to puppet_dir/public Josh Cooper That information is sufficient to provide data as to how well automated/secured the system is over time (noop, etc...), what version (potentially exploitable) of puppet is being run, and the general load of the system. None of this information should be exposed by default to anyone besides root. Start locked down and allow for loosening restrictions if at all possible. To me, this information is like a system log. You don't expose your system logs to all users but you may allow some users, by group, to access certain logs for their job functions. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.369665.1597829487000.65984.1603885980096%40Atlassian.JIRA.
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title Trevor Vaughan commented on PUP-10627 Re: write public information to puppet_dir/public What's the use case for this? From what I'm seeing, it's a security violation based on pretty much any documentation that I can think of. By default, even reports should not be accessible to all users. If you want to share this information, it should be isolated to a specific group and then users should be added to that group for access. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.369665.1597829487000.65328.1603825920025%40Atlassian.JIRA.
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title Trevor Vaughan commented on PUP-10665 Re: Add weak dependencies to puppet resources Changed optionally to optional because it's easier to type Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371714.1599956556000.36286.1600184400027%40Atlassian.JIRA.
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title
Trevor Vaughan updated an issue
Puppet / PUP-10665
Add weak dependencies to puppet resources
Change By:
Trevor Vaughan
After [a long discussion in Slack|https://puppetcommunity.slack.com/archives/C0W1X7ZAL/p1599682853112600], I was asked to create a ticket around adding 'weak dependencies' to puppet resources. Weak dependencies work like the {{wants}} keyword in {{systemd}} in that resources will be ordered after other resources that they {{want}} but failures in earlier resources will not cause cascading errors into resources that {{want}} them.This would be useful in cases like the {{yumrepo}} resource which may cascade down to packages that do not actually reside in that repository.Per the Slack discussion, it looks like implementing this in the compiler is going to be the best case for backwards compatibility and could constitute a non-breaking feature enhancement.An example of what this might look like is: (updated from comments below) {code} exec { 'ping host': command => 'ping 1.2.3.4'}exec { 'ping other host': command => 'ping 2.3.4.5'}file { '/tmp/foo': owner => 'root', mode => '0640', requires => [ File['/tmp'], Exec['ping host'] ], # Add these items to the autorequires list optionally_requires optional_requires => [File['/dev/shm']], # Do not fail if these resources fail wants => [ Exec['ping other host'] ]}{code} The pairings would be: * {{ optionally_requires optional_requires }} => {{ optionally_notifies optional_notifies }}* {{wants}} => {{wanted_by}}Potential symbols (Stretch Goal) : * {{ optionally_requires optional_requires }} => {{*>}}** Denotes the 'match anything' regex marker* {{wants}} => {{+>}}** Denotes a broken line == broken dependencyIn this case, {{requires}} would work as usual and {{wants}} would use the resource if present, ignore it if not, and not cascade resource failures.If something exists in both {{requires}} and {{wants}} then the stronger dependency ({{requires}}) should win.
Add Comment
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title
Trevor Vaughan updated an issue
Puppet / PUP-10665
Add weak dependencies to puppet resources
Change By:
Trevor Vaughan
After [a long discussion in Slack|https://puppetcommunity.slack.com/archives/C0W1X7ZAL/p1599682853112600], I was asked to create a ticket around adding 'weak dependencies' to puppet resources. Weak dependencies work like the {{wants}} keyword in {{systemd}} in that resources will be ordered after other resources that they {{want}} but failures in earlier resources will not cause cascading errors into resources that {{want}} them.This would be useful in cases like the {{yumrepo}} resource which may cascade down to packages that do not actually reside in that repository.Per the Slack discussion, it looks like implementing this in the compiler is going to be the best case for backwards compatibility and could constitute a non-breaking feature enhancement.An example of what this might look like is: (updated from comments below) {code} exec { 'ping host': command => 'ping 1.2.3.4'}exec { 'ping other host': command => 'ping 2.3.4.5'} file { '/tmp/foo': owner => 'root', mode => '0640', requires => [ File['/tmp'], Exec[' foo ping host '] ] , wants # Add these items to the autorequires list optionally_requires => [ File['/ etc dev / bar shm '] ] , # Do not fail if these resources fail wants => [ Exec[' baz ping other host '] ]}{code} The pairings would be:* {{optionally_requires}} => {{optionally_notifies}}* {{wants}} => {{wanted_by}}Potential symbols:* {{optionally_requires}} => {{*>}}** Denotes the 'match anything' regex marker* {{wants}} => {{+>}}** Denotes a broken line == broken dependency In this case, {{requires}} would work as usual and {{wants}} would use the resource if present, ignore it if not, and not cascade resource failures.If something exists in both {{requires}} and {{wants}} then the stronger dependency ({{requires}}) should win.
Add Comment
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title Trevor Vaughan commented on PUP-10665 Re: Add weak dependencies to puppet resources I like the idea above from Henrik Lindberg. It is true that optionally_requires is not the same as isolated_before. (I warned people that I was bad at naming things). Technically, optionally_before is what I expected the regular before to be when I started using the language but I think that ship has sailed. Even though it's a bit more wordy, I think that this is probably better than my original idea. The optionally_ stuff is actually easy to implement because it's identical to the auto (autorequires, etc...) portions of custom types that already exist. I think may be borrowing from systemd and using wants and wanted_by would be a bit easier to wrap our heads around than the isolated_* naming scheme. I'll update the description with these ideas. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371714.1599956556000.36162.1600171980061%40Atlassian.JIRA.
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title
Trevor Vaughan updated an issue
Puppet / PUP-10665
Add weak dependencies to puppet resources
Change By:
Trevor Vaughan
After [a long discussion in Slack|https://puppetcommunity.slack.com/archives/C0W1X7ZAL/p1599682853112600], I was asked to create a ticket around adding 'weak dependencies' to puppet resources. Weak dependencies work like the {{wants}} keyword in {{systemd}} in that resources will be ordered after other resources that they {{want}} but failures in earlier resources will not cause cascading errors into resources that {{want}} them.This would be useful in cases like the {{yumrepo}} resource which may cascade down to packages that do not actually reside in that repository.Per the Slack discussion, it looks like implementing this in the compiler is going to be the best case for backwards compatibility and could constitute a non-breaking feature enhancement. An example of what this might look like is:{code}file { '/tmp/foo': owner => 'root', mode => '0640', requires => [ File['/tmp'], Exec['foo'] ] wants => [ File['/etc/bar'], Exec['baz'] ]}{code}In this case, {{requires}} would work as usual and {{wants}} would use the resource if present, ignore it if not, and not cascade resource failures.If something exists in both {{requires}} and {{wants}} then the stronger dependency ({{requires}}) should win.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-10665 Add weak dependencies to puppet resources Issue Type: New Feature Assignee: Unassigned Components: Language Created: 2020/09/12 5:22 PM Priority: Normal Reporter: Trevor Vaughan After a long discussion in Slack, I was asked to create a ticket around adding 'weak dependencies' to puppet resources. Weak dependencies work like the wants keyword in systemd in that resources will be ordered after other resources that they want but failures in earlier resources will not cause cascading errors into resources that want them. This would be useful in cases like the yumrepo resource which may cascade down to packages that do not actually reside in that repository. Per the Slack discussion, it looks like implementing this in the compiler is going to be the best case for backwards compatibility and could constitute a non-breaking feature enhancement. Add Comment
Jira (PUP-3922) Preserve modulepath structure during pluginsync
Title: Message Title Trevor Vaughan commented on PUP-3922 Re: Preserve modulepath structure during pluginsync Issues with things like client side namespacing have been problematic in the module space for years. Honestly, I think that everything should be namespaced at this point and that it should all be completely unambiguous where possible. In my opinion, one of the main issues is that this causes users to try modules form the Forge but either reject them, or fork them, due to namespace collisions. Fixing this issue would be a boon for the overall reusability of the module space in general. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.65973.1422487314000.49057.1588095180427%40Atlassian.JIRA.
Jira (PUP-10404) Puppet apply can no longer copy directories recursively from a 'puppet:///' file source
Title: Message Title
Trevor Vaughan created an issue
Puppet / PUP-10404
Puppet apply can no longer copy directories recursively from a 'puppet:///' file source
Issue Type:
Bug
Affects Versions:
PUP 6.14.0
Assignee:
Unassigned
Components:
Catalog Application
Created:
2020/03/31 5:55 PM
Priority:
Critical
Reporter:
Trevor Vaughan
Puppet Version: 6.14.0 (6.13 works) Puppet Server Version: N/A OS Name/Version: EL7 Recursive directory copies from modules no longer appear to function in 6.14.0. Repeater:
mkdir -p testmod/{files,manifests}
mkdir testmod/files/test
echo 'one' > testmod/files/test/one
echo 'two' > testmod/files/test/two
Jira (PUP-2368) using booleans result in unmanaged property
Title: Message Title Trevor Vaughan commented on PUP-2368 Re: using booleans result in unmanaged property Removing the inheritance on Puppet::Property::Boolean and adding the following appears to do the trick: def should return nil unless defined?(@should) (@should - [true,:true]).empty? end It's possible that the underlying puppet code could detect whether or not the thing is a boolean in the native should code and "do the right thing". Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-2368) using booleans result in unmanaged property
Title: Message Title Trevor Vaughan commented on PUP-2368 Re: using booleans result in unmanaged property The Resource API hasn't reached parity with the underlying API so this will still need to be addressed at some point. Documentation outside of this ticket would be great. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.33254.1398535206000.16472.1584638700088%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Trevor Vaughan commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Josh Cooper Yep, I tried that for about 10 minutes, realized that I was lost, and posted what I had here :-| Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.302978.1554294806000.765.1582742820224%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Trevor Vaughan commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Just checking to see if there has been any progress on this and/or if the workaround is acceptable for the short term since it doesn't actually make anything slower than the non-cached version. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.302978.1554294806000.581.1582735500374%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Trevor Vaughan commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Thomas Hallgren I may not have been clear. While it is crazy slow, it is no slower than if you remove the entire cache and run without an error. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.302978.1554294806000.10715.1580743260267%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Trevor Vaughan commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated While I completely agree with Henrik Lindberg's assessment that my patch is completely the wrong way to do things, if this isn't going to get much attention in the near future, could it be implemented just to prevent things from crashing? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.302978.1554294806000.10398.1580739600291%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Trevor Vaughan commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated So, after much poking around with Charlie Sharpsteen on Slack, I've determined a few things. puppet apply is crazy slow for some reason The following code snippet appears to work around the issue but I'll leave it to Henrik Lindberg to tell me if it makes any sort of sense. diff --git a/lib/puppet/pops/loader/base_loader.rb b/lib/puppet/pops/loader/base_loader.rb index d3c80b63e7..9691113c1b 100644 --- a/lib/puppet/pops/loader/base_loader.rb +++ b/lib/puppet/pops/loader/base_loader.rb @@ -70,8 +70,11 @@ class BaseLoader < Loader def set_entry(typed_name, value, origin = nil) # It is never ok to redefine in the very same loader unless redefining a 'not found' entry = @named_values[typed_name] + +user_mode_skip = (entry && !entry.value.nil? && Puppet.run_mode.name == :user) +
Jira (PUP-10262) Attempt to redefine entity regression
Title: Message Title Trevor Vaughan commented on PUP-10262 Re: Attempt to redefine entity regression Downgraded to 5.5.18 and no issues. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.344561.1580500988000.8723.1580502420042%40Atlassian.JIRA.
Jira (PUP-10262) Attempt to redefine entity regression
Title: Message Title Trevor Vaughan commented on PUP-10262 Re: Attempt to redefine entity regression Just did a downgrade loop through all versions of Puppet 6 on EL8 and every version has the bug. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.344561.1580500988000.8722.1580502360036%40Atlassian.JIRA.
Jira (PUP-10262) Attempt to redefine entity regression
Title: Message Title
Trevor Vaughan updated an issue
Puppet / PUP-10262
Attempt to redefine entity regression
Change By:
Trevor Vaughan
*Puppet Version: 6.12.0* *Puppet Server Version: N/A* *OS Name/Version: EL8*When using voxpupuli/firewalld code that works in Puppet , I am getting the following error in Puppet 6. NOTE: The same code works on EL7!{code:java} Error: Could not autoload puppet/type/firewalld_service: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/firewalld_service'. Set at unknown locationError: Could not autoload puppet/type/firewalld_zone: Could not autoload puppet/type/firewalld_service: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/firewalld_service'. Set at unknown locationError: Parameter before failed on Service[firewalld]: Could not autoload puppet/type/firewalld_zone: Could not autoload puppet/type/firewalld_service: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/firewalld_service'. Set at unknown location (file: /etc/puppetlabs/code/environments/production/modules/firewalld/manifests/init.pp, line: 79){code}This appears to be related to having run {{puppet generate}} types on the system.Removing the .resource_types directory fixes the puppet run but is not an acceptable solution.*Desired Behavior:*Puppet run should succeed*Actual Behavior:* Posted above.Works on EL7 with identical code.Works on EL8 with Puppet 5 with identical code.There may be one, or two, errors based on the version of Puppet 6 that is installed.CC: [~henrik.lindberg] since this deals with {{generate}} types. *Full Repeater*{code:java}git clone https://github.com/simp/pupmod-simp-pupmodPUPPET_VERSION='~> 6.0' bundle updatePUPPET_VERSION='~>6.0' BEAKER_destroy=onpass rake beaker:suites..wait for failure..cd .vagrant/beaker_vagrant_files/default.ymlvagrant ssh puppet.el8sudo su -cd /tmpgrep pupmod::master *.pp* | head -1puppet apply rm -rf /etc/puppetlabs/code/environments/production/.resource_typespuppet apply puppet generate typespuppet apply {code}
Add Comment
Jira (PUP-10262) Attempt to redefine entity regression
Title: Message Title Trevor Vaughan updated an issue Puppet / PUP-10262 Attempt to redefine entity regression Change By: Trevor Vaughan Priority: Normal Blocker Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.344561.1580500988000.8675.1580501100151%40Atlassian.JIRA.
Jira (PUP-10262) Attempt to redefine entity regression
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-10262 Attempt to redefine entity regression Issue Type: Bug Affects Versions: PUP 6.12.0 Assignee: Unassigned Components: Compiler Created: 2020/01/31 12:03 PM Priority: Normal Reporter: Trevor Vaughan Puppet Version: 6.12.0 Puppet Server Version: N/A OS Name/Version: EL8 When using voxpupuli/firewalld code that works in Puppet , I am getting the following error in Puppet 6. NOTE: The same code works on EL7! Error: Could not autoload puppet/type/firewalld_service: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/firewalld_service'. Set at unknown location Error: Could not autoload puppet/type/firewalld_zone: Could not autoload puppet/type/firewalld_service: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/firewalld_service'. Set at unknown location Error: Parameter before failed on Service[firewalld]: Could not autoload puppet/type/firewalld_zone: Could not autoload puppet/type/firewalld_service: Attempt
Jira (PUP-10259) Hiera cannot interpolate non-string values
Title: Message Title Trevor Vaughan commented on PUP-10259 Re: Hiera cannot interpolate non-string values Thomas Hallgren Seems reasonable to me. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.244421.1522942982000.3211.1580237880452%40Atlassian.JIRA.
Jira (PUP-10239) Modules should have the ability to add data to the Hiera layer of the module and have it affect other modules default lookup settings.
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-10239 Modules should have the ability to add data to the Hiera layer of the module and have it affect other modules default lookup settings. Issue Type: Improvement Assignee: Unassigned Components: Language Created: 2020/01/17 10:53 AM Priority: Normal Reporter: Trevor Vaughan Puppet Version: 5+ Puppet Server Version: 5+ OS Name/Version: Any When creating profiles and/or roles, I would like the ability to be able to have my module data affect the default lookups of other modules. Desired Behavior: If I have a webserver profile, I would like to be able to add data in the modules' hiera layer to affect the defaults for the apache class or the nginx class without adding clutter to my puppet manifests. I imagine that this would be a setting that would have to be explicitly enabled in the module data to tell HIera to delve into the modules for all defaults unless a higher level default is found. Actual Behavior: Functionality currently does not exist CC: Henrik Lindberg Add Comment
Jira (PUP-10105) regression: puppet resource --to_yaml should not emit puppet class tags
Title: Message Title
Trevor Vaughan commented on PUP-10105
Re: regression: puppet resource --to_yaml should not emit puppet class tags
This is causing issues with my acceptance tests and breaks YAML.safe_load (which is a best practice). Fundamentally, 99% of the time, I just want the data when using puppet resource. Example:
require 'yaml'
test = %x{puppet resource -y cron}
YAML.load(test) # breaks
require 'puppet'
YAML.safe_load(test) # breaks
YAML.load(test) # works, but is unsafe
Jira (PUP-9963) The 'value' field of 'selboolean' should accept Booleans
Title: Message Title Trevor Vaughan commented on PUP-9963 Re: The 'value' field of 'selboolean' should accept Booleans Ciprian Badescu Honestly, I just wanted to be able to pass true or false instead of on and off to the value property. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.320668.1565704234000.16221.1572614940070%40Atlassian.JIRA.
Jira (PDOC-293) Would like a documentation header generation function for puppet strings
Title: Message Title Trevor Vaughan created an issue Puppet Strings / PDOC-293 Would like a documentation header generation function for puppet strings Issue Type: Improvement Assignee: Unassigned Created: 2019/10/04 11:27 AM Priority: Normal Reporter: Trevor Vaughan It is time consuming to repeat all of the parameters for a given module in the header of the module when first creating documentation. It would be great if there could be a command such as puppet strings --generate-header that would output an appropriate header template to STDOUT. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9963) The 'value' field of 'selboolean' should accept Booleans
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-9963 The 'value' field of 'selboolean' should accept Booleans Issue Type: Improvement Affects Versions: PUP 6.7.2, PUP 5.5.16 Assignee: Unassigned Components: Modules Created: 2019/08/13 6:50 AM Priority: Normal Reporter: Trevor Vaughan Puppet Version: Any Puppet Server Version: Any OS Name/Version: Linux with SELinux Presently, the selboolean native type accepts either on or off as valid entries for the value parameter. Desired Behavior: The value parameter should accept Boolean values since they will reduce the need for simple translation statements every time selboolean is used. Add Comment
Jira (PUP-9960) Puppet::Util::Execution.execute('command') does not return a Puppet::ExecutionFailure on Windows
Title: Message Title
Trevor Vaughan created an issue
Puppet / PUP-9960
Puppet::Util::Execution.execute('command') does not return a Puppet::ExecutionFailure on Windows
Issue Type:
Bug
Affects Versions:
PUP 5.5.16
Assignee:
Henrik Lindberg
Components:
Functions, Windows
Created:
2019/08/12 6:40 PM
Priority:
Normal
Reporter:
Trevor Vaughan
Puppet Version: 5.5.16 Puppet Server Version: N/A OS Name/Version: Windows 2012r2 Running Puppet::Util::Execution.execute('foo') should raise a Puppet::ExecutionFailure exception but, instead raises Errno::ENOENT since the command is not found. This appears to go against the documented API of the function and makes creating code that is safe for all operating systems difficult. Desired Behavior: Always raise Puppet::ExecutionFailure on an error. Actual Behavior: Errno::ENOENT is raised.
Add Comment
Jira (PUP-4647) Yum provider uses rpm -e to uninstall packages
Title: Message Title Trevor Vaughan commented on PUP-4647 Re: Yum provider uses rpm -e to uninstall packages Josh Cooper Looks like this may actually be a regression: https://tickets.puppetlabs.com/browse/PUP-1198 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.81272.1432290276000.32213.1564106880159%40Atlassian.JIRA.
Jira (PUP-4647) Yum provider uses rpm -e to uninstall packages
Title: Message Title Trevor Vaughan commented on PUP-4647 Re: Yum provider uses rpm -e to uninstall packages This is still an issue. Discovered when attempting to remove `yp-tools` and `ypbind` Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.81272.1432290276000.24003.1563662100195%40Atlassian.JIRA.
Jira (PUP-9793) Users should be able to disable warnings on unresolved module dependencies at the command line.
Title: Message Title
Trevor Vaughan updated an issue
Puppet / PUP-9793
Users should be able to disable warnings on unresolved module dependencies at the command line.
Change By:
Trevor Vaughan
When running {{puppet}} apply by hand, it is quite irritating to see 'unresolved dependency' warnings on modules for components that your system does not require and that you do not include deliberately.I would like to be able to disable only this warning but retain all other warnings so that they are not lost in the noise.Example output with working code (note the Warning that's lost in the mess of uresolved deps):{code:java} puppet apply /tmp/apply_manifest.pp.XopaFKWarning: ModuleLoader: module 'simp_options' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'simplib' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'compliance_markup' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'simp' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'pupmod' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'aide' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'auditd' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'clamav' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'deferred_resources' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available)Warning: ModuleLoader: module 'ntpd' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'pam' has unresolved dependencies - it will only see
Jira (PUP-9793) Users should be able to disable warnings on unresolved module dependencies at the command line.
Title: Message Title
Trevor Vaughan updated an issue
Puppet / PUP-9793
Users should be able to disable warnings on unresolved module dependencies at the command line.
Change By:
Trevor Vaughan
When running {{puppet}} apply by hand, it is quite irritating to see 'unresolved dependency' warnings on modules for components that your system does not require and that you do not include deliberately.I would like to be able to disable only this warning but retain all other warnings so that they are not lost in the noise. Example output with working code (note the Warning that's lost in the mess of uresolved deps):{code:java}puppet apply /tmp/apply_manifest.pp.XopaFKWarning: ModuleLoader: module 'simp_options' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'simplib' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'compliance_markup' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'simp' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'pupmod' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'aide' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'auditd' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'clamav' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'deferred_resources' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available)Warning: ModuleLoader: module 'ntpd' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n (file & line not available) Warning: ModuleLoader: module 'pam' has unresolved dependencies - it will only see
Jira (PUP-9793) Users should be able to disable warnings on unresolved module dependencies at the command line.
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-9793 Users should be able to disable warnings on unresolved module dependencies at the command line. Issue Type: New Feature Affects Versions: PUP 6.4.2 Assignee: Unassigned Components: Catalog Application Created: 2019/06/21 10:25 AM Priority: Normal Reporter: Trevor Vaughan When running puppet apply by hand, it is quite irritating to see 'unresolved dependency' warnings on modules for components that your system does not require and that you do not include deliberately. I would like to be able to disable only this warning but retain all other warnings so that they are not lost in the noise. Add Comment
Jira (PUP-9749) puppet generate types should be run when the puppetserver is upgraded
Title: Message Title Trevor Vaughan commented on PUP-9749 Re: puppet generate types should be run when the puppetserver is upgraded Given the comment from Henrik Lindberg, it would seem that the safe thing to do would be to run it and give people the ability to opt-out. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312214.1560355314000.50124.1560805020216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9749) puppet generate types should be run when the puppetserver is upgraded
Title: Message Title Trevor Vaughan commented on PUP-9749 Re: puppet generate types should be run when the puppetserver is upgraded Josh Cooper I didn't either but it definitely was. It was with a stack of SIMP modules, didn't debug past the fact that rerunning puppet generate types fixed everything. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312214.1560355314000.47075.1560473520172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9749) puppet generate types should be run when the puppetserver is upgraded
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-9749 puppet generate types should be run when the puppetserver is upgraded Issue Type: Bug Assignee: Unassigned Created: 2019/06/12 9:01 AM Priority: Normal Reporter: Trevor Vaughan When the puppetserver is upgraded, existing artifacts generated by puppet generate types may no longer work and so it needs to be re-run automatically on upgrade. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Trevor Vaughan commented on PUP-1298 Re: manage_membership for unix groups provider The gpasswd module still works and Puppet, Inc is welcome to pick up the code as it's Apache licensed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.22682.1388437397000.4319.1557847200923%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9055) Compile catalogs on demand with user-specified facts
Title: Message Title Trevor Vaughan commented on PUP-9055 Re: Compile catalogs on demand with user-specified facts Josh Cooper I'm not sure if this can be done, but would it be possible to generate a fact template based on a target manifest set? Basically, if I need a bunch of facts, it would be nice to have a 'fill in the blanks' YAML file that could be output by puppet itself. Ideally, you could amend the file so that it adds on new facts as the compile gets further along. I'm assuming that this would be an extension to the Facter hooks in Puppet. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Trevor Vaughan commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module Ben Ford That seems like a tie from data to logic to me (and likely to get confusing). Why not just make assert_private() a native function and have Strings just pick up the fact that the class has that call in it? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDOC-171) generate the hiera keynames to use for parameterised classes
Title: Message Title Trevor Vaughan commented on PDOC-171 Re: generate the hiera keynames to use for parameterised classes Actually, thinking about this, it might be a LOT easier than going 'full Hiera': If the hiera path has interpolation, the strings value becomes see in module data If it does not, return the value That should be it, right? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDOC-171) generate the hiera keynames to use for parameterised classes
Title: Message Title Trevor Vaughan commented on PDOC-171 Re: generate the hiera keynames to use for parameterised classes Henrik Lindberg How difficult would it be to just get defaults and not follow any logical paths? This is what is blocking us right now from putting all of our defaults in module data. Also, is it actually a good idea to put all defaults in module data? This seems to be less readable and 'easy to use' for new users. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-5880) Support optional dependencies in Metadata.json
Title: Message Title Trevor Vaughan commented on PUP-5880 Re: Support optional dependencies in Metadata.json Henrik Lindberg What do you think of the approach used by the referenced simplib function? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Trevor Vaughan commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module Henrik Lindberg Completely get how to do it right now but it gets confusing for end users/maintainers since you have to use inheritance to get the behavior that this would provide. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title
Trevor Vaughan commented on PUP-523
Re: Make it possible to declare classes, defines and functions (and more) as private to a module
Exactly, yes. Also:
<| Foo |> {
y => 20
} # error, y is a constant
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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
Jira (PUP-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Trevor Vaughan commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module Henrik Lindberg I was thinking for defined types as well. It would prevent anything from ever modifying that parameter. So ASL would ignore it, resource collectors would ignore it, etc... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Trevor Vaughan commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module Henrik Lindberg Just had this thought... how about a Const Data Type that marks a parameter as immutable? It doesn't solve all of the proposed issues but it seems reasonable in terms of the data typing system and understandability. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9315) Exec resources require output redirection to execute as a disconnected process
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-9315 Exec resources require output redirection to execute as a disconnected process Issue Type: Bug Affects Versions: PUP 5.5.8 Assignee: Henrik Lindberg Components: Catalog Application Created: 2018/11/15 11:58 AM Priority: Normal Reporter: Trevor Vaughan Puppet Version: All 5.X Puppet Server Version: All 5.X OS Name/Version: Red Hat/CentOS/OEL 6 and 7 Something changed between puppet 4 and puppet 5 where exec resources now require output redirection to be executed in the background. This can be used to execute activities that may be long running but should not interrupt the Puppet process since nothing depends on the success of the activity. An example of this is restarting the network without interrupting the Puppet run (which would be bad). A practical example can be found at https://github.com/simp/pupmod-simp-network/blob/master/manifests/init.pp#L23-L31 Desired Behavior: Puppet exec resources should not require arbitrary output redirection to be able to run a command in the background. Alternatively, a parameter could be added to exec that notes that the command should be run in the background and detached (this would be preferred). Actual Behavior: Arbitrary output redirection is required to run processes in the background. I've assigned this to Henrik Lindberg since I believe that we spoke about it on Slack at some point and he may have more relevant information from that time period.
Jira (PUP-9303) A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC
Title: Message Title Trevor Vaughan commented on PUP-9303 Re: A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC Henrik Lindberg If you erase the very first comment in the file and then validate it, it works fine which leads me to believe that it is a parser issue. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9303) A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC
Title: Message Title Trevor Vaughan commented on PUP-9303 Re: A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC Henrik Lindberg Sorry, the following should fail appropriately: git clone https://github.com/simp/pupmod-simp-simp_pki_service cd pupmod-simp-simp_pki_service git checkout d07265e253bb2cb11314dbb962043a21a2cbad05 puppet parser validate manifests/kra.pp I agree that there are no syntax errors in the file, that's why it seems to be a parser bug. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9303) A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC
Title: Message Title
Trevor Vaughan updated an issue
Puppet / PUP-9303
A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC
Change By:
Trevor Vaughan
*Puppet Version:* Anything greater than 5.X*Puppet Server Version:* N/A*OS Name/Version:* N/ADownload the {{simp_pki_service}} module from https://github.com/simp/pupmod-simp-simp_pki_service and run {{puppet parser validate manifests/kra.pp}}. Use {{d07265e253bb2cb11314dbb962043a21a2cbad05}} for the breaking behavior. Changing the {{fact}} call to a local variable did not show any issues. *Desired Behavior:*No validation errors should be shown (just as in Puppet 4)*Actual Behavior:*Puppet parser validation fails with a syntax error in the HEREDOC at line 123.Note: Removing the only line in the *comments* section of the document causes the validation to no longer fail.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google
Jira (PUP-9303) A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC
Title: Message Title Trevor Vaughan commented on PUP-9303 Re: A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC Henrik Lindberg Apologies, apparently a workaround got put in place. Try this one: https://github.com/simp/pupmod-simp-simp_pki_service/commit/d07265e253bb2cb11314dbb962043a21a2cbad05 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9303) A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC
Title: Message Title
Trevor Vaughan updated an issue
Puppet / PUP-9303
A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC
Change By:
Trevor Vaughan
*Puppet Version:* Anything greater than 5.X*Puppet Server Version:* N/A*OS Name/Version:* N/ADownload the {{simp_pki_service}} module from https://github.com/simp/pupmod-simp-simp_pki_service and run {{puppet parser validate manifests/kra.pp}}.*Desired Behavior:*No validation errors should be show shown (just as in Puppet 4)*Actual Behavior:*Puppet parser validation fails with a syntax error in the HEREDOC at line 123.Note: Removing the only line in the *comments* section of the document causes the validation to no longer fail.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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
Jira (PUP-9303) A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-9303 A file with a comment greater than 79 characters causes validation errors in an embedded HEREDOC Issue Type: Bug Affects Versions: PUP 6.0.4, PUP 6.0.3, PUP 6.0.2, PUP 6.0.1, PUP 6.0.0, PUP 5.5.8, PUP 5.5.7, PUP 5.5.6, PUP 5.5.3, PUP 5.5.2 Assignee: Henrik Lindberg Components: Compiler Created: 2018/11/06 8:02 AM Priority: Normal Reporter: Trevor Vaughan Puppet Version: Anything greater than 5.X Puppet Server Version: N/A OS Name/Version: N/A Download the simp_pki_service module from https://github.com/simp/pupmod-simp-simp_pki_service and run puppet parser validate manifests/kra.pp. Desired Behavior: No validation errors should be show (just as in Puppet 4) Actual Behavior: Puppet parser validation fails with a syntax error in the HEREDOC at line 123. Note: Removing the only line in the comments section of the document causes the validation to no longer fail. Add Comment
Jira (BOLT-755) Bolt should support multi-file tasks
Title: Message Title Trevor Vaughan commented on BOLT-755 Re: Bolt should support multi-file tasks Ah, right. I keep forgetting SSH in a loop. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-755) Bolt should support multi-file tasks
Title: Message Title Trevor Vaughan commented on BOLT-755 Re: Bolt should support multi-file tasks Does this not work on Windows? https://ruby-doc.org/stdlib-2.5.1/libdoc/zlib/rdoc/Zlib.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-755) Bolt should support multi-file tasks
Title: Message Title Trevor Vaughan commented on BOLT-755 Re: Bolt should support multi-file tasks If these are text files (and I don't know why they wouldn't be), I think they should be zipped, compressed, and shipped as a bundle. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9036) Setting the client side environment to one that does not exist on the server causes the catalog to fail compilation
Title: Message Title Trevor Vaughan commented on PUP-9036 Re: Setting the client side environment to one that does not exist on the server causes the catalog to fail compilation Josh Cooper Custom ENC so I'm not sure that's a thing. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9036) Setting the client side environment to one that does not exist on the server causes the catalog to fail compilation
Title: Message Title
Trevor Vaughan created an issue
Puppet / PUP-9036
Setting the client side environment to one that does not exist on the server causes the catalog to fail compilation
Issue Type:
Bug
Affects Versions:
PUP 4.10.12
Assignee:
Unassigned
Created:
2018/08/02 7:05 AM
Priority:
Major
Reporter:
Trevor Vaughan
Puppet Version: 4.10.12 Puppet Server Version: 2.8.1 OS Name/Version: CentOS 6 and 7 If you are running an ENC and set the client's configuration on the host to a non-existent environment, the puppet compile will fail. If set to an existing environment, the ENC will correct it and the compile will not fail. Desired Behavior: The puppet compile should use the environment specified on the server for the entire transaction. Actual Behavior:
Error: Could not retrieve catalog from remote server: Find /puppet/v3/catalog/my.host.name?environment=foo_format=pson=%257B%2522name%2522%... resulted in 404 with the message: {"message":"Not Found: Could not find environment 'foo'","issue_kind":"RUNTIME_ERROR"}
Jira (BOLT-57) Download a file
Title: Message Title Trevor Vaughan commented on BOLT-57 Re: Download a file Here's my use case. Feel free to steal the code with attribution. https://github.com/simp/rubygem-simp-beaker-helpers/blob/master/lib/simp/beaker_helpers.rb#L31-L71 Case 1: I'm pointing at something in docker on my local host -> Use docker cp because fast Case 2: I have rsync on both ends -> Use it because fast Otherwise: Fall back to ssh Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-5880) Support optional dependencies in Metadata.json
Title: Message Title
Trevor Vaughan commented on PUP-5880
Re: Support optional dependencies in Metadata.json
I've implemented a version of this at https://github.com/simp/pupmod-simp-simplib/pull/148. The idea is that the calling code will become aware of the optional dependencies and be able to tell the user exactly what needs to be done in order to get the requirement met. For instance:
if $facts['operatingsystem'] == 'RedHat' {
simplib::assert_optional_dependency('puppet/yum')
}
This will look for the puppet/yum dependency and grab the release requirements from the metadata.json file. This means that you can actually have different scenarios based on what is present in your environment (if you so choose) and not have to create specific scenarios if you want to support multiple underlying implementations.
Add Comment
Jira (PUP-3834) remove webrick/rack support from Puppet
Title: Message Title Trevor Vaughan commented on PUP-3834 Re: remove webrick/rack support from Puppet Eric Sorenson It looks like it might be promising once the issues mentioned in the ticket are complete. I definitely need to be able to pass in facts and/or trusted facts, etc... without a PuppetDB in place. For instance, I would occasionally spin up just a compiler in Beaker to make sure things worked properly. My tests can take so much time to run, the slight delay compared with the overhead of the java stack was very much worth it. Being able to have it just "figure things out" and compile would be great. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3834) remove webrick/rack support from Puppet
Title: Message Title Trevor Vaughan commented on PUP-3834 Re: remove webrick/rack support from Puppet Eric Sorenson Would it be possible to get an unsupported face posted somewhere for the JRuby vs Ruby bug testing. I haven't hit these issues often, but when I do they're really difficult to figure out without the alternative. The containerized stack is fine but still uses far more resources than the simple webrick server. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3834) remove webrick/rack support from Puppet
Title: Message Title Trevor Vaughan commented on PUP-3834 Re: remove webrick/rack support from Puppet Eric Sorenson Is there a rationale discussion behind this one? I get removing Rails support but the webrick support has been REALLY handy for testing and debugging some of the Ruby guts. It has also been the only way that I've been able to successfully figure out if something was a regular bug vs a JRuby bug (which is VERY important to know). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-599) Hiera cannot interpolate non-string values
Title: Message Title Trevor Vaughan commented on HI-599 Re: Hiera cannot interpolate non-string values Henrik Lindberg I think that scope should work the same way as alias. It makes sense. I can see that some people might rely on that but that seems like a bug and should be treated as such. In theory, your Hiera data is getting passed into your classes and everything should be strongly typed at this point (hopefully). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-599) Hiera cannot interpolate non-string values
Title: Message Title Trevor Vaughan commented on HI-599 Re: Hiera cannot interpolate non-string values Henrik Lindberg Unfortunately, using scope still results in a String instead of a Boolean value. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-599) Hiera cannot interpolate non-string values
Title: Message Title Trevor Vaughan commented on HI-599 Re: Hiera cannot interpolate non-string values Henrik Lindberg Yes, unfortunately, that doesn't work with facts. Since the use of typed facts is now the norm, Hiera should be able to have a way to ensure that the data type of facts is preserved. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1814) Mountpoints Fact available space does not accurately reflect disk usage
Title: Message Title Trevor Vaughan commented on FACT-1814 Re: Mountpoints Fact available space does not accurately reflect disk usage Charlie Sharpsteen Thanks! Is there a whitelist mode or do I need to implement my own custom fact to just get the "usual suspects" without running off the rails into insanity? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1814) Mountpoints Fact available space does not accurately reflect disk usage
Title: Message Title Trevor Vaughan commented on FACT-1814 Re: Mountpoints Fact available space does not accurately reflect disk usage Since you're messing around with mountpoints...there needs to be some way to exclude mountpoints from fact gathering. Some sites with large storage needs may have 1024+ LUNs and the facter run querying all of them is not a good thing. On the point at hand, why not report both? Add a new fact that reports 'unprivileged space' or something. That way, it's backwards compatible and you don't break things for people that run facter as a non-root user (please don't break things for non-root users). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-599) Hiera cannot interpolate non-string values
Title: Message Title
Trevor Vaughan commented on HI-599
Re: Hiera cannot interpolate non-string values
It would be ideal if, instead of overriding particular lookups at the configuration layer, that this could be exposed at interpolation time so that it is less confusing for users. For instance, something like the following would be nice: "%{typed('facts.selinux.enabled', 'Boolean')}"
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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-7510) FIPS-Enabled Puppet
Title: Message Title Trevor Vaughan commented on PUP-7510 Re: FIPS-Enabled Puppet Jayant Sane It's awesome that this is almost done. Is there an ETA at this point? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-1542) Install Facter 3 as a gem
Title: Message Title Trevor Vaughan commented on FACT-1542 Re: Install Facter 3 as a gem Happy New Year - We all still want this! 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
Trevor Vaughan created an issue
Puppet / PUP-8124
Puppet 5 Release Notes Missed a Language Deprecation
Issue Type:
Bug
Assignee:
Unassigned
Components:
Language
Created:
2017/11/03 10:27 AM
Priority:
Normal
Reporter:
Trevor Vaughan
Looking at https://puppet.com/docs/puppet/5.0/release_notes.html there was a language deprecation that was missed.
In Puppet 4, the following code works as expected and prints 'does it work yes'
class foo (
$var1 = 'does it work',
$var2 = "${foo::var1} yes"
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan commented on FACT-1732 Re: Facter core dump on large integers Branan Riley I just realized that what I said previously is simply untenable since it would break a lot of existing code. I guess auto-Stringification of big numbers is all that can be done for right now with a warning that things that get big might mysteriously break until Bignum support is added across the stack. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan commented on FACT-1732 Re: Facter core dump on large integers Branan Riley I can work on getting tickets in when I have time. We're trying to get a release out so it might be after PuppetConf. 1) Technically, that's everything that's an Integer. We can't dynamically Stringify things that are big because it will destroy logic in the underlying Puppet manifests. With strong typing, either something is an Integer or a String, it won't auto-cast (I think). And, of course, you can't have things be Strings sometimes and Integers other times because users just won't know what to do with the data and manifests will mysteriously break when things get too big (for whatever reason). I would definitely send out an announcement for people to be starting to watch for this and there's going to need to be some sort of purge script for PuppetDB to get bad data converted internally. 2) Yeah, this is the correct solution really but that's going to cover at least 3 languages. They're all solved problems but implementation and testing takes time. 3) Makes sense, but I still think you're going to have to Stringify all Numbers for the short term. You might be able to make this a Stringification of only custom facts and not core facts, but the disk sizes still pose a problem. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan commented on FACT-1732 Re: Facter core dump on large integers Branan Riley To your point about disk sizes...the default mountpoints fact returns both available_bytes and size_bytes as Integers. The disks fact also returns size_bytes as an Integer. If you have a representative disk with over 8 PB of space (not completely out of the question) then these facts will crash the system. My previous math was wrong - Ruby's max hits 4 Exabytes which is stretching it for current technologies, but the _javascript_ limit of 2^53-1 is not. Other items of note (default Facter) gce.instance.id => 4073115147758271314 (no idea how this is not crashing things, perhaps the hash burial is saving it) gce.project.numericProjectId => 1064768239454 (no idea how big this might get) My point is that you just don't know what any of this is going to be. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan commented on FACT-1732 Re: Facter core dump on large integers Branan Riley Things just got a lot more hairy with this particular issue - to put a fine point on it this could cause cascading failures across the entire puppet infrastructure from a single node's facts If you want to know exactly why we're grabbing kernel.shmall, we are using it to calculate the default number of shared memory pages in libvirt per optimization documentation that we found at some point PuppetDB cannot handle this Integer and is spewing errors into /opt/puppetlabs/server/data/puppetdb/stockpile/discard without ever cleaning them up (we had 7.8G which filled our root partition) This was PuppetDB 4.3.0 Puppet Server 2.7.2 works properly, even with the facter error Puppet Server 2.8.0 crashes completely and will not process catalogs Given the fact that a number that can be readily plucked from the running system now crashes numerous components, I think that facter needs to either convert the value to a string on exception (should be easy), or should do something else to prevent a cascading environment failure. It needs to be in facter because it's the only gatekeeper to the system as a whole for a 'fail-fast' solution. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan updated an issue Facter / FACT-1732 Facter core dump on large integers Change By: Trevor Vaughan Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan commented on FACT-1732 Re: Facter core dump on large integers Branan Riley Ok, I get tradeoffs so let's tackle this from another direction. The core dump should be wrapped in an error message that makes some sense to the user (this ticket) Ruby facter should have the same limitation imposed so that acceptance and rspec testing doesn't give false successes (this ticket) Puppet itself should warn if you use something in a variable that is greater than this new PUP-STD-BIGNUM (or whatever it gets called) (new ticket) I think that would cover everything that I would need as a user to not make me go insane between testing and production. Would that work for you? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan commented on FACT-1732 Re: Facter core dump on large integers Branan Riley So, how exactly does this work? Integers are Integers unless arbitrary decision that they're Strings until such point that facter gets fixed and then they're Integers again and all your code breaks? That doesn't seem very 'Strong Type' friendly. I do math on disk sizes quite a bit so this really isn't outside the realm of reality and not knowing whether or not something is a number isn't going to make for a good UX. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7511) Test puppet-agent against FIPS-compliant system openssl library
Title: Message Title Trevor Vaughan commented on PUP-7511 Re: Test puppet-agent against FIPS-compliant system openssl library Jayant Sane RHEL and CentOS 6 and 7. I really need to be able to change the hash algorithms from the central config file. Different customers have had different requirements for their algorithms and it's something that's supported by the underlying code, just not exposed as a configuration option. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Trevor Vaughan commented on PUP-3114 Re: Puppet needs to use default keylength 2048 on FIPS enabled systems Jayant Sane That's good news! I just double checked on one of my systems and the updates to openssl do indeed seem to support 4096 bit keys. However, this will not be compatible with all versions of EL6 and EL7 since I know for a fact that they used to die on 4096 bit keys. Ideally, you would try for 4096 and then either step it down to something that works or just provide a helpful error message. Personally, I would step it down if possible. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Trevor Vaughan commented on PUP-3114 Re: Puppet needs to use default keylength 2048 on FIPS enabled systems Jayant Sane The 2048, 3072, and 15360 key sizes were found by trial and error based on the FIPS documentation and an understanding of the standard key sizes. 4096 may work on EL7, but check EL6 as well. They may have updated both, and that would be nice, but you're going to be in a bit of a bind if you end up with different systems that support different settings based on patch-level. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5454) Bind mounts are not correctly handled by the 'mount' provider.
Title: Message Title Trevor Vaughan commented on PUP-5454 Re: Bind mounts are not correctly handled by the 'mount' provider. Owen Rodabaugh Well, technically everything has a workaround using exec , but That said, I guess an OK short term bespoke workaround would be OK. Anyone using NFSv4 will probably be using Puppet to manage bind mounts at some point. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7511) Test puppet-agent against FIPS-compliant system openssl library
Title: Message Title Trevor Vaughan commented on PUP-7511 Re: Test puppet-agent against FIPS-compliant system openssl library Jayant Sane We did test against a system that was FIPS enabled so from me. We do need to make sure that SHA-384 is supported though, which is what I think you are referring to. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan commented on FACT-1732 Re: Facter core dump on large integers Branan Riley I get not wanting to handle bignum values, but you don't really get to pick what people stuff into Facter facts and if you start talking about things over 4 Petabytes in Bytes, you're going to have a bad time since Ruby's max Fixnum on a 64 bit infrastructure is 2**62 - 1. This is not unreasonable on large systems even with the native facts. You might just want to bring in libgmp and call it a day. Alternatively, I guess you could treat them all as strings and mark them with something that says to translate to Integer (or whatever) before you shove it over the wire. Not precise, and more work, but 100% safe. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7511) Test puppet-agent against FIPS-compliant system openssl library
Title: Message Title Trevor Vaughan commented on PUP-7511 Re: Test puppet-agent against FIPS-compliant system openssl library Jayant Sane Apologies for not getting back to you on this sooner. We tested your build and it DOES work. We had no issues, and we did validate that it was properly linked against the OS libraries. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan created an issue Facter / FACT-1732 Facter core dump on large integers Issue Type: Bug Affects Versions: FACT 3.5.1 Assignee: Unassigned Attachments: facter_core_dump.txt Components: CLI Created: 2017/08/16 2:07 PM Environment: CentOS 7.4 Priority: Major Reporter: Trevor Vaughan Facter is core dumping when returning facts with large integers. How to reproduce: Create test_fact.rb with the following content:
Jira (PDOC-153) Users should be able to document the $name parameter of defined types
Title: Message Title Trevor Vaughan commented on PDOC-153 Re: Users should be able to document the $name parameter of defined types Henrik Lindberg From the *user* point of view, $name is more commonly used that $title so it's what I would usually put in my docs. I also need to be able to document arbitrary variables of import that might be useful to users. I know that this is not a usual use case, but params.pp is going to be around until early Puppet 4 is completely dead (so 2 more years or so?). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
