Jira (PUP-11322) Excessive copying of already merged code for the main hostclass
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11322 Excessive copying of already merged code for the main hostclass Change By: Josh Cooper Sprint: Coremunity Kanban 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.419718.1634318948000.157895.1634605500031%40Atlassian.JIRA.
Jira (PUP-11322) Excessive copying of already merged code for the main hostclass
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-11322 Excessive copying of already merged code for the main hostclass Change By: Josh Cooper Assignee: Josh Cooper 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.419718.1634318948000.157894.1634605440037%40Atlassian.JIRA.
Jira (PUP-11318) puppet code merger should use concat not plus
Title: Message Title Josh Cooper commented on PUP-11318 Re: puppet code merger should use concat not plus Merged to 6.x in https://github.com/puppetlabs/puppet/commit/bc8f433a41a00b34cf4fbadc1354fa53db2a525c 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.419320.1634052941000.157813.1634596324916%40Atlassian.JIRA.
Jira (PDB-5334) Fix facts-test/fact-environment-queries
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-5334
Fix facts-test/fact-environment-queries
Change By:
Rob Browning
Just fix it if it's easy, otherwise create a suitable, bigger ticket. The tests aren't running because they're guarded by the ` {{ :when (not #(re-find ...)) ` }} -- note the presumably unintentionally anonymous function. Fixing that produces schema failures in ` {{ add-facts! ` }} calls, guessing because they haven't been kept up to date over many years.
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.420025.1634593536000.157770.1634593920083%40Atlassian.JIRA.
Jira (PDB-5334) Fix facts-test/fact-environment-queries
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5334 Fix facts-test/fact-environment-queries Change By: Rob Browning Just fix it if it's easy, otherwise create a suitable, bigger ticket. The tests aren't running because they're guarded by the `:when (not #(re-find ...))` -- note the presumably unintentionally anonymous function. Fixing that produces schema failures in `add-facts!` calls, guessing because they haven't been kept up to date over many years. 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.420025.1634593536000.157767.1634593800827%40Atlassian.JIRA.
Jira (PDB-5334) Fix facts-test/fact-environment-queries
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5334 Fix facts-test/fact-environment-queries Change By: Rob Browning Sprint: HAHA/Grooming 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.420025.1634593536000.157765.1634593620093%40Atlassian.JIRA.
Jira (PDB-5334) Fix facts-test/fact-environment-queries
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5334 Fix facts-test/fact-environment-queries Change By: Rob Browning Issue Type: Improvement Bug 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.420025.1634593536000.157764.1634593620047%40Atlassian.JIRA.
Jira (PDB-5334) Fix facts-test/fact-environment-queries
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5334 Fix facts-test/fact-environment-queries Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 2:45 PM Priority: Normal Reporter: Rob Browning Just fix it if it's easy, otherwise create a suitable, bigger ticket. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3077) Inconsistent values coming from facter-ng output
Title: Message Title Jeremy Mozes commented on FACT-3077 Re: Inconsistent values coming from facter-ng output Selvakumar Azhagarsami Thanks, do we think this will be resolved in 2021.4 or is there a plan of action to resolve the bug? 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.418363.1633415924000.157371.1634574242963%40Atlassian.JIRA.
Jira (PUP-11317) Puppet Primary Server support platforms seems outdated.
Title: Message Title Margaret Lee commented on PUP-11317 Re: Puppet Primary Server support platforms seems outdated. Hi Ross Hansen, thanks for submitting this. We don't support Ubuntu 20.04 or SLES 15 for the primary server right now, but will be adding this sometime in the near future. Targeting sometime next year right now. 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.419297.1634028493000.157259.1634572501523%40Atlassian.JIRA.
Jira (PDB-5332) Add workspaces to exports/imports
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5332 Add workspaces to exports/imports Change By: Rob Browning Sprint: HAHA/Grooming 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.419847.1634571289000.157243.1634571422208%40Atlassian.JIRA.
Jira (PDB-5328) Allow workspace restriction key in query map
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5328 Allow workspace restriction key in query map Change By: Rob Browning Sprint: HAHA/Grooming 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.419843.1634571239000.157239.1634571422055%40Atlassian.JIRA.
Jira (PDB-5333) Allow retrieving the pdb version without a db query
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5333 Allow retrieving the pdb version without a db query Change By: Rob Browning Sprint: HAHA/Grooming 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.419848.1634571298000.157244.1634571422215%40Atlassian.JIRA.
Jira (PDB-5329) Add query support for workspaces and endpoint
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5329 Add query support for workspaces and endpoint Change By: Rob Browning Sprint: HAHA/Grooming 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.419844.1634571251000.157240.1634571422101%40Atlassian.JIRA.
Jira (PDB-5326) Add database storage for workspaces
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5326 Add database storage for workspaces Change By: Rob Browning Sprint: HAHA/Grooming 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.419841.1634571191000.157237.1634571422002%40Atlassian.JIRA.
Jira (PDB-5327) Add configure workspaces command
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5327 Add configure workspaces command Change By: Rob Browning Sprint: HAHA/Grooming 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.419842.1634571219000.157238.1634571422049%40Atlassian.JIRA.
Jira (PDB-5330) Restrict query results to specified workspaces when requested
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5330 Restrict query results to specified workspaces when requested Change By: Rob Browning Sprint: HAHA/Grooming 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.419845.1634571265000.157241.1634571422153%40Atlassian.JIRA.
Jira (PDB-5331) Support workspace sync
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5331 Support workspace sync Change By: Rob Browning Sprint: HAHA/Grooming 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.419846.1634571275000.157242.1634571422162%40Atlassian.JIRA.
Jira (PDB-5333) Allow retrieving the pdb version without a db query
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5333 Allow retrieving the pdb version without a db query Change By: Rob Browning Summary: Support Allow retrieving the pdb version without a db query 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.419848.1634571298000.157236.1634571360204%40Atlassian.JIRA.
Jira (PDB-5329) Add query support for workspaces and endpoint
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5329 Add query support for workspaces and endpoint Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:34 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5333) Support retrieving the version without a db query
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5333 Support retrieving the version without a db query Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:34 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5332) Add workspaces to exports/imports
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5332 Add workspaces to exports/imports Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:34 AM Priority: Normal Reporter: Rob Browning 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.
Jira (PDB-5330) Restrict query results to specified workspaces when requested
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5330 Restrict query results to specified workspaces when requested Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:34 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5331) Support workspace sync
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5331 Support workspace sync Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:34 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5328) Allow workspace restriction key in query map
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5328 Allow workspace restriction key in query map Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:33 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5326) Add database storage for workspaces
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5326 Add database storage for workspaces Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:33 AM Priority: Normal Reporter: Rob Browning 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"
Jira (PDB-5327) Add configure workspaces command
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5327 Add configure workspaces command Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:33 AM Priority: Normal Reporter: Rob Browning 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
Jira (PUP-11320) Regression on user resource
Title: Message Title
Franck Jouvanceau updated an issue
Puppet / PUP-11320
Regression on user resource
Change By:
Franck Jouvanceau
*Puppet Version: 7.8.0 6.23.0 6.24.0 6.24.1 6.25.1* *Puppet Server Version:* - *OS Name/Version: RHEL 7 RHEL 8 CENTOS 7 CENTOS 8*The user resource is not working as expected since puppet agent 6.23/7.8.During a puppet run, if a user is created by any utility (package / exec), the puppet user resource try to luseradd the same user instead of lusermod as the user already exists. The following code:{code}exec { '/sbin/luseradd -u 50080 -M myuser': }-> user { 'myuser': uid=> 50081, forcelocal => true,}{code}produce an error on user resource*Desired Behavior:* before version 6.23{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyNotice: /Stage[main]/Main/User[myuser]/uid: uid changed '50080' to 50081{code} *Actual Behavior:* version 6.23 and after{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyError: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.Error: /Stage[main]/Main/User[myuser]/ensure: change from 'absent' to 'present' failed: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.{code}Seem regression introduced by https://tickets.puppetlabs.com/browse/PUP-11067seems puppet 7.9 has fixed default behavior withhttps with https ://tickets.puppetlabs.com/browse/PUP-11131 but not node done on puppet 6. with:{code:java}- if !self[:purge_ssh_keys].empty?+ if !self[:purge_ssh_keys].empty? && self[:purge_ssh_keys] != :false return [] if self[:ensure] == :present && !provider.exists?{code} (I don't see exactly the link between the regression and this purge_ssh_keys setting, but changing this, is fixing it)But if the purge_ssh_keys is set to true, it is not working anymore even in puppet 7.12 agent...{code}exec { '/sbin/luseradd -u 50080 -M myuser': }-> user { 'myuser': uid=> 50081, forcelocal => true, purge_ssh_keys => true,}{code}{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyError: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.Error: /Stage[main]/Main/User[myuser]/ensure: change from 'absent' to 'present' failed: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.{code}
Jira (PDB-5321) Add query support for workspaces and endpoint
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5321 Add query support for workspaces and endpoint Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:09 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5325) Allow retrieving the pdb version without a db query
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5325 Allow retrieving the pdb version without a db query Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:10 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5323) Support workspace sync
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5323 Support workspace sync Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:10 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5324) Add workspaces to exports/imports
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5324 Add workspaces to exports/imports Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:10 AM Priority: Normal Reporter: Rob Browning 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.
Jira (PDB-5322) Restrict query results to specified workspaces when requested
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5322 Restrict query results to specified workspaces when requested Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:10 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5318) Add database storage for workspaces
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5318 Add database storage for workspaces Change By: Rob Browning Sprint: HAHA/Grooming 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.419830.1634569539000.157211.1634569860316%40Atlassian.JIRA.
Jira (PDB-5320) Allow workspace restriction key in query map
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5320 Allow workspace restriction key in query map Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:09 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5319) Add configure workspaces command
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5319 Add configure workspaces command Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:09 AM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-5318) Add database storage for workspaces
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5318 Add database storage for workspaces Change By: Rob Browning Epic Link: PDB-5317 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.419830.1634569539000.157199.1634569620738%40Atlassian.JIRA.
Jira (PDB-5318) Add database storage for workspaces
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5318 Add database storage for workspaces Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/10/18 8:05 AM Priority: Normal Reporter: Rob Browning 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.
Jira (PDB-5317) Add initial support for workspaces
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5317 Add initial support for workspaces Change By: Rob Browning Team/s: HA 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.419829.1634569018000.157196.1634569320033%40Atlassian.JIRA.
Jira (PDB-5311) Gather consensus regarding workspace plan and create initial tickets
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5311 Gather consensus regarding workspace plan and create initial tickets Change By: Rob Browning Epic Link: PDB-5317 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.418641.1633535986000.157194.1634569200132%40Atlassian.JIRA.
Jira (PDB-5317) Add initial support for workspaces
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5317 Add initial support for workspaces Change By: Rob Browning Component/s: PuppetDB 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.419829.1634569018000.157193.1634569140211%40Atlassian.JIRA.
Jira (PDB-5317) Add initial support for workspaces
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5317 Add initial support for workspaces Issue Type: Epic Assignee: Unassigned Created: 2021/10/18 7:56 AM Priority: Normal Reporter: Rob Browning 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
Jira (FACT-3079) Caching not working for some custom facts
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3079 Caching not working for some custom facts Change By: Ciprian Badescu Sprint: NW - 2021-11-17 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.418624.1633530707000.157170.1634566800032%40Atlassian.JIRA.
Jira (PUP-11320) Regression on user resource
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11320 Regression on user resource Change By: Ciprian Badescu Team: Night's Watch 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.419684.1634300951000.157167.1634566560093%40Atlassian.JIRA.
Jira (PUP-11320) Regression on user resource
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11320 Regression on user resource Change By: Ciprian Badescu Sprint: NW - 2021-11-17 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.419684.1634300951000.157166.1634566560045%40Atlassian.JIRA.
Jira (PUP-11322) Excessive copying of already merged code for the main hostclass
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11322 Excessive copying of already merged code for the main hostclass Change By: Ciprian Badescu Team: Coremunity 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.419718.1634318948000.157162.1634566260098%40Atlassian.JIRA.
Jira (PUP-11323) Puppet agent runs in environment specified on CLI when not in an agent specified environment
Title: Message Title Elaine McCloskey commented on PUP-11323 Re: Puppet agent runs in environment specified on CLI when not in an agent specified environment Attached the debug log debug.txt [root@pe-node-48716e-0 ~]# cat $(puppet config print lastrunfile) --- version: config: pe-server-48716e-0-production-979f19487ef puppet: 6.25.0 application: run_mode: agent initial_environment: testing converged_environment: production resources: changed: 0 corrective_change: 0 failed: 0 failed_to_restart: 0
Jira (PUP-11323) Puppet agent runs in environment specified on CLI when not in an agent specified environment
Title: Message Title Elaine McCloskey updated an issue Puppet / PUP-11323 Puppet agent runs in environment specified on CLI when not in an agent specified environment Change By: Elaine McCloskey Attachment: debug.txt 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.419818.1634552014000.157136.1634565300028%40Atlassian.JIRA.
Jira (PDB-5195) Analysis of Estate Reporting Queries
Title: Message Title Dave Woods commented on PDB-5195 Re: Analysis of Estate Reporting Queries Andrei Filipovici can this be closed now? I am hoping to close LIDAR-915. 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.407463.1626788987000.157135.1634565240218%40Atlassian.JIRA.
Jira (PDB-5219) Investigate query performance for "ESTATE - latest corrective change for specific system"
Title: Message Title Dave Woods commented on PDB-5219 Re: Investigate query performance for "ESTATE - latest corrective change for specific system" Andrei Filipovici can this be closed now? I am hoping to close LIDAR-915. 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.409152.1627566005000.157134.1634565240170%40Atlassian.JIRA.
Jira (PDB-5278) Grouping by a fact with a / in the name generates 500
Title: Message Title Dave Woods commented on PDB-5278 Re: Grouping by a fact with a / in the name generates 500 Austin Blatt any idea when this will be merged? We have a Platypus related ticket dependant on this fix. 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.416232.1631899059000.157129.1634565120146%40Atlassian.JIRA.
Jira (FACT-3074) '--log-level none' throws exception
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3074 '--log-level none' throws exception Change By: Ciprian Badescu Sprint: NW - 2021-11- 17 03 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.415852.1631779051000.157121.1634564700194%40Atlassian.JIRA.
Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-4045 Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket Change By: Ciprian Badescu Sprint: NW - 2021-11- 03 17 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.69478.1424944721000.157120.1634564700147%40Atlassian.JIRA.
Jira (PUP-1460) Puppet hangs trying to replace a FIFO
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-1460 Puppet hangs trying to replace a FIFO Change By: Ciprian Badescu Sprint: NW - 2021-11- 03 17 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.23952.1389949607000.157116.1634563860094%40Atlassian.JIRA.
Jira (FACT-3074) '--log-level none' throws exception
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3074 '--log-level none' throws exception Change By: Ciprian Badescu Sprint: NW - 2021-11- 03 17 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.415852.1631779051000.157115.1634563860070%40Atlassian.JIRA.
Jira (PUP-11320) Regression on user resource
Title: Message Title
Franck Jouvanceau updated an issue
Puppet / PUP-11320
Regression on user resource
Change By:
Franck Jouvanceau
Affects Version/s:
PUP 7.12.0
Affects Version/s:
PUP 7.9.0
Affects Version/s:
PUP 7.10.0
Affects Version/s:
PUP 7.11.0
*Puppet Version: 7.8.0 6.23.0 6.24.0 6.24.1 6.25.1* *Puppet Server Version:* - *OS Name/Version: RHEL 7 RHEL 8 CENTOS 7 CENTOS 8*The user resource is not working as expected since puppet agent 6.23 /7 . 8. During a puppet run, if a user is created by any utility (package / exec), the puppet user resource try to luseradd the same user instead of lusermod as the user already exists. The following code:{code} exec { '/sbin/luseradd -u 50080 -M myuser': }-> user { 'myuser': uid=> 50081, forcelocal => true,} {code}produce an error on user resource*Desired Behavior:* before version 6.23{code} Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyNotice: /Stage[main]/Main/User[myuser]/uid: uid changed '50080' to 50081{code} *Actual Behavior:* version 6.23 and after{code} Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyError: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.Error: /Stage[main]/Main/User[myuser]/ensure: change from 'absent' to 'present' failed: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.{code}Seem regression introduced by https://tickets.puppetlabs.com/browse/PUP-11067 in the commit :{{[5c8472c|https://github.com/puppetlabs/puppet/commit/5c8472ca2b6266cb22cfb896663ac0b191609c63]}}on user.rb adding the line 699{code}return [] if self[:ensure] == :present && !provider.exists? {code} seems puppet 7.9 has been fixed by https default behavior withhttps ://tickets.puppetlabs.com/browse/PUP-11131 but not node on puppet 6 .with:{code:java}- if !self[:purge_ssh_keys].empty?+ if !self[:purge_ssh_keys].empty? && self[:purge_ssh_keys] != :false return [] if self[:ensure]
Jira (PUP-11320) Regression on user resource
Title: Message Title
Franck Jouvanceau updated an issue
Puppet / PUP-11320
Regression on user resource
Change By:
Franck Jouvanceau
*Puppet Version: 7.8.0 6.23.0 6.24.0 6.24.1 6.25.1* *Puppet Server Version:* - *OS Name/Version: RHEL 7 RHEL 8 CENTOS 7 CENTOS 8*The user resource is not working as expected since puppet agent 6.23.During a puppet run, if a user is created by any utility (package / exec), the puppet user resource try to luseradd the same user instead of lusermod as the user already exists. The following code:{code}exec { '/sbin/luseradd -u 50080 -M myuser': }-> user { 'myuser': uid=> 50081, forcelocal => true,}{code}produce an error on user resource*Desired Behavior:* before version 6.23{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyNotice: /Stage[main]/Main/User[myuser]/uid: uid changed '50080' to 50081{code} *Actual Behavior:* version 6.23 and after{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyError: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.Error: /Stage[main]/Main/User[myuser]/ensure: change from 'absent' to 'present' failed: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.{code}Seem regression introduced by https://tickets.puppetlabs.com/browse/PUP-11067in the commit :{{[5c8472c|https://github.com/puppetlabs/puppet/commit/5c8472ca2b6266cb22cfb896663ac0b191609c63]}}on user.rb adding the line 699{code}return [] if self[:ensure] == :present && !provider.exists? {code} seems puppet 7.9 has been fixed by https://tickets.puppetlabs.com/browse/PUP-11131 but not node on puppet 6with:{code:java}- if !self[:purge_ssh_keys].empty?+ if !self[:purge_ssh_keys].empty? && self[:purge_ssh_keys] != :false return [] if self[:ensure] == :present && !provider.exists?{code} (I don't see exactly the link between the regression and this purge_ssh_keys setting, but changing this, is fixing it) But if the purge_ssh_keys is set to true, it is not working anymore even in puppet 7.12 agent...{code}exec { '/sbin/luseradd -u 50080 -M myuser': }-> user { 'myuser': uid=> 50081, forcelocal => true, purge_ssh_keys => true,}{code}{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyError: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.Error: /Stage[main]/Main/User[myuser]/ensure: change from 'absent' to 'present' failed: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.{code}
Jira (PUP-11323) Puppet agent runs in environment specified on CLI when not in an agent specified environment
Title: Message Title Gabriel Nagy commented on PUP-11323 Re: Puppet agent runs in environment specified on CLI when not in an agent specified environment Hi Elaine McCloskey, we shuffled some log messages around as a result of implementing PUP-10539, however in this case PE/classifier should still be authoritative, regardless of what's specified on the CLI. Can you share the following logs? puppet agent -t --debug --environment=testing cat $(puppet config print lastrunfile) 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
Jira (PUP-11323) Puppet agent runs in environment specified on CLI when not in an agent specified environment
Title: Message Title Elaine McCloskey created an issue Puppet / PUP-11323 Puppet agent runs in environment specified on CLI when not in an agent specified environment Issue Type: Bug Affects Versions: PUP 6.25.0 Assignee: Unassigned Created: 2021/10/18 3:13 AM Priority: High Reporter: Elaine McCloskey Puppet Version: 6.25 Puppet Server Version: 2019.8.9 OS Name/Version: tested on centos7 Puppet agent runs in environment specified on CLI when not in an agent specified environment Desired Behavior: In Puppet 6.24 the behaviour is as expected, if a CLI environment is specified but the agent is not in a agent specified node group the run outputs a notice and continues in the server specified environment: [root@pe-node-48716e-0 ~]# puppet agent -t --environment=testing Notice: Local environment: 'testing' doesn't match server specified node environment 'production', switching agent to 'production'. Actual Behavior: After upgrading to 6.25 it runs in the CLI specified environment:
Jira (PUP-11320) Regression on user resource
Title: Message Title
Franck Jouvanceau updated an issue
Puppet / PUP-11320
Regression on user resource
Change By:
Franck Jouvanceau
*Puppet Version: 7.8.0 6.23.0 6.24.0 6.24.1 6.25.1* *Puppet Server Version:* - *OS Name/Version: RHEL 7 RHEL 8 CENTOS 7 CENTOS 8*The user resource is not working as expected since puppet agent 6.23.During a puppet run, if a user is created by any utility (package / exec), the puppet user resource try to luseradd the same user instead of lusermod as the user already exists. The following code:{code}exec { '/sbin/luseradd -u 50080 -M myuser': }-> user { 'myuser': uid=> 50081, forcelocal => true,}{code}produce an error on user resource*Desired Behavior:* before version 6.23{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyNotice: /Stage[main]/Main/User[myuser]/uid: uid changed '50080' to 50081{code} *Actual Behavior:* version 6.23 and after{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyError: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.Error: /Stage[main]/Main/User[myuser]/ensure: change from 'absent' to 'present' failed: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.{code}Seem regression introduced by https://tickets.puppetlabs.com/browse/PUP-11067in the commit :{{[5c8472c|https://github.com/puppetlabs/puppet/commit/5c8472ca2b6266cb22cfb896663ac0b191609c63]}}on user.rb adding the line 699{code}return [] if self[:ensure] == :present && !provider.exists? {code} seems puppet 7.9 has been fixed by https://tickets.puppetlabs.com/browse/PUP-11131 but not node on puppet 6with:{code:java} - if !self[:purge_ssh_keys].empty?+ if !self[:purge_ssh_keys].empty? && self[:purge_ssh_keys] != :false return [] if self[:ensure] == :present && !provider.exists? {code} (I don't see exactly the link between the regression and this purge_ssh_keys setting, but changing this, is fixing it)
Add Comment
Jira (PUP-11320) Regression on user resource
Title: Message Title
Franck Jouvanceau updated an issue
Puppet / PUP-11320
Regression on user resource
Change By:
Franck Jouvanceau
*Puppet Version: 7.8.0 6.23.0 6.24.0 6.24.1 6.25.1* *Puppet Server Version:* - *OS Name/Version: RHEL 7 RHEL 8 CENTOS 7 CENTOS 8*The user resource is not working as expected since puppet agent 6.23.During a puppet run, if a user is created by any utility (package / exec), the puppet user resource try to luseradd the same user instead of lusermod as the user already exists. The following code:{code}exec { '/sbin/luseradd -u 50080 -M myuser': }-> user { 'myuser': uid=> 50081, forcelocal => true,}{code}produce an error on user resource*Desired Behavior:* before version 6.23{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyNotice: /Stage[main]/Main/User[myuser]/uid: uid changed '50080' to 50081{code} *Actual Behavior:* version 6.23 and after{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyError: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.Error: /Stage[main]/Main/User[myuser]/ensure: change from 'absent' to 'present' failed: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.{code}Seem regression introduced by https://tickets.puppetlabs.com/browse/PUP-11067in the commit :{{[5c8472c|https://github.com/puppetlabs/puppet/commit/5c8472ca2b6266cb22cfb896663ac0b191609c63]}}on user.rb adding the line 699{code}return [] if self[:ensure] == :present && !provider.exists? {code} seems puppet 7.9 has been fixed by https://tickets.puppetlabs.com/browse/PUP-11131 but not node on puppet 6with:{code:java} - if !self[:purge_ssh_keys].empty?+ if !self[:purge_ssh_keys].empty? && self[:purge_ssh_keys] != :false return [] if self[:ensure] == :present && !provider.exists? {code} (I don't see exactly the link between the regression and this purge_ssh_keys setting, but changing this, is fixing it)
Add Comment
Jira (PUP-11320) Regression on user resource
Title: Message Title
Franck Jouvanceau updated an issue
Puppet / PUP-11320
Regression on user resource
Change By:
Franck Jouvanceau
*Puppet Version: 7.8.0 6.23.0 6.24.0 6.24.1 6.25.1* *Puppet Server Version:* - *OS Name/Version: RHEL 7 RHEL 8 CENTOS 7 CENTOS 8*The user resource is not working as expected since puppet agent 6.23.During a puppet run, if a user is created by any utility (package / exec), the puppet user resource try to luseradd the same user instead of lusermod as the user already exists. The following code:{code}exec { '/sbin/luseradd -u 50080 -M myuser': }-> user { 'myuser': uid=> 50081, forcelocal => true,}{code}produce an error on user resource*Desired Behavior:* before version 6.23{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyNotice: /Stage[main]/Main/User[myuser]/uid: uid changed '50080' to 50081{code} *Actual Behavior:* version 6.23 and after{code}Notice: /Stage[main]/Main/Exec[/sbin/luseradd -u 50080 -M myuser]/returns: executed successfullyError: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.Error: /Stage[main]/Main/User[myuser]/ensure: change from 'absent' to 'present' failed: Could not create user myuser: Execution of '/usr/sbin/luseradd -g myuser -u 50081 -M myuser' returned 3: Account creation failed: entry already present in file.{code}Seem regression introduced by https://tickets.puppetlabs.com/browse/PUP-11067in the commit :{{[5c8472c|https://github.com/puppetlabs/puppet/commit/5c8472ca2b6266cb22cfb896663ac0b191609c63]}}on user.rb adding the line 699{code}return [] if self[:ensure] == :present && !provider.exists? {code} seems puppet 7.9 has been fixed by https://tickets.puppetlabs.com/browse/PUP-11131 but not node on puppet 6with:{code:java}- if !self[:purge_ssh_keys].empty?+ if !self[:purge_ssh_keys].empty? && self[:purge_ssh_keys] != :false {code} (I don't see exactly the link between the regression and this purge_ssh_keys setting, but changing this, is fixing it)
Add Comment
Jira (PUP-11320) Regression on user resource
Title: Message Title Franck Jouvanceau updated an issue Puppet / PUP-11320 Regression on user resource Change By: Franck Jouvanceau Affects Version/s: PUP 7.8.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.419684.1634300951000.157021.1634550720034%40Atlassian.JIRA.
Jira (PDB-5314) Extract old catalog from PDB
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5314 Extract old catalog from PDB Change By: Sebastian Miclea Assignee: Sebastian Miclea 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.419447.1634111756000.156957.1634541660034%40Atlassian.JIRA.
Jira (PDB-5314) Extract old catalog from PDB
Title: Message Title Andrei Filipovici updated an issue PuppetDB / PDB-5314 Extract old catalog from PDB Change By: Andrei Filipovici Sprint: ghost- 3 20 . 11 10 . 2023 2022 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.419447.1634111756000.156956.1634541420034%40Atlassian.JIRA.
Jira (PDB-5314) Extract old catalog from PDB
Title: Message Title Andrei Filipovici updated an issue PuppetDB / PDB-5314 Extract old catalog from PDB Change By: Andrei Filipovici Extract catalogs * for a single node * for an environment (e.g. production) We also need the facts for one node and for an environment 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.419447.1634111756000.156955.1634541360222%40Atlassian.JIRA.
