Jira (FACT-2018) Google Compute Engine metadata facts need endpoint change
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-2018 Google Compute Engine metadata facts need endpoint change Change By: Gabriel Nagy Fix Version/s: FACT 3.13.z Fix Version/s: FACT 3.11.z 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.324465.156829223.121793.1569913980176%40Atlassian.JIRA.
Jira (FACT-2018) Google Compute Engine metadata facts need endpoint change
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2018 Google Compute Engine metadata facts need endpoint change Change By: Mihai Buzgau Fix Version/s: FACT 3.14.5 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.324465.156829223.121811.1569917760238%40Atlassian.JIRA.
Jira (PUP-10057) User resource on Windows confuses domain and local accounts
Title: Message Title Kevin Reeuwijk created an issue Puppet / PUP-10057 User resource on Windows confuses domain and local accounts Issue Type: Bug Affects Versions: PUP 6.4.3 Assignee: Unassigned Components: Types and Providers, Windows Created: 2019/10/01 2:11 AM Priority: Normal Reporter: Kevin Reeuwijk Puppet Version: 6.4.3 (PE Agent from PE 2019.1.1) Puppet Server Version: PE 2019.1.1 OS Name/Version: Tested against Windows 2016 Behavior of the user resource goes wonky when an AD account exists that has the same name as the local user account you’re trying to manage on a Windows server that is domain-joined. Desired Behavior: Enforcing configuration of local user accounts on Windows domain-member servers works normally. Actual Behavior: When a user account exists locally on a member server, and a user account with the same name also exists in the Active Directory domain, this happens when setting `ensure=>absent` on that local user account: The first puppet run, the local user account is detected, and removed The second puppet run, the provider seems to detect the domain user account, and tries to delete the account again (from the local user database), which fails with this error: Could not set 'absent' on ensure: (in OLE method `Delete': ) OLE error code:800708AD in Active Directory The user name could not be found. HRESULT error code:0x80020009 Exception occurred. (file: /etc/puppetlabs/code/environments/development/site-modules/profile/manifests/base.pp, line: 98) Wrapped exception: (in OLE method `Delete': ) OLE error code:
Jira (FACT-2045) facterversion fact includes \n on windows
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2045 facterversion fact includes \n on windows Issue Type: Bug Assignee: Unassigned Created: 2019/10/01 3:30 AM Priority: Normal Reporter: Sebastian Miclea Running facter-ng on windows 2019 also shows \n in the string. facterversion => "0.0.5\n" Add Comment
Jira (FACT-2046) Integrate custom facts in Facter NG
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2046 Integrate custom facts in Facter NG Issue Type: Task Assignee: Unassigned Created: 2019/10/01 5:18 AM Priority: Normal Reporter: Bogdan Irimie 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.327469.1569932328000
Jira (FACT-2046) Integrate custom facts in Facter NG
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2046 Integrate custom facts in Facter NG Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.327469.1569932328000.122035.1569932340529%40Atlassian.JIRA.
Jira (PUP-9562) User resource does not respect forcelocal for the comment parameter
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9562 User resource does not respect forcelocal for the comment parameter Change By: Mihai Buzgau Sprint: PR - Triage 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.300292.1552589325000.122089.1569935580322%40Atlassian.JIRA.
Jira (PUP-10057) User resource on Windows confuses domain and local accounts
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10057 User resource on Windows confuses domain and local accounts Change By: Mihai Buzgau Sprint: PR - Triage 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.327453.1569921077000.122099.1569935700451%40Atlassian.JIRA.
Jira (PUP-10057) User resource on Windows confuses domain and local accounts
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10057 User resource on Windows confuses domain and local accounts Change By: Mihai Buzgau Team: Windows Night's Watch 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.327453.1569921077000.122097.1569935700442%40Atlassian.JIRA.
Jira (PUP-1537) Dpkg package provider misbehaving for held package with specific version
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-1537 Dpkg package provider misbehaving for held package with specific version Change By: Mihai Buzgau Sprint: PR - Triage 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.24894.1391021944000.122108.1569936000398%40Atlassian.JIRA.
Jira (PDOC-292) Pull defaults from data directory
Title: Message Title Igor Galić created an issue Puppet Strings / PDOC-292 Pull defaults from data directory Issue Type: New Feature Assignee: Unassigned Created: 2019/10/01 8:00 AM Priority: Normal Reporter: Igor Galić I'm wondering if it would make sense to pull parameter defaults from a module's data directory. This would require to either query the data using no facts, to ensure that these are platform agnostic defaults, or query the data while iterating thru on_supported_platform and provide a list of defaults Add Comment
Jira (PUP-10056) a warn function, to compliment fail, so it will be seen in agent log
Title: Message Title
Thomas Kishel commented on PUP-10056
Re: a warn function, to compliment fail, so it will be seen in agent log
Works on the command line with puppet apply:
[root@pe-201911-agent ~]# puppet apply -e "warning('TJK')"
Warning: Scope(Class[main]): TJK
Notice: Compiled catalog for pe-201911-agent.puppetdebug.vlan in environment production in 0.01 seconds
Notice: Applied catalog in 0.01 seconds
But not via a service run :
node 'pe-201911-agent.puppetdebug.vlan' {
notify{"YO!":}
warning('TJK')
}
Oct 1 15:20:04 pe-201911-agent puppet-agent[28915]: Caught TERM; exiting
Oct 1 15:20:04 pe-201911-agent systemd: Stopping Puppet agent...
Jira (PDB-3284) PQL operators sometimes whitespace sensitive
Title: Message Title Heston Hoffman updated an issue PuppetDB / PDB-3284 PQL operators sometimes whitespace sensitive Change By: Heston Hoffman Labels: maintenance query-engine-improvements resolved-issue-added 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.172549.148556000.122572.1569945960365%40Atlassian.JIRA.
Jira (PUP-10056) a warn function, to compliment fail, so it will be seen in agent log
Title: Message Title Josh Cooper commented on PUP-10056 Re: a warn function, to compliment fail, so it will be seen in agent log I think there's some confusion about terminology. The term "function" to me means a server-side function which is evaluated during catalog compilation. And there are builtin functions for each log level, e.g. notice, warning, err, etc, and there is also a fail function. The ticket is asking for the log message to appear in the agent log, which could either be a resource like notify or a client-side function (relying on Deferred). However, the fail function doesn't cause messages to appear in the agent's log, so I'm confused what's being requested. 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.327433.1569883542000.122802.1569948780329%40Atlassian.JIRA.
Jira (PUP-10056) a warn function, to compliment fail, so it will be seen in agent log
Title: Message Title Thomas Kishel commented on PUP-10056 Re: a warn function, to compliment fail, so it will be seen in agent log I have been relaying for a user with a PE ticket, so I've asked them to reply here to remove me form the middle ... 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.327433.1569883542000.123039.1569950700913%40Atlassian.JIRA.
Jira (PUP-8986) Puppet agent crashes because of bug in pip provider
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8986
Puppet agent crashes because of bug in pip provider
Change By:
Josh Cooper
*Puppet Version: 4.8.2**OS Name/Version: Debian 8.10* When trying to install a package with the pip providerpuppet agent -t fails with{code:java}Info: Using configured environment 'xxx'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for myhost.comInfo: Applying configuration version '123213'Error: Failed to apply catalog: undefined method `[]' for nil:NilClass {code}with --trace it points to: {code:java}Error: Failed to apply catalog: undefined method `[]' for nil:NilClass/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:64:in `block (2 levels) in pip_version'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:63:in `each'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:63:in `collect'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:63:in `block in pip_version'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:81:in `block (2 levels) in execpipe'/opt/puppetlabs/puppet/lib/ruby/2.1.0/open-uri.rb:36:in `open'/opt/puppetlabs/puppet/lib/ruby/2.1.0/open-uri.rb:36:in `open'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:80:in `block in execpipe'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:128:in `withenv'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:79:in `execpipe'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider.rb:117:in `execpipe'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:62:in `pip_version'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:43:in `instances'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package.rb:4:in `prefetch'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:323:in `prefetch'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:223:in `prefetch_if_necessary'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:107:in `block in evaluate'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `call'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `traverse'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/report.rb:142:in `as_logging_destination'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark' {code}The code is:{code:java}1 def self.pip_version2p
Jira (PDOC-292) Pull defaults from data directory
Title: Message Title Ben Ford commented on PDOC-292 Re: Pull defaults from data directory This would be incredibly useful. I can see the output getting VERY long though, especially if we iterate supported platforms. I wonder if this is worth another PARAMETER_DEFAULTS.md doc? 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.327485.1569942028000.123261.1569951720100%40Atlassian.JIRA.
Jira (PUP-10019) file resource checks source even if the file exists and replace is false
Title: Message Title Josh Cooper commented on PUP-10019 Re: file resource checks source even if the file exists and replace is false This behavior is expected if puppet is managing permissions (so it needs to query the remote source to determine what the correct permissions should be). However, if you set source_permissions => ignore or if you explicitly specify the owner, group, mode, then I would not expect puppet to require the source to exist. 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.324690.1568400128000.123347.1569952920260%40Atlassian.JIRA.
Jira (PUP-8986) Puppet agent crashes because of bug in pip provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8986 Puppet agent crashes because of bug in pip provider Change By: Josh Cooper Fix Version/s: PUP 6.4.z Fix Version/s: PUP 5.5.z 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.263957.1530879286000.123360.1569953460324%40Atlassian.JIRA.
Jira (PUP-8986) Puppet agent crashes because of bug in pip provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8986 Puppet agent crashes because of bug in pip provider Change By: Josh Cooper Sprint: Platform Core KANBAN 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.263957.1530879286000.123369.1569953520146%40Atlassian.JIRA.
Jira (PDOC-292) Pull defaults from data directory
Title: Message Title Henrik Lindberg commented on PDOC-292 Re: Pull defaults from data directory Would also need to understand the hiera.yaml to ensure all is based on data files inside the module. When using hiera to obtain the values (could be using deep merges etc) it needs to evaluate puppet code - and puppet code can call functions so you would need to make sure it is safe to evaluate logic when generating documentation (which was a problem before PDOC as you needed to load the code to get the docs). I think it would be better to have a separate tool that generates the default parameters part as data and that PDOC can make use of that when producing the docs. This way it is up to the publisher to run it in a safe manner whereas anyone else can generate docs without risking evaluating user code. 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.327485.1569942028000.123390.1569954240163%40Atlassian.JIRA.
Jira (PUP-9647) Pip package provider does not handle pip executable paths with spaces
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9647 Pip package provider does not handle pip executable paths with spaces Change By: Josh Cooper Team: Night's Watch Coremunity 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.305257.133562000.123417.1569954780682%40Atlassian.JIRA.
Jira (PUP-9647) Pip package provider does not handle pip executable paths with spaces
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9647 Pip package provider does not handle pip executable paths with spaces Change By: Josh Cooper Fix Version/s: PUP 6.4.z Fix Version/s: PUP 5.5.z 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.305257.133562000.123421.1569954780719%40Atlassian.JIRA.
Jira (PUP-9647) Pip package provider does not handle pip executable paths with spaces
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9647 Pip package provider does not handle pip executable paths with spaces Change By: Josh Cooper Sprint: Platform Core KANBAN 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.305257.133562000.123425.1569954840630%40Atlassian.JIRA.
Jira (PUP-9647) Pip package provider does not handle pip executable paths with spaces
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9647 Pip package provider does not handle pip executable paths with spaces Change By: Josh Cooper Assignee: Josh Cooper 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.305257.133562000.123429.1569954840647%40Atlassian.JIRA.
Jira (PUP-8949) Package pip provide won't work with ensure latest and custom index
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8949 Package pip provide won't work with ensure latest and custom index Change By: Josh Cooper Team: Platform OS Night's Watch 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.261544.1529423125000.123440.1569954900800%40Atlassian.JIRA.
Jira (PUP-2905) When installing PIP packages from sources different than pypi, the install and any notifies are triggered during every run.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2905 When installing PIP packages from sources different than pypi, the install and any notifies are triggered during every run. Change By: Josh Cooper Team: Platform OS Night's Watch 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.41490.1404824405000.123442.1569954900808%40Atlassian.JIRA.
Jira (PUP-7644) puppet installing pip rather than pip3 packages using the pip3 provider only on the first run
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7644 puppet installing pip rather than pip3 packages using the pip3 provider only on the first run Change By: Josh Cooper Team: Platform OS Night's Watch 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.195235.1497025338000.123437.1569954900787%40Atlassian.JIRA.
Jira (PUP-8958) Pip Package Improvements
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8958 Pip Package Improvements Change By: Josh Cooper Team/s: Platform OS Night's Watch 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.262603.1529950604000.123451.1569954960084%40Atlassian.JIRA.
Jira (PUP-2210) Install multi architecture rpm sometimes fail
Title: Message Title
Josh Cooper commented on PUP-2210
Re: Install multi architecture rpm sometimes fail
Hi demetrio condello, I can't reproduce using the latest puppet-agent version after adding multilib_policy=all to /etc/yum.conf as described in the original redmine ticket:
# puppet apply -e "package { 'openssl-devel': ensure => installed }" --debug
...
Debug: Prefetching yum resources for package
Debug: Executing: '/usr/bin/rpm --version'
Debug: Executing '/usr/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' | sort'
Debug: Executing: '/usr/bin/rpm -q openssl-devel --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Debug: Executing: '/usr/bin/rpm -q openssl-devel --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n --whatprovides'
Debug: Package[openssl-devel](provider=yum): Ensuring => present
Debug: Executing: '/usr/bin/yum -d 0 -e 0 -y install openssl-devel'
Notice: /Stage[main]/Main/Package[openssl-devel]/ensure: created
...
Jira (PUP-2210) Install multi architecture rpm sometimes fail
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2210 Install multi architecture rpm sometimes fail Change By: Josh Cooper We need to rebuild our rhel 6.4 machine with i686 and x86_64 packages with our puppet 0.24.8. (Yes, we know that is an old old version..., but for legacy reason we cannot update). To accomply this we added the multilib_policy=all in our /etc/yum.conf.Unfortunatley sometimes puppet doesn't install both versions. the problem affects random packages. Every reinstallation is different.Seem to be a regression of this problem http://projects. reductivelabs puppetlasb .com/issues/1465Do you have any suggestions ?Regards 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/
Jira (PUP-2821) disable_warnings setting is inert in [master]
Title: Message Title Josh Cooper commented on PUP-2821 Re: disable_warnings setting is inert in [master] Looks to work correctly now. Without the setting, the server log prints: 2019-10-01T20:43:14.323Z WARN [qtp1893470395-81] [puppetserver] Puppet This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Integer. There is further documentation for validate_legacy function in the README. at ["/etc/puppetlabs/code/environments/production/manifests/site.pp", 1]: If I add the setting to the master section, and reload puppetserver then no more warning [root@deuaydeq4o5qqbi ~]# puppet config set disable_warnings deprecations --section master [root@deuaydeq4o5qqbi ~]# puppetserver reload [root@deuaydeq4o5qqbi ~]# puppet agent -t Then server log doesn't show deprecation warning: 2019-10-01T20:44:56.072Z INFO [qtp1658177334-125] [puppetserver] Scope(Class[main]) 2019-10-01T20:44:56.078Z INFO [qtp1658177334-125] [puppetserver] Puppet Compiled catalog for deuaydeq4o5qqbi.delivery.puppetlabs.net in environment production in 0.21 seconds
Jira (PUP-3044) Expand Puppet File Permissions
Title: Message Title Josh Cooper commented on PUP-3044 Re: Expand Puppet File Permissions We've talked about adding that to the acl module, instead of core puppet. Closing this. 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.47242.1407790241000.123671.1569963000376%40Atlassian.JIRA.
Jira (PUP-3426) Exit code 2 being used for successful completion without errors
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3426 Exit code 2 being used for successful completion without errors Change By: Josh Cooper Team: Coremunity 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.54124.1412856411000.123679.1569963060226%40Atlassian.JIRA.
Jira (PDB-4524) Provide way to stop/start command processing (maybe only internal initially)
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4524 Provide way to stop/start command processing (maybe only internal initially) Issue Type: Improvement Assignee: Unassigned Created: 2019/10/01 1:56 PM Priority: Normal Reporter: Rob Browning Provide a way to stop and start command processing, perhaps initially only internally, say via a service method. This should help reduce the complexity/fragility of some of the tests. While we might want to eventually support some public way to control this, that can come later. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-7667) puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-7667 puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set Change By: Josh Cooper Assignee: Daniel Dreier 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.196080.1497521296000.123712.1569963420889%40Atlassian.JIRA.
Jira (PUP-7667) puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7667 puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set Change By: Josh Cooper Fix Version/s: PUP 7.0.0 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.196080.1497521296000.123715.1569963420901%40Atlassian.JIRA.
Jira (PUP-7667) puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7667 puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set Change By: Josh Cooper Team: Coremunity 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.196080.1497521296000.123721.1569963480289%40Atlassian.JIRA.
Jira (PUP-7667) puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set
Title: Message Title Josh Cooper commented on PUP-7667 Re: puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set Makes sense Florian Klink. I've updated the description based on your suggestion. 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.196080.1497521296000.123723.1569963480298%40Atlassian.JIRA.
Jira (PUP-7667) puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7667
puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set
Change By:
Josh Cooper
Acceptance Criteria:
Puppet should default its certname to the {{facter fqdn}} fact and fallback to {{$(facter hostname).$(facter domain)}}.
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.196080.1497521296000.123733.1569963600409%40Atlassian.JIRA.
Jira (PUP-10046) Prepare release announcement (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha commented on PUP-10046 Re: Prepare release announcement (Puppet Platform 6.10.0) The next release in the Platform 6 series, Platform 6.10.0 is now available! The release contains bug fixes and minor improvements, including: Query parameters for HTTP and HTTPS file resources are now preserved YAML output with special characters is now valid You can see the full list of changes in the release notes https://puppet.com/docs/puppet/latest/release_notes_puppet.html cc/ Jean Bond Bill Tang please review the release notes above. Eric Griswold you can use this once we get a thumbs up from Jean and Bill for the release announcement. 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.326631.1569437002000.123730.1569963600338%40Atlassian.JIRA.
Jira (PUP-8048) puppet / facter fails randomly in low memory situations
Title: Message Title Josh Cooper commented on PUP-8048 Re: puppet / facter fails randomly in low memory situations The Debian packages of puppet install facter 2.4.6 (the ruby version). It is entirely possible that the old ruby facter implementation required more/excessive amount of memory due to the way it executed the same facts multiple times. We don’t have the engineering resources to investigate this issue, so I'm going to close it. Feel free to reopen if you see the same issue with the puppet-agent packages provided by 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.216102.1507905599000.123756.1569964080341%40Atlassian.JIRA.
Jira (PUP-10046) Prepare release announcement (Puppet Platform 6.10.0)
Title: Message Title Maggie Dreyer commented on PUP-10046 Re: Prepare release announcement (Puppet Platform 6.10.0) Can we include a top-level note about Debian 10 support for masters (Puppet Server and PDB)? We've been getting inquiries from the community. 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.326631.1569437002000.123770.1569964320429%40Atlassian.JIRA.
Jira (PDB-4525) PQL and AST should not return schema errors to user
Title: Message Title
Austin Blatt created an issue
PuppetDB / PDB-4525
PQL and AST should not return schema errors to user
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/10/01 2:11 PM
Priority:
Normal
Reporter:
Austin Blatt
Both PQL and AST can return schema errors to the user. These errors are unintelligible without understanding the query engine.
clojure.lang.ExceptionInfo: Value does not match schema: (not (map? nil)) {:type :schema.core/error, :schema {:type Keyword, :field (cond-pre Keyword honeysql.types.SqlCall honeysql.types.SqlRaw {:select Any, Any Any}), Any Any}, :value nil, :error (not (map? nil))}
We should return a more useful error message. At a minimum we should identify the field that threw that error, the expected type, and the actual type and report that to the user.
Add Comment
Jira (PUP-10058) Allow static catalogs to inline metadata for deeper modulepaths
Title: Message Title Maggie Dreyer moved an issue Puppet / PUP-10058 Allow static catalogs to inline metadata for deeper modulepaths Change By: Maggie Dreyer Affects Version/s: SERVER 5.3.4 Key: SERVER PUP - 2419 10058 Project: Puppet 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.290273.1546538287000.123791.1569964920482%40Atlassian.JIRA.
Jira (PUP-10058) Allow static catalogs to inline metadata for deeper modulepaths
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10058 Allow static catalogs to inline metadata for deeper modulepaths Change By: Maggie Dreyer Team: 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.290273.1546538287000.123793.1569964980165%40Atlassian.JIRA.
Jira (PUP-10046) Prepare release announcement (Puppet Platform 6.10.0)
Title: Message Title Jean Bond commented on PUP-10046 Re: Prepare release announcement (Puppet Platform 6.10.0) +1 from me to send this. I've edited it to include the Debian 10 note. 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.326631.1569437002000.123893.1569966960183%40Atlassian.JIRA.
Jira (PUP-8115) Puppet randomly corrupts files (it puts json/pson instead of file content)
Title: Message Title Josh Cooper commented on PUP-8115 Re: Puppet randomly corrupts files (it puts json/pson instead of file content) This is probably an issue with persistent http connections introduced in puppet 3.7. In the comments above, puppet tries to retrieve file metatdata, but gets an http response containing binary content (application/octet-stream). Presumably the binary content is from a previous content request. If the connection raises an exception (such as a timeout, connection reset, etc), then ruby should raise an exception and puppet will not reuse the connection. However, it is possible ruby is swallowing an exception. I've seen 2 cases so far: ruby silently truncates the response (see PUP-9911), and doesn't raise exceptions when writing to the socket. Puppet also doesn't read the response body when handling redirects. I think one option is to ensure response body's are drained before we add the connection back to the pool. 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.220020.1509616474000.124017.1569968880544%40Atlassian.JIRA.
Jira (PUP-8115) Puppet randomly corrupts files (it puts json/pson instead of file content)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8115 Puppet randomly corrupts files (it puts json/pson instead of file content) Change By: Josh Cooper Team: Coremunity 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.220020.1509616474000.124022.1569968880565%40Atlassian.JIRA.
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Rob Browning commented on PDB-2487 Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Yes, at least that should still be the plan. 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.119255.1456852336000.124053.1569968941021%40Atlassian.JIRA.
Jira (PUP-8180) puppet agent -t fails from within sshfs working directory
Title: Message Title Josh Cooper commented on PUP-8180 Re: puppet agent -t fails from within sshfs working directory I think this is related to PUP-9997, but it's being triggered by the vcsrepo's use of Dir.chdir, and it occurs when the puppet process tries to change the current working directory back to the sshfs home directory. What was the workaround you used? 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.222190.1510773679000.124099.1569969300391%40Atlassian.JIRA.
Jira (PUP-8180) puppet agent -t fails from within sshfs working directory
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8180 puppet agent -t fails from within sshfs working directory Change By: Josh Cooper Team: Coremunity 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.222190.1510773679000.124101.1569969360209%40Atlassian.JIRA.
Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Josh Cooper commented on PUP-8376 Re: Revert to production when agent-specified environment doesn't exist I'm going to close this ticket based on my earlier comments. 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.232102.1516564527000.124108.1569969420745%40Atlassian.JIRA.
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Rob Browning commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs Yasmin Rajabi It's on our team's list of priorities, and it sounds like it's on others' lists as well, so given that, and what it sounds like may be a more general emphasis on HA, I assume it's likely to be addressed in our next rounds of work – we definitely want to fix 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.220461.1509743938000.124127.1569969660496%40Atlassian.JIRA.
Jira (PUP-10046) Prepare release announcement (Puppet Platform 6.10.0)
Title: Message Title Eric Griswold commented on PUP-10046 Re: Prepare release announcement (Puppet Platform 6.10.0) Holding on approval from Bill 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.326631.1569437002000.124131.1569969660534%40Atlassian.JIRA.
Jira (PDB-4342) Add basis for making node lifetimes configurable
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4342 Add basis for making node lifetimes configurable Change By: Zachary Kent Assignee: Zachary Kent 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.304555.1555024076000.124139.1569969723037%40Atlassian.JIRA.
Jira (PUP-10046) Prepare release announcement (Puppet Platform 6.10.0)
Title: Message Title Bill Tang commented on PUP-10046 Re: Prepare release announcement (Puppet Platform 6.10.0) +1. looks good 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.326631.1569437002000.124214.1569970680302%40Atlassian.JIRA.
Jira (PUP-9075) File type "replace => false" doesn't allow to remove the file if "ensure => absent"
Title: Message Title Josh Cooper commented on PUP-9075 Re: File type "replace => false" doesn't allow to remove the file if "ensure => absent" The original behavior comes from https://projects.puppetlabs.com/issues/1750: If I have a File with ensure=>link and replace=>false, and it already exists as a directory, puppet correctly does not change the directory, but also logs an error about not being able to remove the existing directory. The behavior of ensure => absent in combination with replace => false is unspecified in documentation. However, to Eric Sorenson's point, someone is probably relying on the current behavior of never deleting (in addition to modifying) an existing file/link/directory when replace is false. 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.272161.1534820125000.124209.1569970680274%40Atlassian.JIRA.
Jira (PUP-7218) systemd service provider missing double dash
Title: Message Title Justin Collier assigned an issue to Justin Collier Puppet / PUP-7218 systemd service provider missing double dash Change By: Justin Collier Assignee: Justin Collier 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.175424.1487076959000.124377.1569977100261%40Atlassian.JIRA.
Jira (PUP-7218) systemd service provider missing double dash
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7218 systemd service provider missing double dash Change By: Josh Cooper Team: Platform OS Coremunity 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.175424.1487076959000.124427.1569985200702%40Atlassian.JIRA.
Jira (PUP-9787) Unintentional secret reveal while installing modules
Title: Message Title Josh Cooper assigned an issue to Jorie Tappa Puppet / PUP-9787 Unintentional secret reveal while installing modules Change By: Josh Cooper Assignee: Jorie Tappa 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.313276.1560984349000.124479.1569987300388%40Atlassian.JIRA.
Jira (PUP-9787) Unintentional secret reveal while installing modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9787 Unintentional secret reveal while installing modules Change By: Josh Cooper Sprint: Platform Core KANBAN 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.313276.1560984349000.124476.1569987300363%40Atlassian.JIRA.
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8094 Lookup ignores environment from the classifier when using rule with trusted facts Change By: Josh Cooper Sprint: Coremunity Grooming 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.214573.1507141532000.124509.1569987900484%40Atlassian.JIRA.
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Josh Cooper commented on PUP-8094 Re: Lookup ignores environment from the classifier when using rule with trusted facts That makes sense to me too. It's not hard to have lookup perform a node request and either use the returned node's environment or continue along using its configured environment. 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.214573.1507141532000.124519.1569987960304%40Atlassian.JIRA.
Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9295 Notify resource exposes Sensitive data when message is a Sensitive data Change By: Josh Cooper Sprint: Coremunity Hopper Platform Core KANBAN 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.283215.1540998541000.124556.1569991861732%40Atlassian.JIRA.
Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9295 Notify resource exposes Sensitive data when message is a Sensitive data Change By: Josh Cooper Assignee: Josh Cooper 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.283215.1540998541000.124546.1569991861687%40Atlassian.JIRA.
Jira (PUP-10026) skip_tags not documented for puppet agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10026 skip_tags not documented for puppet agent Change By: Josh Cooper Labels: beginner 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.325377.1568896957000.124559.1569992520303%40Atlassian.JIRA.
Jira (PUP-10026) skip_tags not documented for puppet agent
Title: Message Title Josh Cooper commented on PUP-10026 Re: skip_tags not documented for puppet agent tags and skip_tags are both puppet settings, for example, see https://puppet.com/docs/puppet/5.5/configuration.html#skiptags. But puppet agent --help only describes tags. We should include skip_tags for consistency. 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.325377.1568896957000.124563.1569992640141%40Atlassian.JIRA.
