Jira (PDB-4502) PuppetDB command size metrics are missing
Title: Message Title Charlie Sharpsteen commented on PDB-4502 Re: PuppetDB command size metrics are missing Looks like the metric is based on the Content-Length header: https://github.com/puppetlabs/puppetdb/blob/6.5.0/src/puppetlabs/puppetdb/middleware.clj#L268-L276 We should change this to measure bytes written to stockpile. 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.323996.156781861.89748.1567821540248%40Atlassian.JIRA.
Jira (PDB-4502) PuppetDB command size metrics are missing
Title: Message Title Charlie Sharpsteen updated an issue PuppetDB / PDB-4502 PuppetDB command size metrics are missing Change By: Charlie Sharpsteen CS Priority: Needs Priority 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.323996.156781861.89723.1567818660544%40Atlassian.JIRA.
Jira (PDB-4502) PuppetDB command size metrics are missing
Title: Message Title Charlie Sharpsteen created an issue PuppetDB / PDB-4502 PuppetDB command size metrics are missing Issue Type: Bug Affects Versions: PDB 6.5.0, PDB 5.2.9 Assignee: Unassigned Created: 2019/09/06 6:10 PM Priority: Normal Reporter: Charlie Sharpsteen PuppetDB has a global.size message queue metric that provides the distribution of command sizes that have been submitted: https://puppet.com/docs/puppetdb/6.5/api/metrics/v1/mbeans.html#message-queue-metrics This information is important for determining PuppetDB memory use and detecting changes that have caused an abnormal amount of command data to be submitted. In current configurations, this metric is not receiving any data. Reproduction Case Install Puppet, Puppet Server, and PuppetDB 5 on a CentOS 7 system: yum install -y http://yum.puppetlabs.com/puppet5-release-el-7.noarch.rpm yum install -y puppetserver
Jira (PDB-4456) Add support for import/export for "replace catalog inputs"
Title: Message Title Austin Blatt assigned an issue to Zachary Kent PuppetDB / PDB-4456 Add support for import/export for "replace catalog inputs" Change By: Austin Blatt Assignee: Austin Blatt 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.317966.1563991828000.89537.1567803240674%40Atlassian.JIRA.
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Gene Liverman commented on PDOC-273 Re: puppet-strings should pull documentation from the lib folder too Thanks for the info 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.294635.1549292365000.89532.1567803120132%40Atlassian.JIRA.
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Jorie Tappa commented on PDOC-273 Re: puppet-strings should pull documentation from the lib folder too Hi Gene Liverman, we removed this from our active sprint because it's not currently being worked on, and right now we're focusing our efforts on higher priority bugs and features. Kris will update the ticket when he's actively working on it again. 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.294635.1549292365000.89530.1567803060151%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Jean Bond commented on PUP-9480 Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Looks pretty straightforward to me, thank you Kris Bosland! 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.295251.154953565.89419.1567799520240%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Jean Bond updated an issue Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Change By: Jean Bond Labels: known-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.295251.154953565.89409.1567799460611%40Atlassian.JIRA.
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Gene Liverman commented on PDOC-273 Re: puppet-strings should pull documentation from the lib folder too Jorie Tappa - I saw that you made a small edit on this and was curious where it sat on the priority list. 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.294635.1549292365000.89366.1567797120151%40Atlassian.JIRA.
Jira (PUP-9956) Exec logs output of Sensitive unless and onlyif checks at debug
Title: Message Title
Kris Bosland commented on PUP-9956
Re: Exec logs output of Sensitive unless and onlyif checks at debug
Tested in 5.5.x:
kris.bosland@kris:puppet % cat ../tmp/pup-9956/apply.pp ±[remotes/upstream/5.5.x]
# test.pp
exec { 'Non-sensitive command':
command => '/bin/echo Pass',
}exec { 'Sensitive command':
command => Sensitive('/bin/echo "secret0"'),
}exec { 'Sensitive unless':
command => '/bin/echo Pass',
unless => Sensitive('/bin/echo "secret1"'),
}exec { 'Sensitive onlyif':
command => '/bin/echo Pass',
_onlyif_ => Sensitive('/bin/echo "secret2"'),
}
Jira (PUP-9956) Exec logs output of Sensitive unless and onlyif checks at debug
Title: Message Title Kris Bosland commented on PUP-9956 Re: Exec logs output of Sensitive unless and onlyif checks at debug Passed CI in b91e0bfc8f631177edd708fbdffc4181ceb34d6a. 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.320444.1565385879000.89216.1567791600151%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Kris Bosland commented on PUP-9480 Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Jean Bond updated. I kept it pretty short, let me know if it needs more information. 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.295251.154953565.89181.1567791000404%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Kris Bosland updated an issue Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Change By: Kris Bosland Release Notes Summary: The host type only supports one IP address for each hostname. Because of this, it does not support both an IPv4 and IPv6 address for the same hostname. Release Notes: Known 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295251.154953565.89171.1567790940335%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Jean Bond commented on PUP-9480 Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Kris Bosland, thanks for the heads up on this. We should add this as a known issue. If you could fill out the docs tab with a summary of the problem and what users should do about it, that would be very helpful. 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.295251.154953565.89154.1567790700462%40Atlassian.JIRA.
Jira (PUP-2887) IPv6 failover using srv records doesn't work as expected
Title: Message Title Josh Cooper commented on PUP-2887 Re: IPv6 failover using srv records doesn't work as expected One difficulty with implementing happy eyeballs is that Net::HTTP only accepts a hostname or IP to connect to, and always performs SSL verification against that value. If we pass a hostname, then ruby looks up the ipv6 or v4 address, and uses the first one it can connect to. If we pass the IP address, then verification of the server's SSL cert will likely fail. I say likely because it's possible to add the server's IP address as a subject alt name, but that's not very common. To implement happy eyeballs we could either: call Net::HTTP.start with both the IP address (v4 or v6) and fqdn, where SSL verification happens against the latter. This would require an upstream ruby PR. override the SSL verification callback and do the post_connection_check ourselves. 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.41163.140440062.89107.1567789740203%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Kris Bosland commented on PUP-9480 Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Jean Bond, is there some place that we are documenting IPv6 limitations and errata? Because of existing limitations in the `host` type (unrelated to IPv6) this issue will not be fixed any time soon. 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.295251.154953565.89047.1567788780351%40Atlassian.JIRA.
Jira (PDB-4501) Enable debian-10-x86_64 test pipeline for puppetdb
Title: Message Title Maggie Dreyer updated an issue PuppetDB / PDB-4501 Enable debian-10-x86_64 test pipeline for puppetdb Change By: Maggie Dreyer Team: PuppetDB 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.323857.1567787536000.89023.1567788540682%40Atlassian.JIRA.
Jira (PUP-10000) Puppet 10k
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-1 Puppet 10k Change By: Jorie Tappa Issue Type: Bug New Feature 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.323670.1567700828000.89031.1567788600531%40Atlassian.JIRA.
Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title Jorie Tappa created an issue Puppet / PUP-10013 Update minitar version and call new fsync=false option Issue Type: Task Assignee: Unassigned Created: 2019/09/06 9:48 AM Priority: Normal Reporter: Jorie Tappa Update the version in all the places, and make sure you add the option fsync=false so that we're improving performance Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4500) Enable debian-10-x86_64 builds for puppetdb
Title: Message Title Maggie Dreyer updated an issue PuppetDB / PDB-4500 Enable debian-10-x86_64 builds for puppetdb Change By: Maggie Dreyer Team: PuppetDB 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.323856.1567787531000.89018.1567788481621%40Atlassian.JIRA.
Jira (PDB-4469) Add Debian 10 (buster) as a supported platform
Title: Message Title Maggie Dreyer commented on PDB-4469 Re: Add Debian 10 (buster) as a supported platform The tickets for all the Debian 10 master work have been filed as RE-12746. 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.319689.1565038845000.88982.1567788360739%40Atlassian.JIRA.
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Jorie Tappa updated an issue Puppet Strings / PDOC-273 puppet-strings should pull documentation from the lib folder too Change By: Jorie Tappa 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.294635.1549292365000.88986.1567788360754%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Change By: Jorie Tappa Labels: IPv6 Sprint: Platform Core KANBAN Coremunity Hopper 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.295251.154953565.88969.1567788300773%40Atlassian.JIRA.
Jira (PDB-4501) Enable debian-10-x86_64 test pipeline for puppetdb
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-4501 Enable debian-10-x86_64 test pipeline for puppetdb Issue Type: Task Assignee: Unassigned Created: 2019/09/06 9:32 AM Priority: Normal Reporter: Molly Waggett Add debian-10-x86_64 to puppetdb test matrices in ci-job-configs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4500) Enable debian-10-x86_64 builds for puppetdb
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-4500 Enable debian-10-x86_64 builds for puppetdb Issue Type: Task Assignee: Unassigned Created: 2019/09/06 9:32 AM Priority: Normal Reporter: Molly Waggett 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.323856.1567
Jira (FACT-2013) Build Facter for JRuby on debian-10-x86_64
Title: Message Title Molly Waggett created an issue Facter / FACT-2013 Build Facter for JRuby on debian-10-x86_64 Issue Type: Task Assignee: Unassigned Created: 2019/09/06 9:31 AM Priority: Normal Reporter: Molly Waggett The Facter configurations in puppet-agent needs to be updated to build Facter for JRuby on debian-10-x86_64. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10012) Impact Analysis Collection Follow-up
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10012 Impact Analysis Collection Follow-up Change By: Maggie Dreyer Epic Colour: ghx-label- 3 9 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.323829.156778568.88727.1567785780296%40Atlassian.JIRA.
Jira (PUP-10012) Impact Analysis Collection Follow-up
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10012 Impact Analysis Collection Follow-up Change By: Maggie Dreyer Epic Colour: ghx-label- 5 3 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.323829.156778568.88726.1567785780292%40Atlassian.JIRA.
Jira (PUP-10012) Impact Analysis Collection Follow-up
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-10012 Impact Analysis Collection Follow-up Issue Type: Epic Assignee: Unassigned Created: 2019/09/06 9:01 AM Priority: Normal Reporter: Maggie Dreyer For Lovejoy, we added instrumentation to Puppet to collect which Hiera keys are looked up during a compile. There are a few related tasks that we still need to do soonish: 1) Collect similar data for function calls and template evaluation 2) Add analytics Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9934) AIX user resource fails
Title: Message Title
Gabriel Nagy commented on PUP-9934
Re: AIX user resource fails
Hi, I can't reproduce this with Puppet 6.5.0 under AIX 7.2 with oslevel 7200-00-02-1614 and manifest:
user { 'test':
ensure => present,
name => 'test',
password => 'encryptedpassword',
}
Info: Applying configuration version '1567778749'
Debug: Executing: '/usr/sbin/lsuser -c test'
Debug: Executing: '/usr/sbin/lsgroup -c -a id ALL'
Debug: Executing: '/bin/chpasswd -e -c'
Notice: /Stage[main]/Main/User[test]/password: changed [redacted] to [redacted]
Debug: /User[test]: The container Class[Main] will propagate my refresh event
Debug
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title Patrick Grant updated an issue Puppet / PUP-9996 Stdlib : ensure_resources function does not throw an error if dependent resource type is missing Change By: Patrick Grant 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.323404.1567607979000.88497.1567772340106%40Atlassian.JIRA.
Jira (PUP-10011) Tidy resource remove files even dependencies are failed
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10011 Tidy resource remove files even dependencies are failed Change By: Patrick Grant Team: Coremunity Issue Type: Task 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.323802.1567763238000.88495.1567771080276%40Atlassian.JIRA.
Jira (PUP-10011) Tidy resource remove files even dependencies are failed
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10011 Tidy resource remove files even dependencies are failed Change By: Patrick Grant CS Priority: Needs Priority 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.323802.1567763238000.88487.1567770360136%40Atlassian.JIRA.
Jira (PUP-9934) AIX user resource fails
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-9934 AIX user resource fails Change By: Gabriel Nagy Assignee: Gabriel Nagy 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.319111.1564634229000.88485.1567770300334%40Atlassian.JIRA.
Jira (FACT-1992) autofs mountpoints being mounted by facter
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-1992 autofs mountpoints being mounted by facter Change By: Gabriel Nagy Assignee: Gabriel Nagy 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.321294.156596424.88430.1567763700230%40Atlassian.JIRA.
Jira (PUP-10011) Tidy resource remove files even dependencies are failed
Title: Message Title
Henry Wang created an issue
Puppet / PUP-10011
Tidy resource remove files even dependencies are failed
Issue Type:
Task
Affects Versions:
PUP 6.4.3
Assignee:
Unassigned
Created:
2019/09/06 2:47 AM
Priority:
Normal
Reporter:
Henry Wang
Hi team, We got a problem regarding tidy resource. If we put a require => in tidy resource, for example require => Package['v'], if the package is failed to be absent, tidy will still remove files and then raise the Warning "Skipping because of failed depencies" For example, I write a simple Puppet code and tried to apply it: package { 'v': ensure => installed, } tidy { 'cleanup /tmp/tidytest': require => Package['v'], path => '/tmp/tidytest', age => '0', recurse => 1, rmdirs => false, matches => ['*'], } file { '/tmp/testfile.doc': ensure => present, require => Package['v'], } Due to package will not be installed. Then the result is /tmp/testfile.doc will not be created but all files under /tmp/tidytest will be removed. Both resources will raise the "Skipping because of failed depencies" but apparantly, tidy is triggered. Debug: Executing: '/bin/yum -d 0 -e 0 -y install v' Error: Execution of '/bin/yum -d 0 -e 0 -y install v' returned 1: Error: Nothing to do Error: /Stage[main]/Main/Package[v]/ensure: change from 'purged' to 'present' failed: Execution of '/bin/yum -d 0 -e 0 -y install v' returned 1: Error: Nothing to do Debug: /Stage[main]/Main/File[/tmp/tidytest/2]: Removing existing file for replacement with absent Notice: /Stage[main]/Main/File[/tmp/tidytest/2]/ensure: removed Debug: /Stage[main]/Main/File[/tmp/tidytest/2]: The container Class[Main] will propagate my refresh event Debug: /Stage[main]/Main/File[/tmp/tidytest/1]: Removing existing file for replacement with absent Notice: /Stage[main]/Main/File[/tmp/tidytest/1]/ensure: removed Debug: /Stage[main]/Main/File[/tmp/tidytest/1]: The container Class[Main] will propagate my refresh event Notice: /Stage[main]/M
