Jira (PUP-11814) loadbalancing documentation is unclear
Title: Message Title Tim Meusel commented on PUP-11814 Re: loadbalancing documentation is unclear Sorry, this was supposed to be a DOCUMENT ticket, could you please move it? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.483958.1680805807000.3527.1680805920020%40Atlassian.JIRA.
Jira (PUP-11814) loadbalancing documentation is unclear
Title: Message Title Tim Meusel created an issue Puppet / PUP-11814 loadbalancing documentation is unclear Issue Type: Task Assignee: Unassigned Created: 2023/04/06 11:30 AM Priority: Normal Reporter: Tim Meusel Hi, https://www.puppet.com/docs/pe/2021.7/installing_compilers.html#using-load-balancers-with-compilers-load_balancing_for_orchestration_scale is a bit unclear. Two quotes: > If you're not using HTTP health checks, we recommend using a round robin or random load balancing algorithm for PXP agent > Due to the diverse nature of the network communications between the agent and the primary server, we recommend that you implement a load balancing algorithm that distributes traffic between compilers based on the number of open connections. Load balancers often refer to this strategy as "balancing by least connections." Does that mean for pxp agents "round robin" is recommended" and for puppet agents "least connections"? Add Comment
Jira (PDB-5569) RHEL9 packages for puppetdb
Title: Message Title Tim Meusel commented on PDB-5569 Re: RHEL9 packages for puppetdb Same as https://tickets.puppetlabs.com/browse/SERVER-3239. Some of our PE customers are also interested in this (especially since EL8 got dropped in the PE 2023 release). Are the any estimate for PuppetDB packages for EL9? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477996.1672946097000.3816.1674643740071%40Atlassian.JIRA.
Jira (PDB-5523) Add Ubuntu 22.04 Jammy (x86_64) FOSS support
Title: Message Title Tim Meusel commented on PDB-5523 Re: Add Ubuntu 22.04 Jammy (x86_64) FOSS support Hi people, Ubuntu 22 was released almost a year ago. Are there any plans to support PuppetDB on Ubuntu 22.04? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.458563.1660040376000.3793.1674642780022%40Atlassian.JIRA.
Jira (PUP-11722) concurrent-ruby 1.2.0 breaks puppet
Title: Message Title Tim Meusel commented on PUP-11722 Re: concurrent-ruby 1.2.0 breaks puppet Josh Cooper this currently breaks a lot if CI setups. Do you know if this will be shipped in Puppet 7.22 in the next couple of hours, or should we update Gemfiles to pin concurrent-ruby to 1.1.x? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.479492.1674507142000.3484.1674573300116%40Atlassian.JIRA.
Jira (PUP-10639) renew cached Puppet CA on Puppet client
Title: Message Title Tim Meusel commented on PUP-10639 Re: renew cached Puppet CA on Puppet client Hi, as a first step, what about a refresh interval, like we have it for the CRL, to update a not expired CA cert? The agent can establish the usual HTTPS connection and if that works, download a new CA cert. That would enable people to use short-lived certificated and automate their rollover. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.369858.1597923633000.69883.1672911360046%40Atlassian.JIRA.
Jira (PUP-11649) Drop support for ruby < 2.7
Title: Message Title Tim Meusel commented on PUP-11649 Re: Drop support for ruby < 2.7 Hi! I've a question. Why drop support for only Ruby 2.6 and older, and not even newer rubies? My understanding is that Puppet Agent packages will ship Ruby 3.2, so this could be used in the gemspec and for rubocop linting as well? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.470537.1665159191000.65597.1670861400034%40Atlassian.JIRA.
Jira (FACT-3168) networking.domain does resolv to dot
Title: Message Title Tim Meusel commented on FACT-3168 Re: networking.domain does resolv to dot Morgan Rhodes you closed this, but I still think this is a valid bug. Can you please elaborate why you closed it? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.475723.1669812351000.64066.1670404920240%40Atlassian.JIRA.
Jira (PUP-11680) puppet node purge documentation is misleading
Title: Message Title Tim Meusel commented on PUP-11680 Re: puppet node purge documentation is misleading I cloned it (I don't understand why you didn't do this and just closed it). Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.475432.166901847.59841.1669018680030%40Atlassian.JIRA.
Jira (PUP-11680) puppet node purge documentation is misleading
Title: Message Title Tim Meusel created an issue Puppet / PUP-11680 puppet node purge documentation is misleading Issue Type: Improvement Assignee: Unassigned Created: 2022/11/21 12:14 AM Priority: Normal Reporter: Tim Meusel Hi, I think the help for "puppet node purge" is a bit misleading: # puppet node --help USAGE: puppet node [--terminus _TERMINUS] This subcommand interacts with node objects, which are used by Puppet to build a catalog. A node object consists of the node's facts, environment,
Jira (FACT-2081) Facter virtual and is_virtual are wrong on OpenBSD
Title: Message Title
Tim Meusel commented on FACT-2081
Re: Facter virtual and is_virtual are wrong on OpenBSD
the virtual fact is also broken on Arch Linux:
docker run -it archlinux
pacman -Sy puppet
puppet facts show is_virtual virtual
This will give us:
{
"is_virtual": true,
"virtual": "kvm"
}
Systemd detects it properly:
systemd-detect-virt
it returns:
docker
Jira (PUP-11517) Tell puppet it needs a second run
Title: Message Title Tim Meusel commented on PUP-11517 Re: Tell puppet it needs a second run An alternative idea, that also comes up from time to time: tell puppet to collect facts again, during a run. And that's also actually what you need? It's not necessarily another Puppet run, you just need to update facts between two puppet resources? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.444665.1650652859000.34397.1663765380029%40Atlassian.JIRA.
Jira (PUP-11595) puppet lookup fails to resolve topscope variables from node classifier
Title: Message Title Tim Meusel commented on PUP-11595 Re: puppet lookup fails to resolve topscope variables from node classifier Hi people, is this something that can be fixed in the near future? this is a regression and the customer relies on this feature. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.456630.165875490.21693.1661420580050%40Atlassian.JIRA.
Jira (PUP-11595) puppet lookup fails to resolve topscope variables from node classifier
Title: Message Title
Tim Meusel created an issue
Puppet / PUP-11595
puppet lookup fails to resolve topscope variables from node classifier
Issue Type:
Bug
Affects Versions:
PUP 6.27.0
Assignee:
Unassigned
Created:
2022/07/25 6:15 AM
Priority:
Normal
Reporter:
Tim Meusel
Puppet Version: 6.27.0 / 7.16.0 Puppet Server Version: 2019.8.11 / 2021.6.0 OS Name/Version: RHEL 8 We've a hiera.yaml that uses topscope facts within paths, like data/%{::tier}.yaml. With PE 2019.8.9, this worked fine. In https://tickets.puppetlabs.com/browse/PUP-7479 puppet lookup was broke due to a regression (and released in PE 2019.8.10). This was fixed in parts in https://tickets.puppetlabs.com/browse/PUP-11437 (and released in PE 2019.8.11). I also placed a comment in https://tickets.puppetlabs.com/browse/PUP-11437 and a slack thread at https://puppetcommunity.slack.com/archives/C19V5U41Z/p1658312927398119 Desired Behavior: puppet lookup --node $(hostname -f) --compile --environment $hiera_key should work as expected. Actual Behavior: puppet lookup fails to resolve the variable. When hiera.yaml uses data/%{::tier}.yaml, puppet lookup will look into data/.yaml. I raised a PE support ticket for this. Jarret Lavallee suggested this patch (on the 6.27.0 git tag):
diff --git a/lib/puppet/application/lookup.rb b/lib/puppet/application/lookup.rb
index b9e6f22c87..cc6affcb9e 100644
Jira (PUP-11593) Puppet chooses wrong service default provider on Gentoo if systemd is used
Title: Message Title Tim Meusel created an issue Puppet / PUP-11593 Puppet chooses wrong service default provider on Gentoo if systemd is used Issue Type: Bug Assignee: Unassigned Created: 2022/07/18 1:17 AM Priority: Normal Reporter: Tim Meusel Puppet Version: 7.17 Puppet Server Version: tested with puppet apply OS Name/Version: latest Gentoo with systemd Gentoo supports a few init systems, where the default is openrc. If openrc is used, puppet works fine. However if you opt-in to systemd, puppet won't detect that properly Desired Behavior: puppet should check if systemd is running and then use that as default provider Actual Behavior: systemd provider isn't used I have a fix at https://github.com/puppetlabs/puppet/pull/8919. let me know if you need any debug logs. Add Comment
Jira (PUP-11587) IPv6 missing on pm.puppet.com / pm.puppetlabs.com
Title: Message Title Tim Meusel created an issue Puppet / PUP-11587 IPv6 missing on pm.puppet.com / pm.puppetlabs.com Issue Type: Bug Assignee: Unassigned Created: 2022/07/06 2:26 AM Priority: Normal Reporter: Tim Meusel Hi, I think there once was a project for release engineering, but I cannot see that anymore. That might be better placed. The Download Portal for Puppet Enterprise Agents/Server is missing records: $ host pm.puppet.com pm.puppet.com is an alias for pe-downloads-web-prod-1973435458.us-west-2.elb.amazonaws.com. pe-downloads-web-prod-1973435458.us-west-2.elb.amazonaws.com has address 52.33.126.181 pe-downloads-web-prod-1973435458.us-west-2.elb.amazonaws.com has address 52.43.73.108 $ host pm.puppetlabs.com pm.puppetlabs.com is an alias for pm.puppet.com.
Jira (PUP-11437) puppet lookup fails to interpolate topscope variables when an environment is specified
Title: Message Title Tim Meusel commented on PUP-11437 Re: puppet lookup fails to interpolate topscope variables when an environment is specified Hi josh, I'm currently testing on PE 2019 with Puppet Agent 6.27.0 and PE 2021 with Puppet Agent 7.16.0. I have topscope variables set in nodegroups in the PE console. I use those in hiera.yaml. Normal puppet agent runs works fine. I'm not able to lookup keys in Hiera with `puppet lookup` because it cannot resolve the topscope variables. I think fixing that wasn't the intention of the PR? puppet lookup now resolves facts, that are written as topscope variables, but not all topscope variables? If my assumption is true I think the text in the release notes should be updated, it's a bit missleading. 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.432982.1643328691000.50616.1655730060033%40Atlassian.JIRA.
Jira (FACT-3114) operatingsystemrelease/operatingsystemmajrelease missing on Arch Linux
Title: Message Title Tim Meusel commented on FACT-3114 Re: operatingsystemrelease/operatingsystemmajrelease missing on Arch Linux I hacked something together in https://github.com/puppetlabs/facter/pull/2483 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.444551.1650549319000.16432.1650637860126%40Atlassian.JIRA.
Jira (FACT-3114) operatingsystemrelease/operatingsystemmajrelease missing on Arch Linux
Title: Message Title
Tim Meusel commented on FACT-3114
Re: operatingsystemrelease/operatingsystemmajrelease missing on Arch Linux
josh I'm not sure if I can bring up a PR, but I can give it a try. The question is, which value do we want? In facter 3, the major kernel version was used as OS version:
$ facter facterversion os
facterversion => 3.14.22
os => {
architecture => "x86_64",
distro => {
codename => "n/a",
description => "Arch Linux",
id => "Arch",
release => {
full => "rolling",
major => "rolling"
},
specification => "n/a"
Jira (FACT-3114) operatingsystemrelease/operatingsystemmajrelease missing on Arch Linux
Title: Message Title
Tim Meusel created an issue
Facter / FACT-3114
operatingsystemrelease/operatingsystemmajrelease missing on Arch Linux
Issue Type:
Bug
Assignee:
Unassigned
Created:
2022/04/21 6:55 AM
Priority:
Normal
Reporter:
Tim Meusel
Hi, the legacy facts operatingsystemrelease/operatingsystemmajrelease are missing on Arch Linux:
[root@foo ~]# /root/.local/share/gem/ruby/3.0.0/bin/facter --show-legacy os
{
architecture => "x86_64",
distro => {
codename => "n/a",
description => "Arch Linux",
id => "Arch",
Jira (FACT-3108) opensuse OS fact differs between facter 3/4
Title: Message Title
Tim Meusel created an issue
Facter / FACT-3108
opensuse OS fact differs between facter 3/4
Issue Type:
Bug
Assignee:
Unassigned
Created:
2022/03/03 10:20 PM
Priority:
Normal
Reporter:
Tim Meusel
Hi, we recently updated opensuse 15 fact sets in facterdb: https://github.com/voxpupuli/facterdb/pull/241. That PR contains also the Vagrant box to reproduce. The OS facts on all facter 4 releases:
"os": {
"architecture": "x86_64",
"distro": {
"codename": "n/a",
"description": "openSUSE Leap 15.4 Beta",
"id": "SUSE",
"release": {
Jira (PUP-9473) Systemd daemon-reload doesn't get triggered for removal of unit file
Title: Message Title Tim Meusel commented on PUP-9473 Re: Systemd daemon-reload doesn't get triggered for removal of unit file Hey puppet. This is currently marked as 'needs information'. Is that state correct? Is there anything missing from Ewouds description? andreas.pa...@univie.ac.at I don't think your suggestion is the correct way forward. This is a valid workaround, but not a valid bugfix. Puppet has a built-in szstemctl daemon-reload since 6.1, it's just not triggered correctly in all usecase. See https://tickets.puppetlabs.com/browse/PUP-3483 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.294694.154930163.15898.1644912600063%40Atlassian.JIRA.
Jira (FACT-3091) Facter is missing the sys-filesystems gem
Title: Message Title Tim Meusel commented on FACT-3091 Re: Facter is missing the sys-filesystems gem This came up on IRC again. We found https://tickets.puppetlabs.com/browse/FACT-3106. Due to this the factsets in facterdb are inconsistent. Because you don't pull in all the depencencies/not even document it. Can you please fix this? 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.422725.1636446253000.14389.1644582600029%40Atlassian.JIRA.
Jira (FACT-3106) No virt-what in puppet-agent 7 so is_virtual is wrong
Title: Message Title Tim Meusel updated an issue Facter / FACT-3106 No virt-what in puppet-agent 7 so is_virtual is wrong Change By: Tim Meusel In factor facter the is_virtual and other similar facts are very dependent upon thevirt-whatcommand being available. Since this commit to puppet-agent[https://github.com/puppetlabs/puppet-agent/commit/a1a06ba3f42419e]virt-what was removed from the puppet-agent package.I expect it may have been an unintentional consequence to stop these core facts from working out of the box with the puppet-agent package?Installing the system provided virt-what and everything works again but this should be a dep or at least documented if that is the way forward. For reference some history on the subject.https://tickets.puppetlabs.com/browse/FACT-822 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
Jira (HI-627) Update CI matrix to verify it works on ruby 2.7/3
Title: Message Title Tim Meusel commented on HI-627 Re: Update CI matrix to verify it works on ruby 2.7/3 Now that Ruby 3.1 is out, it would be quite helpful to have that as well. 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.410076.1628192723000.14183.1644570540025%40Atlassian.JIRA.
Jira (PUP-11347) `puppet parser validate` ignores plans
Title: Message Title Tim Meusel commented on PUP-11347 Re: `puppet parser validate` ignores plans > In other words, you could pass either --tasks or --plans, but we'd prefer and document --plans (similar to what we do for serverport & masterport). I agree with you. I think that's a good way. > Please file a PDK ticket for that. https://tickets.puppetlabs.com/browse/PDK-1774 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.423063.163654689.14181.1644570180051%40Atlassian.JIRA.
Jira (PUP-9578) Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`
Title: Message Title Tim Meusel commented on PUP-9578 Re: Remove distinction between `puppet parser validate` and `puppet parser validate --tasks` Ping I noticed this a few times during trainings and I think fixing this would lower the entrybar for newcomers. 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.301178.155320275.14176.1644568680036%40Atlassian.JIRA.
Jira (PUP-11430) Drop support for legacy facts in Puppet 8
Title: Message Title Tim Meusel created an issue Puppet / PUP-11430 Drop support for legacy facts in Puppet 8 Issue Type: Task Assignee: Unassigned Created: 2022/01/20 1:54 AM Priority: Normal Reporter: Tim Meusel Hi! https://puppet.com/docs/puppet/7/core_facts.html mentions a few facts that are listed as legacy for some time. I think puppet 8 (or facter 5?) would be a good time to drop them. The structured facts provide alternatives and the reduced amount of facts would be helpful to reduce the data sent to puppetdb. Do you already have a timeline here? Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (FACT-3091) Facter is missing the sys-filesystems gem
Title: Message Title Tim Meusel commented on FACT-3091 Re: Facter is missing the sys-filesystems gem Is there any documentation about those gems? I'm the package maintainer for facter on Arch Linux. For ruby stuff I usually get all deps from the gemspec/gemfile. We had a few issues in the past on facter where some gems aren't a hard requirement but provide additional facts when available. 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.422725.1636446253000.20181.1642068960061%40Atlassian.JIRA.
Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Tim Meusel commented on FACT-3065 Re: submit facts for new facter releases to facterdb hey, thanks for all the work! I'm not sure if rspec-puppet-facts would work out of the box with the patch releases in the directory names / if more factsets would provide some benefit. In the past we sometimes also updated existing factsets, that were created with one facter release, with a newer patch release. ekohl alexjfisher do you have any preference here? 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.412672.1629371747000.5561.1639511340257%40Atlassian.JIRA.
Jira (PDB-5388) make a new module release
Title: Message Title Tim Meusel created an issue PuppetDB / PDB-5388 make a new module release Issue Type: Task Assignee: Unassigned Created: 2021/12/10 3:38 AM Priority: Normal Reporter: Tim Meusel Hi, puppetlabs-stdlib 8 got released on 2021-08-24. The latest puppetlabs-puppetdb module still doesn't support it. can you please: make a new release? main branch already supports stdlib 8 ensure for future releases that puppetlabs owned modules support each other Add Comment
Jira (PUP-11366) Puppet accepts Variant as correct type
Title: Message Title
Tim Meusel created an issue
Puppet / PUP-11366
Puppet accepts Variant as correct type
Issue Type:
Bug
Affects Versions:
PUP 7.12.0
Assignee:
Unassigned
Created:
2021/11/18 5:24 AM
Priority:
Normal
Reporter:
Tim Meusel
Hi, the following code isn't a parser error:
class bar ( Variant $foo = '', ) {}
$ cat test.pp
class bar ( Variant $foo = '', ) {}
$ puppet --version
7.12.1
Jira (PUP-11347) `puppet parser validate` ignores plans
Title: Message Title Tim Meusel created an issue Puppet / PUP-11347 `puppet parser validate` ignores plans Issue Type: Bug Assignee: Unassigned Created: 2021/11/10 4:21 AM Priority: Normal Reporter: Tim Meusel Hi, there are multiple issues about puppet failing to validate plans in puppet DSL or the confusing --tasks option (that's undocumented): https://tickets.puppetlabs.com/browse/PUP-8059?jql=text%20~%20%22parser%20validate%20plan%22 `puppet parser validate` ignores plans `puppet parser validate --tasks` validates plans the `--tasks` option isn't documented I think it's really confusing that tasks aren't validated by default. I tested that on puppet 6.25.0 and 7.12.1. Is there a reason for this? Also why enables the `--tasks` option validation for plans? shouldn't that be --plans? from `puppet parser validate` I would expect to validate all code, manifests and plans from the --tasks option I would expect to only validate tasks, not plans `pdk validate` in pdk 2.2 doesn't use --tasks options. It says it validates */.pp, but it actually validates manifests/*/.pp Since pdk is so commonly used, many people struggle to debug their plans/don't understand why they don't work, because the pass the pdk validation but have actual syntax errors. I think the following improvements would be really helpful: `puppet parser validate` should validate manifests and plans the validate/syntax rake task from
Jira (PUP-10403) Puppet parser --help is missing the --tasks flag
Title: Message Title Tim Meusel commented on PUP-10403 Re: Puppet parser --help is missing the --tasks flag hey people, the --tasks option is also missing in puppet 7.12.1. Could this be added in the near future? Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.353370.1585618793000.3542.1636546320027%40Atlassian.JIRA.
Jira (FACT-3091) Facter is missing the sys-filesystems gem
Title: Message Title Tim Meusel created an issue Facter / FACT-3091 Facter is missing the sys-filesystems gem Issue Type: Bug Assignee: Unassigned Created: 2021/11/09 12:24 AM Priority: Normal Reporter: Tim Meusel Hi, facter uses the sys-filesystems gem to create the mountpoints facts. The gem isn't listed as a dependency in the gemspec file. facter also doesn't provide any error message if the gem is missing, it just doesn't provide the mounpoints fact. This leads to some unexpected behaviour. Facterdb got some factsets where those facts were missing which killed some CI pipelines that depend on it. Also bolt user mentioned that the fact is missing within bolt but works within Puppet AIO. Because Puppet AIO vendored sys-filesystems explicitly. While I understand that sys-filesystems has native extensions and take slightly more time to install and requires a compiler, I still think that this behaviour is a bug and should be fixed by either replacing the gem with something else, or by adding it to the gemspec. Add Comment
Jira (PUP-11235) versioncmp() thinks 11.0 is greater than 11
Title: Message Title Tim Meusel commented on PUP-11235 Re: versioncmp() thinks 11.0 is greater than 11 The awesome Josh Cooper did some digging during the latest office-hours through the issue. The conversation: https://puppetcommunity.slack.com/archives/CFD8Z9A4T/p1631641997091600 tl;dr: > the algorithm is a little strange, if the version strings are different lengths, it'll always fall back to comparing the entire string... maybe it makes sense to add a python like coerce() method for all versioncmp() inputs? Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413995.1630486051000.129917.1631644380465%40Atlassian.JIRA.
Jira (PUP-10240) Puppet gem has no/missing development/test gems
Title: Message Title Tim Meusel commented on PUP-10240 Re: Puppet gem has no/missing development/test gems yes that's fine. as long as all of them are documented in the Gemfile or gemspec that's fine. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342644.1579458924000.123186.1630691040526%40Atlassian.JIRA.
Jira (PUP-11235) versioncmp() thinks 11.0 is greater than 11
Title: Message Title
Tim Meusel created an issue
Puppet / PUP-11235
versioncmp() thinks 11.0 is greater than 11
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/09/01 1:47 AM
Priority:
Normal
Reporter:
Tim Meusel
Puppet Version: 6.24.0 Puppet Server Version: none OS Name/Version: Debian 11 while debugging https://github.com/puppetlabs/puppetlabs-apache/pull/2186 i noticed that versioncmp('11.0', '11') doesn't return 0, it returns 1. Is that expected? Desired Behavior: I think 11.0 and 11 should be treated as equal Actual Behavior: versioncmp() thinks 11.0 is greater than 11 to debug:
notify { "operatingsystemrelease compared to 11: ${versioncmp($::operatingsystemrelease, '11')}":
}
notify { "operatingsystemmajrelease compared to 11: ${versioncmp($::operatingsystemmajrelease, '11')}":
}
notify { "operatingsystemrelease: ${::operatingsystemrelease}":
Jira (PUP-11218) require metaparam cannot be assinged to defined resource if inside var is named $require
Title: Message Title
Tim Meusel created an issue
Puppet / PUP-11218
require metaparam cannot be assinged to defined resource if inside var is named $require
Issue Type:
Task
Affects Versions:
PUP 6.23.0
Assignee:
Unassigned
Components:
Compiler
Created:
2021/08/23 7:23 AM
Priority:
Normal
Reporter:
Tim Meusel
Hi, if I'm using a variable named `$require` within a defined resource,I cannot add the $require metaparameter to it. Failing code:
package { 'htop':
ensure => 'insalled'
}
define bla {
$require = 'a string'
Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Tim Meusel created an issue Facter / FACT-3065 submit facts for new facter releases to facterdb Issue Type: Task Assignee: Unassigned Created: 2021/08/19 4:15 AM Priority: Normal Reporter: Tim Meusel Hi, https://github.com/voxpupuli/facterdb is used for unit tests in basically every module. It currently relies on community contributions for new mocked facts on each facter release. Could you consider providing them on a new facter release? That would resolve a lot of issues. facterdb does a fallback to older factsets if the correct version isn't available, so sometimes tests are executed with older fact sets which lead to false/positive errors. Add Comment This message was sent
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title Tim Meusel commented on PUP-8499 Re: puppet lookup cli, using --facts and --node simultaneously breaks Hi people, I just run into this as well on Puppet 6.23.0. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.238867.1519838722000.107810.1629103980036%40Atlassian.JIRA.
Jira (PDB-5229) CentOS 8 package uses legacy path in tmpfiles
Title: Message Title
Tim Meusel updated an issue
PuppetDB / PDB-5229
CentOS 8 package uses legacy path in tmpfiles
Change By:
Tim Meusel
Hi,during some playing with CentOS 8 I noticed the following error (I was installing the postgresql13-server package after puppetdb-7.5.0-1.el8.src.rpm):{code}Error in scriptlet in rpm package postgresql13-server[/usr/lib/tmpfiles.d/puppetdb.conf:1] Line references path below legacy directory /var/run/, updating /var/run/puppetlabs/puppetdb → /run/puppetlabs/puppetdb; please update the tmpfiles.d/ drop-in file accordingly.{code}the tmpfile:{code}# cat /usr/lib/tmpfiles.d/puppetdb.confd /var/run/puppetlabs/puppetdb 0755 puppetdb puppetdb -{code}could you in the next release update this from /var/run to /run? It's a symlink on CentOS 8:{code}# ls -la /var/runlrwxrwxrwx. 1 root root 6 Dec 4 2020 /var/run -> ../run{code} I reported the same bug to puppetserver in https://tickets.puppetlabs.com/browse/SERVER-3059
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PDB-5229) CentOS 8 package uses legacy path in tmpfiles
Title: Message Title Tim Meusel created an issue PuppetDB / PDB-5229 CentOS 8 package uses legacy path in tmpfiles Issue Type: Bug Assignee: Unassigned Created: 2021/08/10 6:16 AM Priority: Normal Reporter: Tim Meusel Hi, during some playing with CentOS 8 I noticed the following error (I was installing the postgresql13-server package after puppetdb-7.5.0-1.el8.src.rpm): Error in scriptlet in rpm package postgresql13-server [/usr/lib/tmpfiles.d/puppetdb.conf:1] Line references path below legacy directory /var/run/, updating /var/run/puppetlabs/puppetdb → /run/puppetlabs/puppetdb; please update the tmpfiles.d/ drop-in file accordingly. the tmpfile: # cat /usr/lib/tmpfiles.d/puppetdb.conf d /var/run/puppetlabs/puppetdb 0755 puppetdb puppetdb -
Jira (PDB-5228) PuppetDB 7 rpm requires Java 11 but doesn't depend on it
Title: Message Title Tim Meusel created an issue PuppetDB / PDB-5228 PuppetDB 7 rpm requires Java 11 but doesn't depend on it Issue Type: Task Assignee: Unassigned Created: 2021/08/10 5:50 AM Priority: Normal Reporter: Tim Meusel Hi, https://puppet.com/docs/puppetdb/latest/index.html says it Java 11 is required. The packages for CentOS 8 don't depend on Java: [root@server ~]# dnf info puppetdb Last metadata expiration check: 0:05:52 ago on Tue 10 Aug 2021 12:35:40 PM UTC. Installed Packages Name : puppetdb Version : 7.5.0 Release : 1.el8 Architecture : noarch
Jira (HI-627) Update CI matrix to verify it works on ruby 2.7/3
Title: Message Title Tim Meusel created an issue Hiera / HI-627 Update CI matrix to verify it works on ruby 2.7/3 Issue Type: Task Assignee: Unassigned Created: 2021/08/05 12:45 PM Priority: Normal Reporter: Tim Meusel Hi! I'm maintaining the Arch Linux packages for all the puppet tooling. This also includes hiera, because that's listed as a dependency for puppet. It looks like the Travis/Appveyor configuration is broken since some time and I don't reall know on which ruby versions hiera works, I guess 2.7 since that's vendored in Puppet 7 AIO. Can you please take a look at https://github.com/puppetlabs/hiera/pull/430 / let me know the supported Ruby versions? Add Comment This message was sent by
Jira (HI-626) hiera gem is missing a gemspec/license
Title: Message Title
Tim Meusel created an issue
Hiera / HI-626
hiera gem is missing a gemspec/license
Issue Type:
Task
Assignee:
Unassigned
Created:
2021/06/15 1:58 AM
Priority:
Normal
Reporter:
Tim Meusel
Hi, the latest hiera gem has no gemspec/license speficied: https://rubygems.org/gems/hiera/versions/3.7.0
~ $ bundle info hiera
* hiera (3.7.0)
Summary: Light weight hierarchical data store
Homepage: https://github.com/puppetlabs/hiera
Path: /home/bastelfreak/modulesync_config/modules/voxpupuli/puppet-corosync/.vendor/ruby/3.0.0/gems/hiera-3.7.0
~ $ bundle licenses 2>&1 | awk '/^hiera:/ {print $0}'
Jira (PUP-11118) Puppet gem has no gemspec/license
Title: Message Title
Tim Meusel created an issue
Puppet / PUP-8
Puppet gem has no gemspec/license
Issue Type:
Task
Assignee:
Unassigned
Created:
2021/06/15 1:56 AM
Priority:
Normal
Reporter:
Tim Meusel
Hi, the puppet is published as a gem: https://rubygems.org/gems/puppet/versions/7.7.0. But it looks like there is no gemspec file and based on that there is no license specified:
~ $ bundle info puppet
* puppet (7.7.0)
Summary: Puppet, an automated configuration management tool
Homepage: https://github.com/puppetlabs/puppet
Path: /home/bastelfreak/modulesync_config/modules/voxpupuli/puppet-corosync/.vendor/ruby/3.0.0/gems/puppet-7.7.0
~ $ bundle licenses 2>&1 | awk '/^puppet:/ {print $0}'
Jira (PUP-10535) Move to Addressable
Title: Message Title Tim Meusel commented on PUP-10535 Re: Move to Addressable hey Josh Cooper, it it possible to get this fixed in one of the next puppet 7 releases? This would really help people that package Puppet on their own against system ruby (which might be Ruby 3.0, like it is on Arch Linux). Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.360343.1590685774000.1378.1617658200121%40Atlassian.JIRA.
Jira (PDB-4622) Backport changes from austb/ruby-puppetdb to voxpupuli/ruby-puppetdb?
Title: Message Title Tim Meusel commented on PDB-4622 Re: Backport changes from austb/ruby-puppetdb to voxpupuli/ruby-puppetdb? ping Austin Blatt 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.340847.1577909036000.153628.1614543840162%40Atlassian.JIRA.
Jira (FACT-1848) cmdline fact does not propperly resolve multiple parameters
Title: Message Title Tim Meusel commented on FACT-1848 Re: cmdline fact does not propperly resolve multiple parameters Hi! I know the issue is quite old, sorry to bother you. I'm interested in a fact that parses /proc/cmdline. May I ask where this fact is coming from? As far as I know it's not a core fact on facter 3 nor 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.247654.1524755038000.151808.1614263940033%40Atlassian.JIRA.
Jira (FACT-2906) Dependency to lsb packages is missing
Title: Message Title
Tim Meusel created an issue
Facter / FACT-2906
Dependency to lsb packages is missing
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/12/20 4:56 AM
Priority:
Normal
Reporter:
Tim Meusel
Hi, I installed puppet-agent-7.1.0-1.el7.x86_64 on CentOS 7. puppet facts show os:
{
"os": {
"architecture": "x86_64",
"family": "RedHat",
"hardware": "x86_64",
"name": "CentOS",
"release": {
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Tim Meusel commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact thanks for the feedback. I fixed it in master for puppet-prometheus. I agree with Josh Cooper that a puppet-lint plugin might be really good here (although I think puppet-lint at the moment only checks actual Puppet DSL) 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.379364.1606744776000.90699.1607015820025%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Tim Meusel commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact awesome, I tested it locally and your patch works for me: ~ # puppet agent -t --environment puppet7 Info: Using configured environment 'puppet7' Info: Retrieving pluginfacts Info: Retrieving plugin Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/alert_manager_running.rb]/content: --- /opt/puppetlabs/puppet/cache/lib/facter/alert_manager_running.rb 2020-11-04 16:45:06.270485994 +0100 +++ /tmp/puppet-file20201202-8312-olysy6 2020-12-02 17:56:41.113642951 +0100 @@ -1,10 +1,9 @@ require 'puppet' -service = Puppet::Type.type(:service).new(:name => 'alert_manager') # rubocop:disable Style/HashSyntax -
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Tim Meusel commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact Hi, I put all the infos into a gist, because the comments in Jira don't allow so many characters: https://gist.github.com/bastelfreak/4fd5f15f232d965480e21db7a5ef428b let me know if you need more information 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.379364.1606744776000.89391.1606907280037%40Atlassian.JIRA.
Jira (PUP-10793) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title Tim Meusel commented on PUP-10793 Re: puppet 7 treats nonexistent fact differently compared to puppet 6? hey Bogdan Irimie, thanks for the fix. I verified that it fixes this 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.379177.1606234679000.87416.1606754220088%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title
Tim Meusel commented on FACT-2880
Re: facter 4 differing output from facter 3 for service_provider fact
Hey, I've some more output as well (both from CentOS 7 nodes that use the official Puppet packages):
~ # puppet --version
7.0.0
~ # facter --version
4.0.46
~ # puppet resource service sshd
service { 'sshd':
ensure => 'running',
provider => 'base',
}
~ #
this works with the normal puppet 6:
~ # puppet --version
6.19.1
Jira (PUP-10793) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title
Tim Meusel commented on PUP-10793
Re: puppet 7 treats nonexistent fact differently compared to puppet 6?
it's working properly on CentOS 7 with Puppet 7 rpms:
root@* ~ # cat test.pp
$var = $facts['THISDOESNOTEXISTHOPEFULLY'] ? {
'' => 'empty string',
undef => 'undef',
default => $facts['foo'],
}
notify { $var:}
root@* ~ #
Notice: Compiled catalog for *s in environment production in 0.03 seconds
Notice: undef
Notice: /Stage[main]/Main/Notify[undef]/message: defined 'message' as 'undef'
Notice: Applied catalog in 0.33 seconds
Jira (PUP-10793) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title Tim Meusel commented on PUP-10793 Re: puppet 7 treats nonexistent fact differently compared to puppet 6? additional information: facter is 4.0.46 on both boxes the ubuntu setup: root@* ~ # facter --version 4.0.46 root@* ~ # which facter /opt/puppetlabs/bin/facter root@* ~ # and the gem install: bastelfreak@bastelfreak-ws /tmp/puppet7 $ bundle exec gem which facter /tmp/puppet7/.vendor/ruby/2.7.0/gems/facter-4.0.46/lib/facter.rb bastelfreak@bastelfreak-ws /tmp/puppet7 $
Jira (PUP-10793) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title
Tim Meusel commented on PUP-10793
Re: puppet 7 treats nonexistent fact differently compared to puppet 6?
I did some testing with the puppet 7 gem on Arch linux and undef facts are treated as undef:
bastelfreak@bastelfreak-ws /tmp/puppet7 $ bundle exec puppet apply test.pp
Warning: Found multiple default providers for package: gem, pip, pip3, pip2; using gem
Notice: Compiled catalog for bastelfreak-ws.fritz.box in environment production in 0.01 seconds
Notice: undef
Notice: /Stage[main]/Main/Notify[undef]/message: defined 'message' as 'undef'
Notice: Applied catalog in 0.08 seconds
bastelfreak@bastelfreak-ws /tmp/puppet7 $ vim test.pp
bastelfreak@bastelfreak-ws /tmp/puppet7 $ bundle exec puppet --version
7.0.0
bastelfreak@bastelfreak-ws /tmp/puppet7 $ cat test.pp
$var = $facts['foo'] ? {
'' => 'empty string',
Jira (PUP-10793) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title
Tim Meusel created an issue
Puppet / PUP-10793
puppet 7 treats nonexistent fact differently compared to puppet 6?
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/11/24 8:17 AM
Priority:
Normal
Reporter:
Tim Meusel
Puppet Version: 7.0.0 Puppet Server Version: 6.14.1 OS Name/Version: Ubuntu 16.04 Hi!
Sorry for the ugly issue title
this might be better as a facter issue, but I'm not sure
I've the following fact:
Facter.add('sach_passalgo') do
confine :osfamily => 'RedHat'
confine { Facter::Core::Execution.which('authconfig') }
setcode do
Jira (PUP-9139) Package provider apt fails when installing from local file
Title: Message Title Tim Meusel commented on PUP-9139 Re: Package provider apt fails when installing from local file hey people, any chance this can be fixed soonish? Ben Ford could you have a look please? 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.275711.1536922461000.76781.1605100980109%40Atlassian.JIRA.
Jira (PUP-10775) Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog`
Title: Message Title
Tim Meusel commented on PUP-10775
Re: Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog`
wopwop, some progress \o/ I created a testenv and checked it for all binary files:
...
root@puppetserver ~ # shopt -s globstar
root@puppetserver ~ # file /etc/puppetlabs/code/environments/msgpack2/modules/*/files/**/* | grep ELF
/etc/puppetlabs/code/environments/msgpack2/modules/mcollective_agent_dockerinfo/files/mcollective/agent/dockerinfo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), not stripped
/etc/puppetlabs/code/environments/msgpack2/modules/mcollective_agent_user/files/mcollective/agent/user: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped
...
root@puppetserver ~ #
There were some more binary blobs. All not listed blobs are distributed like this:
file {'bla':
ensure => file,
source => '///..'
Jira (PUP-10775) Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog`
Title: Message Title
Tim Meusel commented on PUP-10775
Re: Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog`
A short update here. After digging alot through the thousands of nodes, I discovered at least a few CentOS 6 derivates with the exact same behaviour as above:
root ~ # facter -p os
{
architecture => "x86_64",
family => "RedHat",
hardware => "x86_64",
name => "VirtuozzoLinux",
release => {
full => "6.8",
major => "6",
minor => "8"
},
selinux => {
enabled => false
}
Jira (PUP-10775) Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog`
Title: Message Title Tim Meusel commented on PUP-10775 Re: Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog` heyho, please let me know if I should test more things or if you need a specific 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.377304.1604596654000.72975.1604596740079%40Atlassian.JIRA.
Jira (PUP-10775) Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog`
Title: Message Title
Tim Meusel created an issue
Puppet / PUP-10775
Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog`
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/11/05 9:17 AM
Priority:
Normal
Reporter:
Tim Meusel
Hey Josh Cooper, I did further debugging for https://tickets.puppetlabs.com/browse/PUP-10772. while doing so I discovered that I've 5 Ubuntu 16.04 machines, all of them currently show the `Failed to deserialize Puppet::Resource::Catalog` error message that I show later my client:
root~ # facter -p os
pup{
architecture => "amd64",
distro => {
codename => "xenial",
description => "Ubuntu 16.04.7 LTS",
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Tim Meusel commented on PUP-10772 Re: fresh puppet agent installation fails when msgpack is enabled on puppetserver So some testing. First let me explain my current setup: agents send all requests to an haproxy haproxy forwards requests with /puppet-ca to one specific puppetserver all other requests go to another group of puppetservers the puppetserver for CA requests has the msgpack gem installed and was restarted after it was installed. I purged it on all other puppetservers and restarted them. Log from an existing/working puppet agent, where I also purged the msgpack gem: Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing Debug: catalog supports formats: rich_data_json json rich_data_msgpack pson yaml dot Debug: Closing connection for https://*:8140 Debug: Creating new connection for https://*:8140 Debug: Starting connection for https://*:8140 Debug: Using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 Debug: HTTP POST https://*:8140/puppet/v3/catalog/*?environment=production returned 200 OK Debug: Caching connection for https://*:8140 besides that, the run works fine. Now I took the same agent, without msgpack installed, and it was talking directly to the CA server with msgpack installed:
Jira (PUP-10548) Wrong SELinux contexts on files if puppet installs new rpm with SELinux policy
Title: Message Title Tim Meusel commented on PUP-10548 Re: Wrong SELinux contexts on files if puppet installs new rpm with SELinux policy hey people, just wanted to mention that vox pupuli hits this issue in several places as well, for example in our https://github.com/voxpupuli/puppet-hyperglass module 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.363809.1593020161000.41066.1600843380032%40Atlassian.JIRA.
Jira (PDB-4899) Update docs for report_ttl and resource_events_ttl
Title: Message Title Tim Meusel commented on PDB-4899 Re: Update docs for report_ttl and resource_events_ttl Hi! I just saw this on the mailing list. Did I understand it correctly that partitioning for the reports was introduced recently? I scrolled through the changelog and couldn't spot a hint. In which version was it introduced and if I have a huge amount of reports, might an upgrade cause a long downtime due to table migrations? (not sure if existing data will be split into partitions as well). Maybe infos to those questions can be added to the docs as well cheers, Tim 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.372484.1600444705000.38637.1600446000179%40Atlassian.JIRA.
Jira (PUP-10658) Puppet service ps parsing using too loose regex
Title: Message Title Tim Meusel commented on PUP-10658 Re: Puppet service ps parsing using too loose regex I agree that this might break existing setups that worked by accident. I was hoping this will be fixed for Puppet 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.371182.1599213891000.37092.1600257420024%40Atlassian.JIRA.
Jira (PUP-10658) Puppet service ps parsing using too loose regex
Title: Message Title Tim Meusel created an issue Puppet / PUP-10658 Puppet service ps parsing using too loose regex Issue Type: Bug Assignee: Unassigned Created: 2020/09/04 3:04 AM Priority: Normal Reporter: Tim Meusel Puppet Version: 6.18.0 Puppet Server Version: 6.12.0 OS Name/Version: CentOS 6 Hello, I've got two services running, bird and bird6. their processes are also named bird and bird6. If I manage the service via puppet and set hasstatus to false, puppet will parse ps -ef: https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/service/base.rb#L37 If I want to manage the bird service and it's currently not running, but bird6 is running, but will assume that the bird6 process relates to the bird service: from the debug output: Debug: Service[bird](provider=redhat): Executing 'ps -ef' Debug: Executing: 'ps -ef' Debug: Service[bird](provider=redhat): Process matched: bird6 10046 1 0 Aug28 ?00:16:23 /usr/sbin/bird6 -u bird6 -g bird6 Desired Behavior: I would like to see that the regex won't match, puppet detects the service as off and starts it Actual Behavior: puppet assumes that the bird service is running and won't start it testcode
Jira (PUP-10611) puppet daemon fails with undefined method `uri_unescape' for Puppet::Util:Module, CLI works
Title: Message Title Tim Meusel commented on PUP-10611 Re: puppet daemon fails with undefined method `uri_unescape' for Puppet::Util:Module, CLI works I'm now unable to reproduce this. I guess that the puppet agent wasn't properly restarted after the last upgrades. I will close the issue and reopen it if it happens again. 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.368596.1596784031000.17172.1597689480040%40Atlassian.JIRA.
Jira (PUP-10611) puppet daemon fails with undefined method `uri_unescape' for Puppet::Util:Module, CLI works
Title: Message Title Tim Meusel commented on PUP-10611 Re: puppet daemon fails with undefined method `uri_unescape' for Puppet::Util:Module, CLI works sorry, missed your comment I added the trace option to the init script and restarted the service on 4 boxes. I will check foreman later if it recieved proper reports. 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.368596.1596784031000.13591.1597147440023%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Tim Meusel commented on PUP-10351 Re: Puppet Agent fails to self-restart on config change or update Hi. Can someone confirm this is actually fixed in 6.16.0? I wasn't able to find an entry in the release notes and my agents still fail: root@server01 ~ # puppet --version 6.16.0 root@server01 ~ # systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled) Active: active (running) (thawing) since Thu 2020-02-20 13:50:56 CET; 5 months 20 days ago Main PID: 20855 (puppet) IP: 94.9M in, 75.0M out Tasks: 5 (limit: 145001) Memory: 112.7M CPU: 4h 17min 29.438s CGroup: /system.slice/puppet.service ├─20855
Jira (PUP-10611) puppet daemon fails with undefined method `uri_unescape' for Puppet::Util:Module, CLI works
Title: Message Title Tim Meusel created an issue Puppet / PUP-10611 puppet daemon fails with undefined method `uri_unescape' for Puppet::Util:Module, CLI works Issue Type: Bug Assignee: Unassigned Created: 2020/08/07 12:07 AM Priority: Normal Reporter: Tim Meusel Puppet Version: 6.17.0 Puppet Server Version: 6.12.1 OS Name/Version: FreeBSD 12.1 I can run `puppet agent -t` without issues in the shell. However the daemon fails to run in the background. Foreman has the following error logs: err /File[/var/puppet/facts.d] Failed to generate additional resources using 'eval_generate': undefined method `uri_unescape' for Puppet::Util:Module err /File[/var/puppet/facts.d] Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: undefined method `uri_unescape' for Puppet::Util:Module err /File[/var/puppet/lib] Failed to generate additional resources using 'eval_generate': undefined method `uri_unescape' for Puppet::Util:Module err /File[/var/puppet/lib] Could not evaluate: Could not retrieve file metadata for puppet:///plugins: undefined method `uri_unescape' for Puppet::Util:Module
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Tim Meusel commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Hey Josh Cooper, we sadly run into this bug as well. It's still present in Puppet 6.17.0. 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.302978.1554294806000.936.1595594520092%40Atlassian.JIRA.
Jira (PDB-4627) Docs are unclear about supported postgres/java versions
Title: Message Title Tim Meusel commented on PDB-4627 Re: Docs are unclear about supported postgres/java versions Hi PuppetDB people. today I read https://puppet.com/docs/puppetdb/latest/release_notes.html#puppetdb-6110 saying: > Running PuppetDB with PostgreSQL 9.6 and 10 has been deprecated. Use PostgreSQL 11 instead. whereas https://puppet.com/docs/puppetdb/latest/index.html#postgresql-96 says: > PuppetDB requires PostgreSQL 9.6 or later. After half a year, can you please tell me which versions are tested/supported and which is recommended? 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.342654.1579514884000.79775.1591359540050%40Atlassian.JIRA.
Jira (FACT-2536) facter 4.x fails on Archlinux
Title: Message Title Tim Meusel commented on FACT-2536 Re: facter 4.x fails on Archlinux Hi Andrei Filipovici, https://github.com/puppetlabs/facter-ng/pull/470 was merged some time ago. Do you already know when arch support will work again? 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.354178.1585993672000.56567.1588839120084%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title
Tim Meusel commented on PUP-10351
Re: Puppet Agent fails to self-restart on config change or update
I've multiple centos boxes, but most of them have nothing in their journal except the restart message.
root ~ # facter -p os
{
architecture => "x86_64",
family => "RedHat",
hardware => "x86_64",
name => "CentOS",
release => {
full => "7.7.1908",
major => "7",
minor => "7"
},
selinux => {
config_mode => "enforcing",
config_policy => "targeted",
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Tim Meusel commented on PUP-10351 Re: Puppet Agent fails to self-restart on config change or update I thought to try something new and noticed that I could just start the agent on the cmdline, if the daemon logs `Shutdown/restart in progress (:restart_requested); skipping run`. At least on this box it wasn't required to kill the agent. 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.348520.1583329295000.41585.158736927%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Tim Meusel commented on PUP-10351 Re: Puppet Agent fails to self-restart on config change or update Hello people, I see this error on multiple nodes in my environment, at the moment all of them are running puppet 6.12.0 and 6.14.0: Apr 09 12:03:19 puppet-agent[27550]: Starting Puppet client version 6.12.0 Apr 09 12:03:19 puppet-agent[27550]: Could not run: Could not create PID file: /var/run/puppetlabs/agent.pid Apr 09 12:03:19 systemd[1]: puppet.service: main process exited, code=exited, status=1/FAILURE Apr 09 12:03:19 systemd[1]: Unit puppet.service entered failed state. Apr 09 12:03:19 systemd[1]: puppet.service failed. Apr 09 12:03:23 puppet-agent[21586]: Config file /etc/puppetlabs/puppet/puppet.conf changed; triggering re-parse of all config files. Apr 09 13:59:35 puppet-agent[21586]: Shutdown/restart in progress (:restart_requested); skipping run Apr 09 15:59:35 puppet-agent[21586]: Shutdown/restart in progress (:restart_requested); skipping run Apr 09 17:59:35 puppet-agent[21586]: Shutdown/restart in progress (:restart_requested); skipping run Apr 09 19:59:35 puppet-agent[21586]: Shutdown/restart in progress (:restart_requested); skipping run Apr 09
Jira (PDOC-300) Add support for additional tags like author/license
Title: Message Title Tim Meusel created an issue Puppet Strings / PDOC-300 Add support for additional tags like author/license Issue Type: Improvement Assignee: Unassigned Created: 2020/03/11 2:09 AM Priority: Normal Reporter: Tim Meusel Hi, I think it makes sense to enhance puppet-strings with at lease those two tags: license author In big modules it's possible that certain files come from external contributors with a different license than the one listed in the metadata.json. To properly give credit to authors it also makes sense to list them in a file if they contributed the whole file. Add Comment
Jira (FACT-2354) Provide fact fixtures on new facter releases to facterdb
Title: Message Title Tim Meusel commented on FACT-2354 Re: Provide fact fixtures on new facter releases to facterdb The team that maintains the Puppet modules might be interested in this as well, since most of their modules also use rspec-puppet-facts. 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.345749.158135502.21735.1581443460235%40Atlassian.JIRA.
Jira (FACT-2354) Provide fact fixtures on new facter releases to facterdb
Title: Message Title Tim Meusel created an issue Facter / FACT-2354 Provide fact fixtures on new facter releases to facterdb Issue Type: Task Assignee: Unassigned Created: 2020/02/10 9:17 AM Priority: Normal Reporter: Tim Meusel Hi, to my understanding it's common practice to use rspec-puppet-facts for spec tests. The tool iterates on every operating system in the metadata.json and uses matching fact sets from facterdb. We try to use the correct facter version for the puppet version we're testing on: # getting the correct facter version is tricky. We use facterdb as a source to mock facts # see https://github.com/camptocamp/facterdb # people might provide a specific facter version. In that case we use it. # Otherwise we need to match the correct facter version to the used puppet version. # as of 2019-10-31, puppet 5 ships facter 3.11 and puppet 6 ships facter 3.14
Jira (PUP-10240) Puppet gem has no/missing development/test gems
Title: Message Title Tim Meusel commented on PUP-10240 Re: Puppet gem has no/missing development/test gems Hi Jorie Tappa! I'm building the official Arch Linux packages for Puppet tools. That includes r10k, pdk and Puppet. The abstract workflow for Arch packages looks like this: Setup a minimal Arch container Download the release. e.g. a git tag or a tar ball from http://downloads.puppet.com/ Install all dependencies required to run tests + to built it via native Arch packages Run the tests "build" the software specific for Puppet: At the moment we download the release from https://downloads.puppetlabs.com/, verify the signature and try to install required dependencies. Since puppet is published as a gem, I went the usual way for gems -> checking required depdencies on rubygems.org / in the gemspec file. Most projects I work with define runtime + test dependencies in the gemspec. Stuff that's nice for development is defined in a Gemfile. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-4627) Docs are unclear about supported postgres/java versions
Title: Message Title Tim Meusel created an issue PuppetDB / PDB-4627 Docs are unclear about supported postgres/java versions Issue Type: Task Assignee: Unassigned Created: 2020/01/20 2:08 AM Priority: Normal Reporter: Tim Meusel Hi people, I had a look at https://puppet.com/docs/puppetdb/latest/index.html. I need to setup a puppetdb with latest java / postgres. In the previous years I learned that puppetdb almost never works on the latest postgres version. The docs say however: > PuppetDB requires PostgreSQL 9.6 or later And: > ... PuppetDB can run on any Unix-like OS with JVM 8 or newer Does PuppetDB actually work with Java 11/12/13? Which versions are tested/supported? Does PuppetDB work with Postgres 11/12? Which versions are tested/supported? Add Comment
Jira (PUP-10240) Puppet gem has no/missing development/test gems
Title: Message Title Tim Meusel created an issue Puppet / PUP-10240 Puppet gem has no/missing development/test gems Issue Type: Bug Assignee: Unassigned Created: 2020/01/19 10:35 AM Priority: Normal Reporter: Tim Meusel Hi, I took a look at the puppet gem dependencies for the latest release: https://rubygems.org/gems/puppet/versions/6.12.0 It lists a few runtime dependencies, but no additional dependencies for development/test. Could you add gems required to execute the test suite as well? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4622) Backport changes from austb/ruby-puppetdb to voxpupuli/ruby-puppetdb?
Title: Message Title Tim Meusel created an issue PuppetDB / PDB-4622 Backport changes from austb/ruby-puppetdb to voxpupuli/ruby-puppetdb? Issue Type: Task Assignee: Unassigned Created: 2020/01/01 12:03 PM Priority: Normal Reporter: Tim Meusel Hi people, https://github.com/voxpupuli/puppetdb-ruby is the home of the puppetdb gem. We (Vox Pupuli) noticed that a lot of stuff happened at https://github.com/austb/puppetdb-ruby. Is it planned to backport those changes to Vox Pupuli? CC: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1967) Unable to compile libwhereami 0.2.2 on latest Archlinux
Title: Message Title
Tim Meusel commented on FACT-1967
Re: Unable to compile libwhereami 0.2.2 on latest Archlinux
I actually discovered something which needs clarification. The lib is built static. This is a bit problematic because it's hard to determine which runtime dependencies exist and a security update for a dependency forces us to recompile libwhereami. On Archlinux, we modified the built config to link it dynamically:
sed 's|add_library(lib${PROJECT_NAME}|add_library(lib${PROJECT_NAME} SHARED|' -i lib/CMakeLists.txt
Is libwhereami static on purpose? Otherwise I could provide a PR to link it dynamically.
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.318292.1564323614000.49774.1565361540160%40Atlassian.JIRA.
Jira (FACT-1968) Unable to compile facter 3.14.2 on latest Archlinux
Title: Message Title
Tim Meusel commented on FACT-1968
Re: Unable to compile facter 3.14.2 on latest Archlinux
I'm now able to build facter properly with the following commands:
sed -i 's/-source 1.6 -target 1.6/-source 1.8 -target 1.8/' CMakeLists.txt
sed -i 's/rb_data_object_alloc/rb_data_object_wrap/g' lib/src/ruby/*.cc
mkdir release
cd release
JAVA_HOME=/usr/lib/jvm/default cmake -DCMAKE_INSTALL_PREFIX=/usr -DENABLE_CXX_WERROR=OFF ..
make
make test
make install DESTDIR="${pkgdir}"
I unpinned the gems to the testsuite works properly with ruby 2.6: https://github.com/puppetlabs/facter/pull/1818 Also facter has an optional dependency to udev, but there is no cmake file to search for a udev lib. I added this in: https://github.com/puppetlabs/facter/pull/1820
Add Comment
Jira (FACT-1968) Unable to compile facter 3.14.2 on latest Archlinux
Title: Message Title Tim Meusel commented on FACT-1968 Re: Unable to compile facter 3.14.2 on latest Archlinux Tests are failing because the rake version is too new on Arch (version 12). The Gemfile expects Version 10. I'm currently working on a fix. 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.318296.1564333964000.47904.1565269320184%40Atlassian.JIRA.
Jira (FACT-1967) Unable to compile libwhereami 0.2.2 on latest Archlinux
Title: Message Title Tim Meusel commented on FACT-1967 Re: Unable to compile libwhereami 0.2.2 on latest Archlinux Hi. Thanks for the hint. I'm now using those commands (base directory is the extracted release from github.com): mkdir build-release cd build-release cmake .. -DENABLE_CXX_WERROR=OFF -DCMAKE_INSTALL_PREFIX:PATH=/usr make libwhereami_test make make install This looks good in a clean container environment. This is used as a base to create a package for Archlinux Add Comment This message was sent by
Jira (FACT-1967) Unable to compile libwhereami 0.2.2 on latest Archlinux
Title: Message Title Tim Meusel created an issue Facter / FACT-1967 Unable to compile libwhereami 0.2.2 on latest Archlinux Issue Type: Bug Assignee: Unassigned Created: 2019/07/28 7:20 AM Priority: Normal Reporter: Tim Meusel Hi, I tried to compile the 0.2.2 release and experienced some issues. My output from cmake .. -- The C compiler identification is GNU 9.1.0 -- The CXX compiler identification is GNU 9.1.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works
Jira (FACT-1966) Facter depends on unstable libwhereami release
Title: Message Title Tim Meusel created an issue Facter / FACT-1966 Facter depends on unstable libwhereami release Issue Type: Task Assignee: Unassigned Created: 2019/07/28 7:14 AM Priority: Normal Reporter: Tim Meusel Hi people, First of, this is more a libwhereami (https://github.com/puppetlabs/libwhereami) issue than facter. Please move the issue if this is the wrong project. I'm trying to create an Archlinux package for Facter 3.14.2. It depends on libwhereami. The last known release I could find is 0.2.2. I assume that you use semantic versioning because you do that in other projects as well. Is this true for libwhereami as well? If so, depending on a project with an unstable API feels a bit wrong. Could you do a 1.0.0 release (if the API is already stable..). Also I wasn't able to find gpg signed releases at http://downloads.puppet.com and also the older git tags aren't signed. Add Comment
Jira (FACT-1907) facter 3.12.2 choses wrong ip as main ip
Title: Message Title Tim Meusel commented on FACT-1907 Re: facter 3.12.2 choses wrong ip as main ip As a workaround, I would be totally fine by reconfigering the network so facter the detects the correct ip address again, but I've no idea how facter would like to have it. Are you able to figure out how facter detects it by reading the code? I failed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1907) facter 3.12.2 choses wrong ip as main ip
Title: Message Title Tim Meusel created an issue Facter / FACT-1907 facter 3.12.2 choses wrong ip as main ip Issue Type: Bug Assignee: Unassigned Created: 2019/01/23 1:43 PM Priority: Normal Reporter: Tim Meusel Hi people, I did some debugging with Eric Sorenson on slack about this. I have a server with multiple ip addresses on a single interface. One address is considered the main address. This one is persistant and always present. the others are floating ips.they might be added/removed during runtime. The setup at the moment: # facter -p networking.interfaces.enp5s0.ip 10.254.4.100 # facter -p networking.ip 10.254.4.100 # facter --version 3.12.2
Jira (PUP-9268) 5.5.7 breaks custom function
Title: Message Title Tim Meusel commented on PUP-9268 Re: 5.5.7 breaks custom function I agree with Alexander Fisher here. To me this looks like a breaking change for something that wasn't optimal and not recommended, but definitely not prohibited. If semantic versioning should be honored, this should only fail in puppet 7, not 5 and not 6. 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 (PDB-3857) Fix fact path GC incompatibility with Postgres 10
Title: Message Title Tim Meusel commented on PDB-3857 Re: Fix fact path GC incompatibility with Postgres 10 Hey people. Is there an ETA for 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1886) Facter3 should also check for 'Virtuozzo Linux'
Title: Message Title Tim Meusel commented on FACT-1886 Re: Facter3 should also check for 'Virtuozzo Linux' A patch is already available at https://github.com/puppetlabs/facter/pull/1749 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-6114) Add support for Artifactory checksum headers and enable SHA1 checksum type
Title: Message Title Tim Meusel commented on PUP-6114 Re: Add support for Artifactory checksum headers and enable SHA1 checksum type Hey puppet people. I'm highly interested into this issue. Any chance you can rereview the PR and work on it? Thanks in advance! 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-7474) PuppetCA should issue certs with Subject Alternative Name containing the CN for compliance with RFC 2818
Title: Message Title Tim Meusel commented on PUP-7474 Re: PuppetCA should issue certs with Subject Alternative Name containing the CN for compliance with RFC 2818 Just for the reference: One related PR with a possible solution is at https://github.com/puppetlabs/puppet/pull/6438 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.
