Jira (PUP-11432) Debian package versions don't allow for clean upgrades
Title: Message Title Kenyon Ralph created an issue Puppet / PUP-11432 Debian package versions don't allow for clean upgrades Issue Type: Bug Assignee: Unassigned Created: 2022/01/22 10:37 AM Priority: Normal Reporter: Kenyon Ralph Please use Debian package versions that sort properly across Debian releases. Currently, when upgrading from Debian 10 buster to Debian 11 bullseye for example, the buster package versions are higher than the bullseye versions, which means you have to manually upgrade these packages: % apt policy puppet-agent puppetserver puppetdb puppet-agent: Installed: 7.14.0-1buster Candidate: 7.14.0-1buster Version table: *** 7.14.0-1buster 100
Jira (PDB-5388) make a new module release
Title: Message Title Kenyon Ralph commented on PDB-5388 Re: make a new module release Blocking https://github.com/voxpupuli/puppet-puppetboard/pull/337 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.426892.1639136324000.3556.1639170480028%40Atlassian.JIRA.
Jira (PUP-10950) unless should support sensitive data for any type
Title: Message Title
Kenyon Ralph updated an issue
Puppet / PUP-10950
unless should support sensitive data for any type
Change By:
Kenyon Ralph
*Puppet Version:6.22.0* (was able to reproduce the problem on puppet6-nightly and puppet7-nightly) *OS Name/Version:Ubuntu 18.04 (*on all OSes*)**Sensitive masking is not implemented in core puppet at the points where the module needs it:*Using 'Sensitive' in 'unless' throws the following error{code:java}Unable to mark 'unless' as sensitive: unless is a parameter and not a property, and cannot be automatically redacted.{code}*Steps to reproduce the problem*Install the latest version of postgresql module (v6.10.2 and above) which we uses sensitive for security fixes.puppet module install puppetlabs-postgresql --version 7.0.0Apply the following manifest {code:java}test.ppclass { 'postgresql::server': } postgresql::server::role { testuser: password_hash => postgresql::postgresql_password('testuser', 'testpw'), } puppet apply test.ppNotice: Compiled catalog for oval-secrecy.delivery.puppetlabs.net in environment production in 0.37 secondsWarning: /Postgresql_psql[ALTER ROLE testuser ENCRYPTED PASSWORD ]: Unable to mark 'unless' as sensitive: unless is a parameter and not a property, and cannot be automatically redacted.Notice: /Stage[main]/Main/Postgresql::Server::Role[testuser]/Postgresql_psql[CREATE ROLE testuser ENCRYPTED PASSWORD ]/command: changed [redacted] to [redacted]Notice: Applied catalog in 1.01 secondsroot@oval-secrecy:~#{code} *Desired Behavior:*unless should support sensitive data*Actual Behavior:*Throws the below error on unless *Unable to mark 'unless' as sensitive: unless is a parameter and not a property, and cannot be automatically redacted.*Found similar tickets for exec type https : //tickets.puppetlabs.com/browse/ PUP-8399Please let us know if you need more information.
Add Comment
Jira (FACT-2477) On Debian, include lsb-release as deb dependency
Title: Message Title Kenyon Ralph commented on FACT-2477 Re: On Debian, include lsb-release as deb dependency Just a note that the os fact indeed does not depend on lsb-release, but the legacy facts like lsbdistcodename do. But in this case the things using legacy facts should be updated instead. Related: PA-3543 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.350224.1584487795000.129167.1611974400032%40Atlassian.JIRA.
Jira (PUP-10850) Puppet facts show doesn't have an option to opt out of legacy facts
Title: Message Title Kenyon Ralph commented on PUP-10850 Re: Puppet facts show doesn't have an option to opt out of legacy facts The release notes should be fixed then. "By default, puppet facts show displays all facts, including legacy facts. This release adds a --no-legacy option to disable legacy facts when querying all facts. PUP-10850" – https://puppet.com/docs/puppet/7.3/release_notes_puppet.html#release_notes_puppet 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.382858.1610379246000.120125.1611173280031%40Atlassian.JIRA.
Jira (FACT-2906) Dependency to lsb packages is missing
Title: Message Title Kenyon Ralph commented on FACT-2906 Re: Dependency to lsb packages is missing I think this is a good idea. Related: https://github.com/puppetlabs/puppetlabs-apt/pull/964 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.381525.1608468982000.104706.1608505740026%40Atlassian.JIRA.
Jira (FACT-2895) Add networking.primary6 fact
Title: Message Title Kenyon Ralph commented on FACT-2895 Re: Add networking.primary6 fact Bogdan Irimie https://github.com/puppetlabs/facter/pull/2241 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.380478.1607513744000.104075.1608284880289%40Atlassian.JIRA.
Jira (FACT-2891) Facter 4.0.46 (from puppet 7) breaks virtual flag
Title: Message Title Kenyon Ralph commented on FACT-2891 Re: Facter 4.0.46 (from puppet 7) breaks virtual flag As a workaround, try having lspci installed (from the pciutils package on Debian), if it's not already there. I found this in https://tickets.puppetlabs.com/browse/FACT-2081?focusedCommentId=771889=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-771889 (if it's already installed, then this is a distinct bug) 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.380171.1607408588000.93204.1607417580038%40Atlassian.JIRA.
Jira (FACT-2871) Regression: interfaces without an ipaddress assigned are not anymore reported
Title: Message Title Kenyon Ralph commented on FACT-2871 Re: Regression: interfaces without an ipaddress assigned are not anymore reported Andrei Filipovici don't forget about the -json option like ip -json addr show to get nice JSON for easy and parsing. 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.379055.160591045.93190.1607417100032%40Atlassian.JIRA.
Jira (FACT-2888) networking.interfaces fact nonexistent
Title: Message Title
Kenyon Ralph updated an issue
Facter / FACT-2888
networking.interfaces fact nonexistent
Change By:
Kenyon Ralph
Puppet 7, Facter 4.0.46. Same problem as FACT-2886, but this only happens for me on my IPv6-only Vultr VM, so I'm not sure if it's the same root cause as FACT-2886. My other nodes have IPv6 and IPv4, and their {{networking.interfaces}} works just fine.See attached logs.Note that the {{fill_io_v6_info!}} method ("io" is probably a typo for "ip" in that method name, btw) doesn't produce any debug output.Also note that even though {{facter networking}} shows the {{interfaces}} fact, there are a bunch of facts missing: ip, ip6, netmask, netmask6, network, network6, both at the {{networking}} level and at the {{networking.interfaces.}} level, and primary. These facts all worked fine with the Facter 3 version included with Puppet 6.19.
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
Jira (FACT-2888) networking.interfaces fact nonexistent
Title: Message Title Kenyon Ralph updated an issue Facter / FACT-2888 networking.interfaces fact nonexistent Change By: Kenyon Ralph Labels: platform_7 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.379996.1607227122000.92112.1607228400089%40Atlassian.JIRA.
Jira (FACT-2888) networking.interfaces fact nonexistent
Title: Message Title Kenyon Ralph updated an issue Facter / FACT-2888 networking.interfaces fact nonexistent Change By: Kenyon Ralph Component/s: Facter 4 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.379996.1607227122000.92111.1607228400043%40Atlassian.JIRA.
Jira (FACT-2888) networking.interfaces fact nonexistent
Title: Message Title Kenyon Ralph updated an issue Facter / FACT-2888 networking.interfaces fact nonexistent Change By: Kenyon Ralph Affects Version/s: FACT 4.0.46 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.379996.1607227122000.92110.1607228340028%40Atlassian.JIRA.
Jira (FACT-2888) networking.interfaces fact nonexistent
Title: Message Title
Kenyon Ralph updated an issue
Facter / FACT-2888
networking.interfaces fact nonexistent
Change By:
Kenyon Ralph
Same problem as FACT-2886, but this only happens for me on my IPv6-only Vultr VM, so I'm not sure if it's the same root cause as FACT-2886. My other nodes have IPv6 and IPv4, and their {{networking.interfaces}} works just fine.See attached logs.Note that the {{fill_io_v6_info!}} method ("io" is probably a typo for "ip" in that method name, btw) doesn't produce any debug output.Also note that even though {{facter networking}} shows the {{interfaces}} fact, there are a bunch of facts missing , like : ip, ip6, netmask, netmask6, network, network6, and primary, both at the {{networking}} level and at the {{networking.interfaces.}} level , and primary .
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
Jira (FACT-2888) networking.interfaces fact nonexistent
Title: Message Title
Kenyon Ralph updated an issue
Facter / FACT-2888
networking.interfaces fact nonexistent
Change By:
Kenyon Ralph
Same problem as FACT-2886, but this only happens for me on my IPv6-only Vultr VM, so I'm not sure if it's the same root cause as FACT-2886. My other nodes have IPv6 and IPv4, and their {{networking.interfaces}} works just fine.See attached logs.Note that the {{fill_io_v6_info!}} method ("io" is probably a typo for "ip" in that method name, btw) doesn't produce any debug output. Also note that even though {{facter networking}} shows the {{interfaces}} fact, there are a bunch of facts missing, like ip, ip6, netmask, netmask6, network, network6, and primary, both at the {{networking}} level and at the {{networking.interfaces.}} level.
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
Jira (FACT-2888) networking.interfaces fact nonexistent
Title: Message Title
Kenyon Ralph updated an issue
Facter / FACT-2888
networking.interfaces fact nonexistent
Change By:
Kenyon Ralph
Same problem as FACT-2886, but this only happens for me on my IPv6-only Vultr VM, so I'm not sure if it's the same root cause as FACT-2886. My other nodes have IPv6 and IPv4, and their {{networking.interfaces}} works just fine.See attached logs.Note that the {{fill_io_v6_info!}} method ("io" is probably a typo for "ip" in that method name, btw) doesn't produce any debug output.
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.379996.1607227122000.92107.1607227320030%40Atlassian.JIRA.
Jira (FACT-2887) retrieve_default_interface uses incorrect method and doesn't work when IPv6-only
Title: Message Title
Kenyon Ralph updated an issue
Facter / FACT-2887
retrieve_default_interface uses incorrect method and doesn't work when IPv6-only
Change By:
Kenyon Ralph
Here: https://github.com/puppetlabs/facter/blob/2c87e9e700dc1f75bda71f3a7805449f37fa1945/lib/facter/resolvers/networking_linux_resolver.rb#L144{{ip route get 1}} is not the right way to get the default route egress interface. That's the equivalent of {{ip route get 1.0.0.0}}. There is nothing special about the 1.0.0.0 address, so it should not be treated like a way to find out the default route egress interface.A better way to get the default route egress interface would be to use the output of {{ip route show default}}. This is how it's done with the old tools here: https://github.com/puppetlabs/facter/blob/23a6be6494c0729eaf439e173020bb3be88b75c6/lib/facter/resolvers/networking_resolver.rb#L23 Also, this method currently neglects to take IPv6 into consideration. There should be a retrieve_default_interface_v6 method that looks at {{ip -6 route show default}} and populates a {{networking.primary6}} fact.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2888) networking.interfaces fact nonexistent
Title: Message Title
Kenyon Ralph created an issue
Facter / FACT-2888
networking.interfaces fact nonexistent
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
facter-networking-trace-debug.txt, puppet-facts-show-networking-debug.txt
Created:
2020/12/05 7:58 PM
Priority:
Normal
Reporter:
Kenyon Ralph
Same problem as FACT-2886, but this only happens for me on my IPv6-only Vultr VM, so I'm not sure if it's the same root cause as FACT-2886. My other nodes have IPv6 and IPv4, and their networking.interfaces works just fine. See attached logs. Note that the fill_io_v6_info! ("io" is probably a typo for "ip" in that method name, btw) doesn't produce any debug output.
Add Comment
Jira (FACT-2887) retrieve_default_interface uses incorrect method and doesn't work when IPv6-only
Title: Message Title Kenyon Ralph created an issue Facter / FACT-2887 retrieve_default_interface uses incorrect method and doesn't work when IPv6-only Issue Type: Bug Assignee: Unassigned Created: 2020/12/05 7:22 PM Priority: Normal Reporter: Kenyon Ralph Here: https://github.com/puppetlabs/facter/blob/2c87e9e700dc1f75bda71f3a7805449f37fa1945/lib/facter/resolvers/networking_linux_resolver.rb#L144 ip route get 1 is not the right way to get the default route egress interface. That's the equivalent of ip route get 1.0.0.0. There is nothing special about the 1.0.0.0 address, so it should not be treated like a way to find out the default route egress interface. A better way to get the default route egress interface would be to use the output of ip route show default. Also, this method currently neglects to take IPv6 into consideration. There should be a retrieve_default_interface_v6 method that looks at ip -6 route show default and populates a networking.primary6 fact. Add Comment
Jira (FACT-2081) Facter virtual and is_virtual are wrong
Title: Message Title
Kenyon Ralph commented on FACT-2081
Re: Facter virtual and is_virtual are wrong
Here is the problem: in https://github.com/puppetlabs/facter/blob/master/lib/src/facts/linux/virtualization_resolver.cc it uses lspci to detect virtualization. On my VMs, I do not have lspci (from the pciutils package on Debian) installed by default. Installing pciutils fixes the facts:
kenyon@alpha ~ % sudo aptitude install pciutils
The following NEW packages will be installed:
libpci3{a} [1:3.5.2-1] pciutils [1:3.5.2-1]
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 336 kB of archives. After unpacking 1,354 kB will be used.
Do you want to continue? [Y/n/?]
Get: 1 https://deb.debian.org/debian buster/main amd64 libpci3 amd64 1:3.5.2-1 [56.5 kB]
Get: 2 https://deb.debian.org/debian buster/main amd64 pciutils amd64 1:3.5.2-1 [279 kB]
Fetched 336 kB in 0s (3,876 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Jira (FACT-2081) Facter virtual and is_virtual are wrong
Title: Message Title Kenyon Ralph updated an issue Facter / FACT-2081 Facter virtual and is_virtual are wrong Change By: Kenyon Ralph Affects Version/s: FACT 4.0.46 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.331929.1571915917000.92078.1607202900036%40Atlassian.JIRA.
Jira (FACT-2081) Facter virtual and is_virtual are wrong
Title: Message Title Kenyon Ralph updated an issue Facter / FACT-2081 Facter virtual and is_virtual are wrong Change By: Kenyon Ralph Priority: Normal Critical 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.331929.1571915917000.92077.1607202840029%40Atlassian.JIRA.
Jira (FACT-2081) Facter virtual and is_virtual are wrong
Title: Message Title Kenyon Ralph updated an issue Facter / FACT-2081 Facter virtual and is_virtual are wrong Change By: Kenyon Ralph Summary: Facter virtual and is_virtual are worng wrong 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.331929.1571915917000.92074.1607200860026%40Atlassian.JIRA.
Jira (FACT-2081) Facter virtual and is_virtual are worng
Title: Message Title Kenyon Ralph commented on FACT-2081 Re: Facter virtual and is_virtual are worng Same problem with Puppet Collection 7. kenyon@puppet ~ % facter --version 4.0.46 kenyon@puppet ~ % uname --all Linux puppet 5.6.14-x86_64-linode135 #1 SMP PREEMPT Fri May 22 14:57:20 UTC 2020 x86_64 GNU/Linux kenyon@puppet ~ % lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 40 bits physical, 48 bits virtual CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1
Jira (PUP-10656) Provide a JSON terminus for facts
Title: Message Title Kenyon Ralph updated an issue Puppet / PUP-10656 Provide a JSON terminus for facts Change By: Kenyon Ralph We have a YAML terminus for facts, however YAML can problematic for hexidecimal hexadecimal numbers (see PUP-9505).Additionally, JSON is generally a better serialization format for machines to understand, is a smaller spec than YAML, has a relatively mature ecosystem in Java around parsing/serializing, and is backwards compatible with YAML for recent YAML parsers (YAML has become a superset of JSON).For these reasons we should implement a JSON terminus for facts (there already exists one for catalogs) and users should be encouraged to use it instead of the YAML terminus. 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
Jira (PUP-7918) puppet fails to change user group membership if directory group names have spaces
Title: Message Title Kenyon Ralph commented on PUP-7918 Re: puppet fails to change user group membership if directory group names have spaces Actually, correction to my previous comment: I overlooked at least one group name with a space in it. 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.209406.1504722903000.50264.1602024540027%40Atlassian.JIRA.
Jira (PUP-7918) puppet fails to change user group membership if directory group names have spaces
Title: Message Title Kenyon Ralph commented on PUP-7918 Re: puppet fails to change user group membership if directory group names have spaces I suspect this is also a problem with groups with dots/periods in their names. I don't have any groups with spaces, but I have groups with underscores, and groups with dots, and get the same error, "Groups must be comma-separated", when trying to manage a user resource and modify the groups attribute. Relevant discussion with references to POSIX: https://unix.stackexchange.com/a/11481/8945 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.209406.1504722903000.48347.1601686980025%40Atlassian.JIRA.
Jira (PUP-7428) Implement knockout prefix for unique lookups
Title: Message Title Kenyon Ralph commented on PUP-7428 Re: Implement knockout prefix for unique lookups knockout_prefix should really be removed from the documentation so that people don't waste time rediscovering this bug like I just did. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title Kenyon Ralph commented on PUP-8405 Re: Knock-out-prefix fails with more than 3 merges This seems to be a duplicate of PUP-7428 (and this is a bug that just bit me as well, trying to remove a class in a node that's added by the common level). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
