Issue #1238 has been updated by Gerard Bernabeu.
Hi, The behaviour you're showing is what I'd expect but can not get... One difference I saw with your run is that I am using stages (same stage for the whole class) but tried with everything in the main stage and still got the issue. I tried updating the ruby and puppet version but I still have the issue. Now I am running with the following RPM versions: [root@fcl-puppet ~]# rpm -qa | grep ruby ruby-shadow-1.4.1-13.el6.x86_64 ruby-mysql-2.8.2-1.el6.x86_64 ruby-libs-1.8.7.352-10.el6_4.x86_64 ruby-irb-1.8.7.352-10.el6_4.x86_64 ruby-rdoc-1.8.7.352-10.el6_4.x86_64 libselinux-ruby-2.0.94-5.3.el6.x86_64 rubygems-1.3.7-1.el6.noarch ruby-augeas-0.4.1-1.el6.x86_64 rubygem-rake-0.8.7-2.1.el6.noarch ruby-1.8.7.352-10.el6_4.x86_64 ruby-devel-1.8.7.352-10.el6_4.x86_64 rubygem-json-1.5.5-1.el6.x86_64 [root@fcl-puppet ~]# rpm -qa | grep puppet puppetdb-1.2.0-1.el6.noarch puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch puppet-server-3.1.1-1.el6.noarch puppet-dashboard-1.2.23-1.el6.noarch puppetdb-terminus-1.2.0-1.el6.noarch This is Scientific Linux Fermi 6.3, which should not be too different from CentOS6: [root@fcl-puppet ~]# facter | grep oper operatingsystem => Scientific operatingsystemmajrelease => 6 operatingsystemrelease => 6.3 [root@fcl-puppet ~]# facter | grep lsb lsbdistcodename => Ramsey lsbdistdescription => Scientific Linux Fermi release 6.3 (Ramsey) lsbdistid => ScientificFermi lsbdistrelease => 6.3 lsbmajdistrelease => 6 lsbrelease => :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch [root@fcl-puppet ~]# Can you provide an output with debugging enabled? Maybe I can spot any difference... Thanks, Gerard ---------------------------------------- Bug #1238: strange yumrepo/package interaction https://projects.puppetlabs.com/issues/1238#change-89832 * Author: BMDan - * Status: Needs More Information * Priority: Normal * Assignee: Gerard Bernabeu * Category: yumrepo * Target version: 3.x * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- Yumrepo appears to be checking file existence before allowing the package command to complete, meaning that it creates a file containing only "[remi]" and "enabled=1", overwriting the file that the RPM installed. Manifests, additional debug output, etc., available upon request. Just tell me what you need to know. Workarounds especially welcomed. Puppet v. 0.24.4, running with --debug --test, on Ruby 1.8.6.114-1, compiled from source with default options. <pre> debug: //Node[default]/remi_enabled/Yumrepo[remi]/require: requires Package[remi-release-5-4.el5.remi] </pre> ... <pre> debug: Puppet::Type::Package::ProviderRpm: Not suitable: false value debug: Puppet::Type::Package::ProviderRpm: Executing '/bin/rpm -q remi-release-5-4.el5.remi --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}' debug: /Package[remi-release-5-4.el5.remi]: Changing ensure debug: /Package[remi-release-5-4.el5.remi]: 1 change(s) debug: Puppet::Type::Package::ProviderRpm: Executing '/bin/rpm -i --oldpackage http://rpms.famillecollet.com/el5.x86_64/remi-release-5-4.el5.remi.noarch.rpm' notice: /Package[remi-release-5-4.el5.remi]/ensure: created info: create new repo remi in file /etc/yum.repos.d/remi.repo debug: //Node[default]/remi_enabled/Yumrepo[remi]: Changing enabled debug: //Node[default]/remi_enabled/Yumrepo[remi]: 1 change(s) notice: //Node[default]/remi_enabled/Yumrepo[remi]/enabled: defined 'enabled' as '1' info: Filebucket[/var/lib/puppet/clientbucket]: Adding /etc/yum.repos.d/remi.repo(18f7009978e772c9c646b9410fa3a8b6) </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
