Jira (PUP-6021) Tidy can not trigger resources
Title: Message Title Maximilian Philipps commented on PUP-6021 Re: Tidy can not trigger resources 2 years later, puppet 6.18.0 and the bug still isn't fixed. 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.120354.1457449682000.31589.1599575880025%40Atlassian.JIRA.
Jira (PUP-10365) puppet agent unable to fetch file from https source - Error: certificate verify failed
Title: Message Title Maximilian Philipps commented on PUP-10365 Re: puppet agent unable to fetch file from https source - Error: certificate verify failed Are there any plans for a bug fix release including this? Just spend several hours debugging this only to finally come up with the same fix, followed by me finding this bug report. I have also tried to always include the system store, but apparently include here means replace the puppetmaster CA, not add to it. The best workaround I can think of right now is to have a puppet file_line resource patch puppet, which doesn't feel right. 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.349360.1583950376000.17065.1584701520023%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Maximilian Philipps commented on PUP-10017 Re: Collapse dependency failures into Class level failures From reading the release notes I hoped this would help us. However after renaming the apache package resource in our test environment I still get almost 7000 lines of Skipping because of failed dependencies and just one Skipping resources in class because of failed class dependencies. Is this supposed to only work on class dependencies and not on individual resources? We often tag resources and then build dependencies between them using resource collectors. 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.324379.1568220393000.24250.1579077720375%40Atlassian.JIRA.
Jira (PUP-5921) Deprecate source_permissions
Title: Message Title Maximilian Philipps commented on PUP-5921 Re: Deprecate source_permissions I don't understand why source_permissions is deprecated. "it doesn't make sense for environments (including PE) that use git for the backend (user/group aren't managed by git)" and if the backend isn't git? Also source_permissions is really useful for mode sensitive files, even if the backend is git. I am not aware that source may only point to git repositories. 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.117270.1455758203000.14130.1578399360201%40Atlassian.JIRA.
Jira (PUP-10120) resources cron purge fails if resource's name to be purged matches the title of a different resource
Title: Message Title Maximilian Philipps updated an issue Puppet / PUP-10120 resources cron purge fails if resource's name to be purged matches the title of a different resource Change By: Maximilian Philipps Summary: resources cron purge fails if resource's name to be purged matches the title of a different resource 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.333535.1572956409000.21508.1573036620618%40Atlassian.JIRA.
Jira (PUP-10120) resources cron purge fails resource's name to be purged matches the title of a different resource
Title: Message Title Maximilian Philipps commented on PUP-10120 Re: resources cron purge fails resource's name to be purged matches the title of a different resource hi, I can see how it is similiar to PUP-10118. Is the resource purge logic independent from the resource provider? I can't think of how a cron resource wouldn't be idempotent. Another thing to keep in mind, from what I recall the cron purge logic also isn't working correct for when a cron entry exists in the wrong cron user tab. I feel like the user value should be part of the namevar. 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.333535.1572956409000.21505.1573036620600%40Atlassian.JIRA.
Jira (PUP-10120) resources cron purge fails iff title != name
Title: Message Title
Maximilian Philipps created an issue
Puppet / PUP-10120
resources cron purge fails iff title != name
Issue Type:
Bug
Assignee:
Unassigned
Components:
Catalog Application
Created:
2019/11/05 4:20 AM
Priority:
Normal
Reporter:
Maximilian Philipps
Puppet Version: 6.10.1-1stretch** OS Name/Version: Debian stretch hi, I just discovered some duplicated crontab entries and then after some debugging found that resources cron purge ignores the name of the cron resources. Reproduction: puppet apply the following:
resources { 'cron':
purge => true
}
cron { 'foo1':
command => '/bin/true'
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Maximilian Philipps commented on PUP-9790 Re: undefined method `pip_version' with pip3 provider Alright, looking forward to 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.1534.1561962600159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Maximilian Philipps commented on PUP-9790 Re: undefined method `pip_version' with pip3 provider Josh Cooper: Is there any chance of getting an 6.5.1 release with this fixed? 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.313529.1561106191000.15.1561711260142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title
Maximilian Philipps updated an issue
Puppet / PUP-9790
undefined method `pip_version' with pip3 provider
Change By:
Maximilian Philipps
*Puppet Version: 6.5.0* *Puppet Server Version: 6.4.0* *OS Name/Version: Debian stretch*After updating puppet-agent to 6.5.0 and the puppet server to 6.4.0 package resources with a pip3 provider throw the following error:{noformat}Debug: Prefetching pip3 resources for packageDebug: Executing '/usr/bin/pip3 --version'Debug: Executing '/usr/bin/pip3 freeze --all'Debug: Puppet::Type::Package::ProviderPip3: Prefetched instance: %{name} via command: %{command}Debug: Puppet::Type::Package::ProviderPip3: Prefetched instance: %{name} via command: %{command}Error: Could not get latest version: undefined method `pip_version' for Package[checkdmarc](provider=pip3)(command=default):Puppet::Type::Package::ProviderPip3Info: Unknown failure using insync_values? on type: Package[checkdmarc] / property: ensure to compare values [:latest] and 4.1. 10Error 10 Error : /Stage[main]/Main/Node[redacted]/Mail::Dmarc_report[redacted]/Package[checkdmarc]/ensure: change from '4.1.10' to 'latest' failed: Could not get latest version: undefined method `pip_version' for Package[checkdmarc](provider=pip3)(command=default):Puppet::Type::Package::ProviderPip3{noformat}The code from the module is just:{noformat}package { 'checkdmarc': ensure => 'latest' , provider => 'pip3' , require => Package['python3-pip'] }{noformat} {noformat}$ /usr/bin/pip3 --versionpip 9.0.1 from /usr/lib/python3/dist-packages (python 3.5){noformat}
Add Comment
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title
Maximilian Philipps updated an issue
Puppet / PUP-9790
undefined method `pip_version' with pip3 provider
Change By:
Maximilian Philipps
*Puppet Version: 6.5.0* *Puppet Server Version: 6.4.0* *OS Name/Version: Debian stretch*After updating puppet-agent to 6.5.0 and the puppet server to 6.4.0 package resources with a pip3 provider throw the following error:{noformat} Debug: Prefetching pip3 resources for package Debug packageDebug : Executing '/usr/bin/pip3 --version' Debug: Executing '/usr/bin/pip3 freeze --all' Debug: Puppet::Type::Package::ProviderPip3: Prefetched instance: %{name} via command: %{command} Debug: Puppet::Type::Package::ProviderPip3: Prefetched instance: %{name} via command: %{command} Error: Could not get latest version: undefined method `pip_version' for Package[checkdmarc](provider=pip3)(command=default):Puppet::Type::Package::ProviderPip3 Info: Unknown failure using insync_values? on type: Package[checkdmarc] / property: ensure to compare values [:latest] and 4.1. 10 Error 10Error : /Stage[main]/Main/Node[redacted]/Mail::Dmarc_report[redacted]/Package[checkdmarc]/ensure: change from '4.1.10' to 'latest ' failed: Could not get latest version: undefined method `pip_version' for Package[checkdmarc](provider=pip3)(command=default):Puppet::Type::Package:: ProviderPip3 ProviderPip3 {noformat}The code from the module is just:{noformat} package { 'checkdmarc': ensure => 'latest' , provider => 'pip3' , require => Package['python3-pip'] }{noformat} {noformat} $ /usr/bin/pip3 --versionpip 9.0.1 from /usr/lib/python3/dist-packages (python 3.5){noformat}
Add Comment
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Maximilian Philipps created an issue Puppet / PUP-9790 undefined method `pip_version' with pip3 provider Issue Type: Bug Affects Versions: PUP 6.5.0 Assignee: Unassigned Components: Types and Providers Created: 2019/06/21 1:36 AM Labels: regression type_and_provider Priority: Major Reporter: Maximilian Philipps Puppet Version: 6.5.0 Puppet Server Version: 6.4.0 OS Name/Version: Debian stretch After updating puppet-agent to 6.5.0 and the puppet server to 6.4.0 package resources with a pip3 provider throw the following error: Debug: Prefetching pip3 resources for packageDebug: Executing '/usr/bin/pip3 --version' Debug: Executing '/usr/bin/pip3 freeze --all'Debug:
Jira (PUP-3482) server-side only execution stub
Title: Message Title Maximilian Philipps commented on PUP-3482 Re: server-side only execution stub hi, Are there any plans to fix this? I have been trying to write a generate() puppet function for the last few hours only to discover that implementation for Puppet::Util::Execution.execute is highly confusing. For anyone else trying something similar here is what I discovered: Puppet::Util::Exection.execute is the intended way of calling an external program from puppet. This is the case for client side (like a Exec) Resource and for server side (generate()). execute() takes a set of options, however what documented and what is implemented quickly diverges. For example the code sets a default value for suppress_window, the documentation never mentions it and I am not sure it is ever actually used. Presumably that is a MS Windows specific option anyway. Following that we run into several ifs that determine which code path to use for actually executing the command. The first one appears to be used for for spec testing (Puppet::Util::Execution_stub, the second is for POSIX and the last for MS Windows. For Puppet Linux is considered a POSIX system and for client side execution this is the path taken. However on the server things a different. If we try same path as on the client we discover that Kernel.fork is not implemented in JRuby and that the server instead intercepts the execution call through the spec test path and instead continues in Puppet::Server::Execution. Not supported options are just silently dropped. Is there any reason to fall back into the java code for the puppet server? Surely there must be a way to call an external command from JRuby. Even if Kernel.fork is not implemented, maybe there is something like Kernel.spawn? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Maximilian Philipps commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log I have no idea how you all get such fast puppets runs, but I at least can confirm the issue. Sometimes we see a large discreptancy between the time reported in the puppet-agent log and in the last_summery.yaml: In this case here the last_summery.yaml reports a total of 2755.9764387860105 seconds, but the puppet-agent log claims to have "only" taken 920.03 seconds. version: config: 5a84cbdc4c7277446118e5c5847bc7ffeee017f3-dirty puppet: 5.5.0 resources: changed: 0 corrective_change: 0 failed: 0 failed_to_restart: 0 out_of_sync: 0 restarted: 0 scheduled: 0 skipped: 0 total: 1971
