Jira (PUP-11121) LogonAccount in Service Resource doesn't detect AD account
Title: Message Title Austin Boyd updated an issue Puppet / PUP-11121 LogonAccount in Service Resource doesn't detect AD account Change By: Austin Boyd Labels: jira_escalated support 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.403900.1623923251000.59170.1623925500091%40Atlassian.JIRA.
Jira (PUP-11121) LogonAccount in Service Resource doesn't detect AD account
Title: Message Title Austin Boyd updated an issue Puppet / PUP-11121 LogonAccount in Service Resource doesn't detect AD account Change By: Austin Boyd 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.403900.1623923251000.59169.1623925500040%40Atlassian.JIRA.
Jira (PUP-11121) LogonAccount in Service Resource doesn't detect AD account
Title: Message Title
Bartosz Blizniak updated an issue
Puppet / PUP-11121
LogonAccount in Service Resource doesn't detect AD account
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)}}I have attached the code provided by the customer and also a screenshot of their AD structure. The customer has tried to insert different combinations of LogonAccount (also trying to pass full path):1. PILOT\rma_sql_svc2. PILOT \\ rma_sql_svc3. pilot.usda.lab\rma_sql_svc4. pilot.usda.lab \\ rma_sql_svc6. [rma_sql_...@pilot.usda.lab|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. The customer has also stated:"When we install puppet, it is not yet joined to the domain. Puppet will join the server to the domain after the first run of its agent. Until then it has a local service account assigned.When I try to tell puppet to change its account from local service to the domain account, I get an access denied (assuming the local account is unable to do the lookup of the domain account)."*Desired Behavior:* Run the MSSQL with a specific account without giving puppet service domain administrator rights (just local) .*Actual Behavior:* Fails to find the domain account specified.
Add Comment
Jira (PUP-11121) LogonAccount in Service Resource doesn't detect AD account
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11121 LogonAccount in Service Resource doesn't detect AD account Change By: Luchian Nemes 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.403900.1623923251000.59164.1623924960112%40Atlassian.JIRA.
Jira (PUP-11121) LogonAccount in Service Resource doesn't detect AD account
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11121 LogonAccount in Service Resource doesn't detect AD account Change By: Luchian Nemes 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.403900.1623923251000.59163.1623924960053%40Atlassian.JIRA.
Jira (PUP-11121) LogonAccount in Service Resource doesn't detect AD account
Title: Message Title Bartosz Blizniak created an issue Puppet / PUP-11121 LogonAccount in Service Resource doesn't detect AD account Issue Type: Bug Affects Versions: PUP 7.6.0 Assignee: Unassigned Attachments: Screenshot 2021-06-15 195925.png, Screenshot 2021-06-15 200107.png, Screenshot 2021-06-16 09.png, Screenshot 2021-06-16 093414.png, mysql.pp, mysql.yaml Components: Windows Created: 2021/06/17 2:47 AM Due Date: 2021/06/22 Labels: support Priority: Major 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) I have attached the code provided by the customer and also a screenshot of their AD structure. The customer has tried to insert different
