Jira (PUP-6289) Puppet 4.4.2 detects samba3x-common incorrect
Title: Message Title
Stefan Heijmans commented on PUP-6289
Re: Puppet 4.4.2 detects samba3x-common incorrect
Did a test with puppet 4.6 2 which still has the same behaviour.
$ puppet --version
4.6.2
$ rpm -qa|grep samba|sort
samba3x-3.6.23-9.el5_11
samba3x-client-3.6.23-9.el5_11
samba3x-common-3.6.23-9.el5_11
samba3x-winbind-3.6.23-9.el5_11
$ puppet resource package samba-common
package { 'samba-common':
ensure => '3.6.23-9.el5_11',
}
Jira (PDB-2850) puppet-client-tools 1.0.1 has no `puppet-db status`
Title: Message Title Stefan Heijmans created an issue PuppetDB / PDB-2850 puppet-client-tools 1.0.1 has no `puppet-db status` Issue Type: Bug Affects Versions: PDB CLI 1.0.1 Assignee: Unassigned Components: PuppetDB Created: 2016/07/05 11:47 AM Environment: Centos 7.2/RHEL7.2 x86_64 puppet-agent-1.5.2 puppetdb-4.1.2 puppet-client-tools-1.0.1 Priority: Normal Reporter: Stefan Heijmans The README.md shows that there is a `puppet-db status` available. $ puppet-db status
Jira (PDB-2846) The [database] classname/subprotocol setting has been retired and will be ignored.
Title: Message Title Stefan Heijmans commented on PDB-2846 Re: The [database] classname/subprotocol setting has been retired and will be ignored. PuppetDB config docs mentions https://docs.puppet.com/puppetdb/4.1/configure.html#using-postgresql To configure PuppetDB to use this database, put the following in the [database] section: classname = org.postgresql.Driver subprotocol = postgresql subname = //:/ username = password = And there is also a deprectated section; https://docs.puppet.com/puppetdb/4.1/configure.html#deprecated-settings classname Note: This setting is deprecated and ignored by PuppetDB. It will be
Jira (PDB-2846) The [database] classname/subprotocol setting has been retired and will be ignored.
Title: Message Title Stefan Heijmans created an issue PuppetDB / PDB-2846 The [database] classname/subprotocol setting has been retired and will be ignored. Issue Type: Bug Affects Versions: PDB 4.1.2 Assignee: Unassigned Components: PuppetDB Created: 2016/06/29 6:07 AM Environment: RHEL 7.2 x86_64 3.10.0-327.13.1.el7.x86_64 puppet-agent-1.5.2-1.el7.x86_64 puppetdb-4.1.2-1.el7.noarch Priority: Normal Reporter: Stefan Heijmans Did an upgrade of PuppetDB 3.2.4 to 4.1.2; # puppet resource package puppetdb ensure=latest
Jira (PUP-6289) Puppet 4.4.2 detects samba3x-common incorrect
Title: Message Title Stefan Heijmans commented on PUP-6289 Re: Puppet 4.4.2 detects samba3x-common incorrect Just did a test on a RHEL5.11 server with a Puppet3 agent, this works fine. cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.11 (Tikanga) puppet --version 3.8.2 rpm -qa|grep samba samba3x-3.6.23-9.el5_11 samba3x-client-3.6.23-9.el5_11 samba3x-common-3.6.23-9.el5_11 samba3x-winbind-3.6.23-9.el5_11
Jira (PUP-6289) Puppet 4.4.2 detects samba3x-common incorrect
Title: Message Title
Stefan Heijmans updated an issue
Puppet / PUP-6289
Puppet 4.4.2 detects samba3x-common incorrect
Change By:
Stefan Heijmans
Just did an upgrade of agent from 3 to 4, now the catalog fails on samba-common package.The following samba packages are installed;{noformat}rpm -qa | grep sambasamba3x-common-3.6.23-9.el5_11samba3x-winbind-3.6.23-9.el5_11{noformat}In the manifest we have; {noformat} ->package { 'samba-common': ensure => absent,}->package { 'samba3x-common': ensure => present,}->{noformat}Which now results in the following error;{noformat}err: Puppet: Execution of '/bin/rpm -e samba3x-common-3.6.23-9.el5_11.x86_64' returned 1: error: Failed dependencies: samba3x-common = 0:3.6.23-9.el5_11 is needed by (installed) samba3x-winbind-3.6.23-9.el5_11.x86_64err: /Stage[main]/Common::Install/Package[samba-common]/ensure: change from 3.6.23-9.el5_11 to absent failed: Execution of '/bin/rpm -e samba3x-common-3.6.23-9.el5_11.x86_64' returned 1: error: Failed dependencies: samba3x-common = 0:3.6.23-9.el5_11 is needed by (installed) samba3x-winbind-3.6.23-9.el5_11.x86_64{noformat}Puppet detects samba3x-common as samba-common which is not correct.samba-common{noformat}puppet resource package samba-commonpackage { 'samba-common': ensure => '3.6.23-9.el5_11',}rpm -q samba-commonpackage samba-common is not installed{noformat}samba3x-common{noformat}puppet resource package samba3x-commonpackage { 'samba3x-common': ensure => '3.6.23-9.el5_11',}rpm -q samba3x-commonsamba3x-common-3.6.23-9.el5_11{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6289) Puppet 4.4.2 detects samba3x-common incorrect
Title: Message Title Stefan Heijmans created an issue Puppet / PUP-6289 Puppet 4.4.2 detects samba3x-common incorrect Issue Type: Bug Affects Versions: PUP 4.4.2 Assignee: Kylo Ginsberg Components: Client Created: 2016/05/11 1:03 AM Environment: Red Hat Enterprise Linux Server release 5.11 (Tikanga) Puppet Opensource; puppet-agent-1.4.2-1.el5 puppet 4.4.2 Priority: Normal Reporter: Stefan Heijmans Just did an upgrade of agent from 3 to 4, now the catalog fails on samba-common package. The following samba packages are installed; rpm -qa | grep samba
Jira (PUP-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Stefan Heijmans commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ Thanks for the update, nr 2 will be nicer then nr.1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Stefan Heijmans commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ Just tested with the PR and both message are now gone. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5524) RHEL7 puppet agent run messages are logged incorrect
Title: Message Title Stefan Heijmans created an issue Puppet / PUP-5524 RHEL7 puppet agent run messages are logged incorrect Issue Type: Bug Affects Versions: PUP 3.8.3 Assignee: Eric Sorenson Components: Community Created: 2015/11/20 3:12 AM Environment: vSphere 5.5U2 VM RHEL7 64bit OS RHEL7.1 x86_64 OpenSource Puppet 3.8.3 Priority: Normal Reporter: Stefan Heijmans Hello, We notice the following on running a puppet agent run through; MCollective vmtoolsd in the OS system log file; /var/log/messages. We see the messages from puppet agent also being logged coming from mcollectived and vmtoolsd. vmtoolsd
Jira (PUP-2651) Loading facts happens twice when environmentpath is in then main section of puppet.conf
Title: Message Title Stefan Heijmans created an issue Puppet / PUP-2651 Loading facts happens twice when environmentpath is in then main section of puppet.conf Issue Type: Bug Affects Versions: 3.6.1 Assignee: Eric Sorenson Components: Community Created: 23/May/14 3:50 AM Environment: VMware guest with RHEL6.5 Ruby 1.8.7.352-13 Puppet 3.6.1 Priority: Normal Reporter: Stefan Heijmans Did an upgrade from Puppet 3.4.3 to 3.6.1 (and also 3.6.0). Now with a puppet run on the puppet master, facts are loaded twice, from modules directory and /var/lib/puppet; Info: Retrieving plugin Info: Loading facts in /etc/puppet/environments/tst/modules/netbackup/lib/facter/netbackup_agent_version.rb Info: Loading facts in /etc/puppet/environments/tst/modules/netbackup/lib/facter/netbackup.rb Info: Loading facts in /etc/puppet/environments/tst/modules/multipath/lib/facter/lvm2version.rb Info: Loading facts in /etc/puppet/environments/tst/modules/multipath/lib/facter/multipathversion.rb Info: Loading facts in /etc/puppet/environments/tst/modules/common/lib/facter/vendor.rb Info: Loading facts in
