Jira (PUP-11380) Backport user/sshkey fixes to 6.x
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11380 Backport user/sshkey fixes to 6.x Change By: Josh Cooper Sprint: Coremunity Kanban 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.427222.1639501173000.5770.1639527840033%40Atlassian.JIRA.
Jira (PUP-11380) Backport user/sshkey fixes to 6.x
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11380 Backport user/sshkey fixes to 6.x Change By: Josh Cooper Team: Phoenix 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.427222.1639501173000.5769.1639527780031%40Atlassian.JIRA.
Jira (PUP-355) how to run rspec-puppet with lookup a.k.a data in environment/modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-355 how to run rspec-puppet with lookup a.k.a data in environment/modules Change By: Josh Cooper Sprint: PDE 2017-04-05, PDE 2017-04-19 , Language Triage 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.14888.1379534768000.5768.1639527660038%40Atlassian.JIRA.
Jira (PUP-11380) Backport user/sshkey fixes to 6.x
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11380 Backport user/sshkey fixes to 6.x Change By: Josh Cooper Sprint: Coremunity Kanban 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.427222.1639501173000.5752.1639525740033%40Atlassian.JIRA.
Jira (PUP-11380) Backport user/sshkey fixes to 6.x
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11380 Backport user/sshkey fixes to 6.x Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Puppet no longer fails when using "purge_ssh_keys" if the user's home directory doesn't exist yet. 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.427222.1639501173000.5744.1639524480041%40Atlassian.JIRA.
Jira (PUP-11380) Backport user/sshkey fixes to 6.x
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11380 Backport user/sshkey fixes to 6.x Change By: Josh Cooper Fix Version/s: PUP 6.26.0 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.427222.1639501173000.5742.1639524300032%40Atlassian.JIRA.
Jira (PUP-11380) Backport user/sshkey fixes to 6.x
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-11380 Backport user/sshkey fixes to 6.x Change By: Josh Cooper Assignee: Josh Cooper 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.427222.1639501173000.5741.1639524240075%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-5376) Update winston (Puppet Platform 7.13.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5376 Update winston (Puppet Platform 7.13.0) Change By: Rob Browning Fix Version/s: PDB 7.8.0 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.423548.1637014539000.5534.1639508460096%40Atlassian.JIRA.
Jira (PDB-5376) Update winston (Puppet Platform 7.13.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5376 Update winston (Puppet Platform 7.13.0) Change By: Rob Browning Release Notes: Not Needed 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.423548.1637014539000.5533.1639508400147%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Josh Cooper commented on PUP-11328 Re: Puppet agent may download all plugins after updating brandfbb thanks for bringing this to our attention. I filed PUP-11379 for the regression. Please watch/comment on that ticket instead of this one. 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.421154.1635201319000.5458.1639504980145%40Atlassian.JIRA.
Jira (PUP-11380) Backport user/sshkey fixes to 6.x
Title: Message Title Josh Cooper created an issue Puppet / PUP-11380 Backport user/sshkey fixes to 6.x Issue Type: Task Assignee: Unassigned Created: 2021/12/14 8:59 AM Priority: Normal Reporter: Josh Cooper We need to backport merge commit b011076f3789861b47ac79650d007508143562eb to 6.x After this change, the sshkeys_core module tests should pass Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Ewoud Kohl van Wijngaarden commented on FACT-3065 Re: submit facts for new facter releases to facterdb If we're going to upload facts per patch set (and I think there's value in that) it certainly makes sense. The code should already work with that since it's just a Dir.glob(File.join(facts_dir, "*", '.facts')) so you could even make it facts/4.2/4.2.6/myos.facts. I'm not saying we have to, but the code supports it. If we consistently have that, we can even optimize some things. We now query all facts even if we know a specific facter version is requested. We could do fact filtering prior to loading files. +1 from me on including the patch version, even bigger +1 if we modify the existing facterdb to include the patch level in the directory name. 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.5160.1639500420027%40Atlassian.JIRA.
Jira (PUP-11379) Regression: agent no longer calls local enc script
Title: Message Title Breno Fernandes created an issue Puppet / PUP-11379 Regression: agent no longer calls local enc script Issue Type: Bug Assignee: Unassigned Created: 2021/12/14 8:42 AM Priority: Normal Reporter: Breno Fernandes As a result of changes made in the environment convergence epic, the agent no longer calls the Puppet::Node terminus to resolve the environment during the run (before doing pluginsync and the catalog request). If the agent is configured to use a *local* enc, then it will no longer be called. See gabriel.nagy comment in https://tickets.puppetlabs.com/browse/PUP-11328?focusedCommentId=839470=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-839470 for more information. We should re-add this capability with the following notes: 1. The terminus should only be called when the following is true: unless (cached_catalog || options[:catalog] || Puppet[:strict_environment_mode]) 2. The terminus should only be called if it's overridden from the default. 3. If the terminus should be called with the same parameters as last time, e.g. transaction_uuid. 4. If the terminus returns a node, then the agent should use its environment as the "last known environment" ignoring what is stored in the last run summary. 5. If the terminus returns a node whose environment is nil, then I'm not sure. We should check what happened previously.
Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-3065 submit facts for new facter releases to facterdb Change By: Gabriel Nagy Assignee: Gabriel Nagy 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.5121.1639498080060%40Atlassian.JIRA.
Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Gabriel Nagy commented on FACT-3065 Re: submit facts for new facter releases to facterdb ekohl bastelfreak I updated our fact generation script to more closely resemble the layout in facterdb: https://github.com/puppetlabs/puppet-agent/pull/2176 One question I have is if you think there would be value in also including the Facter patch version in the output directory name (i.e. 4.2.6 instead of 4.2 - for us this would be trivial). 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.5110.1639496640033%40Atlassian.JIRA.
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title productboard updated an issue Puppet / PUP-11023 Make trlinkin-noop a fully supported feature Change By: productboard productboard URL: https://puppet.productboard.com/feature-board/planning/features/11142283 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.394534.1617818266000.5088.1639492200055%40Atlassian.JIRA.
Jira (PUP-11378) User resource difference in functionality between rhel 7 and 8
Title: Message Title Ciprian Badescu commented on PUP-11378 Re: User resource difference in functionality between rhel 7 and 8 Can you use https://puppet.com/docs/puppet/6/types/user.html#user-attribute-forcelocal parameter to force puppet to use the local user 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.427060.1639420066000.4959.1639472640030%40Atlassian.JIRA.
Jira (FACT-3100) Facter 4.2.6 disks fact could not get serial bacause of using absolute path for lsblk
Title: Message Title
Valentyna updated an issue
Facter / FACT-3100
Facter 4.2.6 disks fact could not get serial bacause of using absolute path for lsblk
Change By:
Valentyna
Fact disks does not show serial of disks because of using absolute path for lsblk, on my updated ubuntu 20.04 from 18.04. On my updated OS lsblk is available in path /bin/lsblk, on my another PC with installed ubuntu 20.04 from scratch lsblk is on /usr/bin/lsblk.I think should use instead of full path result = Facter::Core::Execution.execute("/usr/bin/lsblk -dn -o serial /dev/# \ {disk}", \ {on_fail: "", time_limit: 1}).strip,use result = Facter::Core::Execution.execute("lsblk -dn -o serial /dev/# \ {disk}", \ {on_fail: "", time_limit: 1}).strip Which solves the problem.
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
Jira (FACT-3100) Facter 4.2.6 disks fact could not get serial bacause of using absolute path for lsblk
Title: Message Title
Valentyna created an issue
Facter / FACT-3100
Facter 4.2.6 disks fact could not get serial bacause of using absolute path for lsblk
Issue Type:
Bug
Affects Versions:
FACT 4.2.6
Assignee:
Unassigned
Components:
Facter 4
Created:
2021/12/14 1:00 AM
Labels:
github platform_7
Priority:
Medium
Reporter:
Valentyna
Fact disks does not show serial of disks because of using absolute path for lsblk, on my updated ubuntu 20.04 from 18.04. On my updated OS lsblk is available in path /bin/lsblk, on my another PC with installed ubuntu 20.04 from scratch lsblk is on /usr/bin/lsblk. I think should use instead of full path result = Facter::Core::Execution.execute("/usr/bin/lsblk -dn -o serial /dev/# {disk}", {on_fail: "", time_limit: 1}).strip, use result = Facter::Core::Execution.execute("lsblk -dn -o serial /dev/#{disk} ", {on_fail: "", time_limit: 1} ).strip Which solves the problem.
