Jira (PUP-11206) Exec modules with powershell as a provider do not display any logs from commands.
Title: Message Title Maciej Sikora created an issue Puppet / PUP-11206 Exec modules with powershell as a provider do not display any logs from commands. Issue Type: Bug Assignee: Unassigned Created: 2021/08/13 5:24 AM Environment: Any Windows system Priority: Major Reporter: Maciej Sikora Puppet Version: 7.9.0 Puppet Server Version: 7.9.0 OS Name/Version: Windows When using exec module with powershell as a provider, puppet doesn't display any logs. It doesn't matter if --verbose, or --debug is provided as a flag with starting puppet script or if logoutput is set to true as a parameter of module. Example of a command that doesn't displays anything "Get-Content $path_to_an_existing_file" Desired Behavior: The module displays everything that a command executed from a powershell would execute. Actual Behavior: Puppet doesn't displays anything other than "executed successfully" Add Comment
Jira (PDB-5211) Check whether PuppetDB still doesn't complete shutdown after migration fails
Title: Message Title Andrei Filipovici commented on PDB-5211 Re: Check whether PuppetDB still doesn't complete shutdown after migration fails Also the interesting thing is that PuppetDB is started in a loop, but it won't be able to start. So, if you do a: journalctl -u puppetdb | grep 'Failed to start puppetdb Service' you'll see a bunch of: Aug 13 09:53:34 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:53:43 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:53:53 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:02 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:12 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:21 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:31 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:40 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:50 well-clover systemd[1]: Failed to start puppetdb Service.
Jira (PDB-5211) Check whether PuppetDB still doesn't complete shutdown after migration fails
Title: Message Title
Andrei Filipovici commented on PDB-5211
Re: Check whether PuppetDB still doesn't complete shutdown after migration fails
Tried on a centos-7-x86_64 machine with the puppet agent 7.9.0 and puppetdb versions 6.12.0 and 7.9.0. I first installed puppetdb version 6.12.0 and modified a table that breaks migration 78. The exact steps are as follows: rpm -Uvh https://yum.puppet.com/puppet7-release-el-7.noarch.rpm yum install -y puppet agent /opt/puppetlabs/bin/puppet module install puppetlabs-puppetdb --version 7.9.0 yum install java-1.8.0-openjdk-headless rpm -ivh http://builds.delivery.puppetlabs.net/puppetdb/6.12.0/artifacts/el/7/puppet6/x86_64/puppetdb-6.12.0-1.el7.noarch.rpm /opt/puppetlabs/puppet/bin/puppet apply << EOF class {'puppetdb::globals': version => '6.12.0'} class {'puppetdb': disable_ssl => true} EOF sudo -u postgres /usr/bin/psql -d puppetdb -c "ALTER TABLE certnames ADD COLUMN catalog_inputs_hash bytea" wget http://builds.delivery.puppetlabs.net/puppetdb/7.5.2/artifacts/el/7/puppet7/x86_64/puppetdb-7.5.2-1.el7.noarch.rpm /opt/puppetlabs/bin/puppet resource --evaltrace package puppetdb ensure=7.5.2 provider=rpm source=/root/puppetdb-7.5.2-1.el7.noarch.rpm tail -f /var/log/puppetlabs/puppetdb/puppetdb.log journalctl -u puppetdb | grep 'Failed to start puppetdb Service' cat /usr/lib/systemd/system/puppetdb.service
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.
Jira (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Sebastian Miclea assigned an issue to Unassigned PuppetDB / PDB-3715 PuppetDB doesn't complete shutdown after migration fails 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.216460.1508186567000.106868.1628841960047%40Atlassian.JIRA.
Jira (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-3715 PuppetDB doesn't complete shutdown after migration fails 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.216460.1508186567000.106866.1628841900026%40Atlassian.JIRA.
Jira (PDB-5203) Script that runs the pdb benchmark tests
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5203 Script that runs the pdb benchmark tests 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.408406.162704879.106862.1628840160042%40Atlassian.JIRA.
