Jira (FACT-3202) Incorrect is_virtual and virtual facts on crio container runtime
Title: Message Title Jesse Hathaway commented on FACT-3202 Re: Incorrect is_virtual and virtual facts on crio container runtime Any chance I could get a review? Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.485493.1683835348000.416.1686844860025%40Atlassian.JIRA.
Jira (FACT-3202) Incorrect is_virtual and virtual facts on crio container runtime
Title: Message Title Jesse Hathaway created an issue Facter / FACT-3202 Incorrect is_virtual and virtual facts on crio container runtime Issue Type: Bug Assignee: Unassigned Created: 2023/05/11 1:02 PM Priority: Normal Reporter: Jesse Hathaway When using the crio container runtime facter reports the following incorrect information: $ facter is_virtual false $ facter virtual physical
Jira (FACT-3202) Incorrect is_virtual and virtual facts on crio container runtime
Title: Message Title Jesse Hathaway updated an issue Facter / FACT-3202 Incorrect is_virtual and virtual facts on crio container runtime Change By: Jesse Hathaway Affects Version/s: FACT 4.3.1 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.485493.1683835348000.12649.1683835380100%40Atlassian.JIRA.
Jira (PUP-3761) puppet agent --onetime not honored
Title: Message Title Jesse Hathaway commented on PUP-3761 Re: puppet agent --onetime not honored Josh Cooper any chance we could re-open this issue? 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.61271.141833753.259.1679675700148%40Atlassian.JIRA.
Jira (PUP-3761) puppet agent --onetime not honored
Title: Message Title Jesse Hathaway commented on PUP-3761 Re: puppet agent --onetime not honored It would be really nice if running in the foreground skipped the lock or if a flag was added to skip the lock. Otherwise there is a race condition as Dan Bode mentioned between enabling puppet and kicking off a run in the foreground. 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.61271.141833753.7.1679602320062%40Atlassian.JIRA.
Jira (PUP-10782) Could not parse for environment ...: Syntax error at '=>' ...
Title: Message Title
Jesse Hathaway commented on PUP-10782
Re: Could not parse for environment ...: Syntax error at '=>' ...
Just ran into this today, is it documented anywhere, I couldn't find it on the hashes doc, https://puppet.com/docs/puppet/7/lang_data_hash.html fails without semicolon:
$c = 'bubbles'
{'butter' => $c}.each |$a, $b| { notice($a,$b) }
succeeds with semicolon:
$c = 'bubbles'
;{'butter' => $c}.each |$a, $b| { notice($a,$b) }
It would be nice to understand when a semicolon is needed before an anonymous hash
Add Comment
This message was sent by Atlassi
Jira (PUP-3922) Preserve modulepath structure during pluginsync
Title: Message Title Jesse Hathaway commented on PUP-3922 Re: Preserve modulepath structure during pluginsync Has this situation been improved since Puppet 5.5, the version we are currently running? 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.65973.1422487314000.4492.1647534420565%40Atlassian.JIRA.
Jira (PUP-9001) show_diff does not show content changes for new files
Title: Message Title Jesse Hathaway commented on PUP-9001 Re: show_diff does not show content changes for new files Pull request to add diffing on new files, https://github.com/puppetlabs/puppet/pull/8890 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.107312.1448882974000.32267.164600082%40Atlassian.JIRA.
Jira (PUP-11472) Legacy function error does not include the source ref
Title: Message Title Jesse Hathaway created an issue Puppet / PUP-11472 Legacy function error does not include the source ref Issue Type: Bug Assignee: Unassigned Created: 2022/02/28 3:17 PM Priority: Normal Reporter: Jesse Hathaway Puppet Version: main Desired Behavior: Legacy function errors would include the source path Actual Behavior: No source path is included, e.g. ruby_legacy_function_instantiator.rb:97:in `walk': Illegal method definition of method 'initialize' on line 8 in legacy function. See https://puppet.com/docs/puppet/latest/functions_refactor_legacy.html for more information (SecurityError) Add Comment
Jira (PUP-11472) Legacy function error does not include the source ref
Title: Message Title Jesse Hathaway commented on PUP-11472 Re: Legacy function error does not include the source ref Pull request: https://github.com/puppetlabs/puppet/pull/ 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.437580.1646090265000.25220.1646090400097%40Atlassian.JIRA.
Jira (PUP-1153) Incorrect ordering of group and user resource purging
Title: Message Title Jesse Hathaway commented on PUP-1153 Re: Incorrect ordering of group and user resource purging Josh Cooper You are correct that forcing group deletion is not necessary if I use the resources resource. That methodology should be sufficient for my use case, so I will go ahead and close my pull request. I maintain that this is a relatively innocuous change which improves usability and eliminates a difference between Linux and platforms such as FreeBSD, but evidently you disagree on the importance of those factors. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21655.1387320781000.38699.1559935681135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1153) Incorrect ordering of group and user resource purging
Title: Message Title
Jesse Hathaway commented on PUP-1153
Re: Incorrect ordering of group and user resource purging
Josh Cooper We manage all our users, including system users, with puppet so your suggestion would not help our use case. We have been running a version of my PR for three years with no ill effects. I am not sure what the concerns are with "dangling pointers" the affected user can still login and even access any files, they just can't resolve their GID into a name. You are correct that through proper ordering you can delete the user before the group, but there are a couple of issues with that approach:
This behavior is inconsistent between platforms, for example FreeBSD or DragonflyBSD will happily delete a group when there still exists a user who has that group set as their GID. This inconsistency makes it harder to use cross platform modules on the forge.
You have to change your puppet ordering anytime you delete a user, since on creation you want the group created before the user and upon deletion you want the user deleted before the group:
# Creation
group { 'butter':
ensure => present,
gid => 555,
}
user { 'butter':
ensure => present,
uid => 555,
Jira (PUP-2644) Code Formatter
Title: Message Title Jesse Hathaway commented on PUP-2644 Re: Code Formatter Would it be possible to reopen this feature request? Tools like `gofmt` have quickly become an industry standard and the lack of such a tool as part of puppet makes it very difficult to bring consistent style to a large code base. Would it be possible to extend `puppet validate` with a new command, perhaps `puppet format`, which would output a puppet file adhering to the style guide? 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.
