Jira (PUP-11127) Generate short message when PObjectTypes are mismatched
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11127 Generate short message when PObjectTypes are mismatched Change By: Josh Cooper Summary: In TypeMismatch_describer.rb I have suggested changes for more user friendly type error messages Generate short message when PObjectTypes are mismatched 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.404747.1624576451000.69082.1624997700212%40Atlassian.JIRA.
Jira (PUP-11132) SELinux updates
Title: Message Title Josh Cooper commented on PUP-11132 Re: SELinux updates There's also some issues in the puppetlabs-selinux module: https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20MODULES%20AND%20component%20%3D%20selinux_core%20ORDER%20BY%20issuetype%20DESC 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.405070.1624975827000.69078.1624997580146%40Atlassian.JIRA.
Jira (PUP-10955) Environment caches string and symbol environment names differently
Title: Message Title Josh Cooper commented on PUP-10955 Re: Environment caches string and symbol environment names differently Merged to 6.x in https://github.com/puppetlabs/puppet/commit/1da11137af2412c531b4337f60debc7ed426122f 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.390307.1615236079000.69073.1624997400117%40Atlassian.JIRA.
Jira (PUP-10955) Environment caches string and symbol environment names differently
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10955 Environment caches string and symbol environment names differently Change By: Josh Cooper Fix Version/s: PUP 7.9.0 Fix Version/s: PUP 6.24.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.390307.1615236079000.69074.1624997400164%40Atlassian.JIRA.
Jira (PUP-6554) Can't run puppet resource on agent with environment specified in main section
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6554 Can't run puppet resource on agent with environment specified in main section Change By: Josh Cooper Fix Version/s: PUP 7.9.0 Fix Version/s: PUP 6.24.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.143699.1469626368000.68907.1624992060080%40Atlassian.JIRA.
Jira (PUP-6554) Can't run puppet resource on agent with environment specified in main section
Title: Message Title Josh Cooper commented on PUP-6554 Re: Can't run puppet resource on agent with environment specified in main section Merged to 6.x in https://github.com/puppetlabs/puppet/commit/b3c3ef0a00f81c0b4505220fdb9db6cd44d2b86f 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.143699.1469626368000.68906.1624992060035%40Atlassian.JIRA.
Jira (PUP-6801) agent_specified_environment fact doesn't populate with the environment setting in the [agent] section
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6801 agent_specified_environment fact doesn't populate with the environment setting in the [agent] section Change By: Josh Cooper Fix Version/s: PUP 7.9.0 Fix Version/s: PUP 6.24.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.155635.1475796831000.68897.1624991760145%40Atlassian.JIRA.
Jira (PUP-6801) agent_specified_environment fact doesn't populate with the environment setting in the [agent] section
Title: Message Title Josh Cooper commented on PUP-6801 Re: agent_specified_environment fact doesn't populate with the environment setting in the [agent] section Merged to 6.x in https://github.com/puppetlabs/puppet/commit/f1af4aa7fcc76d0aca803bb64e27ed40e215cfcb 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.155635.1475796831000.68894.1624991700036%40Atlassian.JIRA.
Jira (PUP-10641) Puppet Module Tool gives unhelpful error message for bad module name
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10641 Puppet Module Tool gives unhelpful error message for bad module name Change By: Josh Cooper Release Notes: Enhancement Release Notes Summary: The "puppet module install " command prints a better error if the author component of the name is omitted. 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.59877.1417031796000.68860.1624991040253%40Atlassian.JIRA.
Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9570 Catalog failure on first run due to pluginsync and environment switch Change By: Josh Cooper Sprint: Coremunity Hopper Platform Core 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.300842.1553021716000.68746.1624989120367%40Atlassian.JIRA.
Jira (PUP-10641) Puppet Module Tool gives unhelpful error message for bad module name
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10641 Puppet Module Tool gives unhelpful error message for bad module name Change By: Josh Cooper Fix Version/s: PUP 7.9.0 Fix Version/s: PUP 6.24.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.59877.1417031796000.68725.1624988760033%40Atlassian.JIRA.
Jira (PUP-11131) Puppet type 'user' does not honor 'purge_ssh_keys: false'
Title: Message Title Josh Cooper commented on PUP-11131 Re: Puppet type 'user' does not honor 'purge_ssh_keys: false' If you remove the purge_ssh_keys parameter, then it should work as expected, since the default is to not purge. That said, I agree short-circuiting when it's set to :false makes sense, though I find double negatives confusing, so maybe: if !self[:purge_ssh_keys].empty? && self[:purge_ssh_keys] != :false}} Note in general we don't fix bugs or implement features for third-party packages of puppet. But if you'd like to submit a pull request, we'd gladly accept. 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.405068.1624975314000.68723.1624988580282%40Atlassian.JIRA.
Jira (PUP-11131) Puppet type 'user' does not honor 'purge_ssh_keys: false'
Title: Message Title Christoph Bihler commented on PUP-11131 Re: Puppet type 'user' does not honor 'purge_ssh_keys: false' Josh Cooper that's correct, we're packaging ourselves based on puppet opensource version (and haven't changed our specfiles from 6.22→6.23, so that's something new). basically we: take source from https://downloads.puppetlabs.com/puppet/puppet-.tar.gz add: Facter Hiera Ruby Augeas Ruby Shadow add ruby gems: Concurrent Ruby Deep Merge Fast Gettext Hiera eYAML Highline Hocon HTTP Client Locale Multi JSON Puppet Resource API Semantic Puppet Trollop These are mostly the dependencies listed here: https://github.com/puppetlabs/puppet/blob/main/.gemspec#L34-L42 If there are some (external) module dependencies to make puppet (agent) run, they should be listed somewhere, or am I missing something? Especially, it feels strange for me that a module is required if I explicitly tell the code not to use it (therefore the patch) Add Comment
Jira (PUP-10853) When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact
Title: Message Title Beth Glenfield updated an issue Puppet / PUP-10853 When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact Change By: Beth Glenfield Epic Link: FACT-3051 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.383136.1610563179000.68327.1624982340115%40Atlassian.JIRA.
Jira (PUP-10853) When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact
Title: Message Title Beth Glenfield assigned an issue to Unassigned Puppet / PUP-10853 When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact Change By: Beth Glenfield Assignee: Beth Glenfield 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.383136.1610563179000.68328.1624982340161%40Atlassian.JIRA.
Jira (PDB-5164) Fully document AST field syntax
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5164 Fully document AST field syntax 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.405083.1624981418000.68301.1624981440131%40Atlassian.JIRA.
Jira (PDB-5164) Fully document AST field syntax
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5164 Fully document AST field syntax Issue Type: Improvement Assignee: Rob Browning Components: PuppetDB Created: 2021/06/29 8:43 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 (PUP-11134) server_list not fully working on Windows
Title: Message Title Ciprian Badescu commented on PUP-11134 Re: server_list not fully working on Windows Vadym Chepkov, is agent run failing on Windows or it is just the connection failure logged as error on Windows? 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.405081.1624980264000.68283.1624980540131%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Ciprian Badescu commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails Vadym Chepkov, we created a new ticket to track Windows specific error (https://tickets.puppetlabs.com/browse/PUP-11134) 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.381638.1608653215000.68279.1624980420026%40Atlassian.JIRA.
Jira (PUP-11134) server_list not fully working on Windows
Title: Message Title Ciprian Badescu created an issue Puppet / PUP-11134 server_list not fully working on Windows Issue Type: Bug Assignee: Unassigned Created: 2021/06/29 8:24 AM Priority: Normal Reporter: Ciprian Badescu PE Version: 2019.8.7 Puppet Server Version: 6.23.0 OS Name/Version: Windows server_list not fully working on Windows: Could not retrieve catalog from remote server: Request to https://infdevx-puppet202.example.com:8140/puppet/v3/catalog/infdevw-mdt001.example.com?environment=windows_development failed after 1.027 seconds: Failed to open TCP connection to infdevx-puppet202.example.com:8140 (No connection could be made because the target machine actively refused it. - connect(2) for "infdevx-puppet202.example.com" port 8140) Wrapped exception:
Jira (PUP-5474) Solaris service provider lies about service state
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-5474 Solaris service provider lies about service state Change By: Ciprian Badescu Epic Link: PUP-11133 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.104450.1446683843000.68261.1624979940038%40Atlassian.JIRA.
Jira (PUP-4993) systemd thinks 'activating' services are 'stopped'
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-4993 systemd thinks 'activating' services are 'stopped' Change By: Ciprian Badescu Epic Link: PUP-11133 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.91706.1438630147000.68260.1624979880086%40Atlassian.JIRA.
Jira (PUP-10885) Race-condition in service resource
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-10885 Race-condition in service resource Change By: Ciprian Badescu Epic Link: PUP-11133 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.385969.1612347692000.68255.1624979760157%40Atlassian.JIRA.
Jira (PUP-11133) Service provider enhancement
Title: Message Title Ciprian Badescu created an issue Puppet / PUP-11133 Service provider enhancement Issue Type: Epic Assignee: Unassigned Created: 2021/06/29 8:14 AM Priority: Normal Reporter: Ciprian Badescu Currently service state is binary and any not-running state is considered stopped. When services are not in stopped state but in transitional state(starting/stopping), puppet will consider them stopped and will try to restart the service while in fact the service is currently starting but not fully started. This epic should add support for transitional state like starting/stopping. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11126) PowerShell Validity check
Title: Message Title Erwin Solis commented on PUP-11126 Re: PowerShell Validity check Josh Cooper I don't believe you replicated the scenario and instead created an entirely different outcome and subsequent error message with the steps you took. The request is not to second-guess the OS or its built-in security, the request is to catch and log the scenario provided with a descriptive error message, so that customers can identify the issue and correct it. It's also a good defensive coding practice to validate an external binary before attempting to have it execute code. 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.404383.1624476059000.68218.1624979040023%40Atlassian.JIRA.
Jira (PUP-11131) Puppet type 'user' does not honor 'purge_ssh_keys: false'
Title: Message Title Josh Cooper commented on PUP-11131 Re: Puppet type 'user' does not honor 'purge_ssh_keys: false' Christoph Bihler the error message means the https://forge.puppet.com/modules/puppetlabs/sshkeys_core module is not installed. Based on the file path /opt/puppetlabs/puppet/lib64/ruby/vendor_ruby/puppet/type/user.rb it appears you're not running for puppet-agent packages built by Puppet. 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.405068.1624975314000.68212.1624978805897%40Atlassian.JIRA.
Jira (PUP-11127) In TypeMismatch_describer.rb I have suggested changes for more user friendly type error messages
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11127 In TypeMismatch_describer.rb I have suggested changes for more user friendly type error messages Change By: Ciprian Badescu Team: Bolt 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.404747.1624576451000.68203.1624978500090%40Atlassian.JIRA.
Jira (PUP-11129) Cached environment may not be deleted if the directory is removed
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11129 Cached environment may not be deleted if the directory is removed Change By: Ciprian Badescu Epic Link: PUP-10539 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.405015.162492624.68121.1624977240103%40Atlassian.JIRA.
Jira (PUP-11129) Cached environment may not be deleted if the directory is removed
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11129 Cached environment may not be deleted if the directory is removed 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.405015.162492624.68122.1624977240148%40Atlassian.JIRA.
Jira (PUP-11130) LogonAccount not working with MSSQLSERVER service
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11130 LogonAccount not working with MSSQLSERVER service Change By: Mihai Buzgau Zendesk Ticket Count: 1 Zendesk Ticket IDs: 44707 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.405066.1624968914000.68079.1624976100081%40Atlassian.JIRA.
Jira (PUP-11132) SELinux updates
Title: Message Title Ciprian Badescu created an issue Puppet / PUP-11132 SELinux updates Issue Type: Epic Assignee: Unassigned Created: 2021/06/29 7:10 AM Priority: Normal Reporter: Ciprian Badescu 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-7375) Puppet does not change file to directory when selinux is enabled
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-7375 Puppet does not change file to directory when selinux is enabled Change By: Ciprian Badescu Epic Link: PUP-11132 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.181500.1490035286000.68065.1624975860249%40Atlassian.JIRA.
Jira (PUP-11131) Puppet type 'user' does not honor 'purge_ssh_keys: false'
Title: Message Title
Christoph Bihler created an issue
Puppet / PUP-11131
Puppet type 'user' does not honor 'purge_ssh_keys: false'
Issue Type:
Bug
Affects Versions:
PUP 6.23.0
Assignee:
Unassigned
Components:
Types and Providers
Created:
2021/06/29 7:01 AM
Priority:
Normal
Reporter:
Christoph Bihler
It seems that the type user does not honor setting purge_ssh_keys => false correctly. puppet language:
user { "myuser":
ensure => present,
[...]
purge_ssh_keys => false,
}
Jira (PUP-11130) LogonAccount not working with MSSQLSERVER service
Title: Message Title
Bartosz Blizniak updated an issue
Puppet / PUP-11130
LogonAccount not working with MSSQLSERVER service
Change By:
Bartosz Blizniak
*Puppet Version: 7.6.0* *Puppet Server Version: 2021.1* *OS Name/Version: Primary RHEL8 & Agent(issues) Windows Server 2019*The customer is having issues with running MSSQL service by passing `logonaccount` parameters. {{Error: Failed to apply catalog: Parameter logonpassword failed on Service[MSSQLSERVER]: Failed to update service configuration: The account name is invalid or does not exist, or the password is invalid for the account name specified. (file: /etc/puppetlabs/code/modules/profiles/manifests/windows/mssql.pp, line: 32)}}The customer has tried to insert different combinations of LogonAccount (also trying to pass full path):1. PILOT\rma_sql_svc 2. PILOT rma_sql_svc 3. pilot.usda.lab domain \rma_sql_svc 4. pilot.usda.lab domain rma_sql_svc 6. [rma_sql_svc@ pilot.usda.lab domain |mailto:rma_sql_...@pilot.usda.lab]Code snippet:{{service {'MSSQLSERVER':}} {{ logonaccount => 'pilot.usda.lab}} {{rma_sql_svc',}} {{ logonpassword => 'Password1234', #sensitive}} {{ ensure => 'running'}}{{}}}**The puppet service account was given both Domain administrator and local administrator rights and nothing has worked. One of our engineers has managed to create a workaround and stated:"We added debug logs and the conclusion is that the error comes from Windows API and probably is caused by the way the MSSQLSERVER services are defined(maybe they are protected?), since we are not setting specifically the logon account on the respective API request." *Desired Behavior:* Run the MSSQL with a specific account. *Actual Behavior:* Windows API and MSSQLSERVER possibly have different ways of communicating and setting the accounts, which means that the current implementation of LogonAccount won't work for this specific service. *Workaround applied:* the direction was to use {{exec}} resource with {{unless}} parameter that will apply {{exec}} resource only if {{unless}} script return value is not 0. A bug was raised under: https://tickets.puppetlabs.com/browse/PUP-11121More information from the customer ticket: [https://puppetlabs.zendesk.com/agent/tickets/44707]
Add Comment
Jira (PUP-11130) LogonAccount not working with MSSQLSERVER service
Title: Message Title
Bartosz Blizniak created an issue
Puppet / PUP-11130
LogonAccount not working with MSSQLSERVER service
Issue Type:
New Feature
Affects Versions:
PUP 7.6.0
Assignee:
Unassigned
Components:
Windows
Created:
2021/06/29 5:15 AM
Priority:
Normal
Reporter:
Bartosz Blizniak
Puppet Version: 7.6.0 Puppet Server Version: 2021.1 OS Name/Version: Primary RHEL8 & Agent(issues) Windows Server 2019 The customer is having issues with running MSSQL service by passing `logonaccount` parameters. Error: Failed to apply catalog: Parameter logonpassword failed on Service[MSSQLSERVER]: Failed to update service configuration: The account name is invalid or does not exist, or the password is invalid for the account name specified. (file: /etc/puppetlabs/code/modules/profiles/manifests/windows/mssql.pp, line: 32) The customer has tried to insert different combinations of LogonAccount (also trying to pass full path): 1. PILOT\rma_sql_svc 2. PILOT rma_sql_svc 3. pilot.usda.lab\rma_sql_svc 4. pilot.usda.lab rma_sql_svc 6. rma_sql_...@pilot.usda.lab Code snippet: service {'MSSQLSERVER': logonaccount => 'pilot.usda.lab rma_sql_svc', logonpassword => 'Password1234', #sensitive ensure => 'running'} **The puppet service account was given both Domain administrator and local administrator rights and nothing has worked. One of our engineers has managed to create a workaround and stated: "We added debug logs and the conclusion is that the error comes from Windows API and probably is caused by the way the MSSQLSERVER services are defined(maybe they are protected?), since we are not setting specifically the logon account on the respective API request." Desired Behavior: Run the MSSQL with a specific account. Actual Behavior: Windows API and MSSQLSERVER possibly have
Jira (PUP-394) Install windows packages from remote sources
Title: Message Title Ciprian Badescu commented on PUP-394 Re: Install windows packages from remote sources Josh Cooper, do you think this is still an issue? 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.14942.1379575018000.67894.1624959960214%40Atlassian.JIRA.
Jira (FACT-3049) Reading the `/etc/resolv.conf` file for the domain value
Title: Message Title Ciprian Badescu commented on FACT-3049 Re: Reading the `/etc/resolv.conf` file for the domain value Paul Liong, as per Selvakumar Azhagarsami comment, facter will use /etc/resolv.conf only when DNS resolving fails (`gethostname`/`hostname -f` are doing DNS lookup). 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.401272.1622450814000.67790.1624954080027%40Atlassian.JIRA.
Jira (PUP-10962) Migrate SELinux util from matchpathcon(3) to selabel_lookup(3)
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-10962 Migrate SELinux util from matchpathcon(3) to selabel_lookup(3) Change By: Ciprian Badescu Epic Link: PUP-7384 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.390652.1615457543000.67711.1624949820029%40Atlassian.JIRA.
Jira (PUP-7375) Puppet does not change file to directory when selinux is enabled
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-7375 Puppet does not change file to directory when selinux is enabled Change By: Ciprian Badescu Sprint: ready for triage 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.181500.1490035286000.67710.1624949700039%40Atlassian.JIRA.
