Issue #1238 has been updated by Charlie Sharpsteen.
Status changed from Re-opened to Needs More Information
Assignee changed from Charlie Sharpsteen to Gerard Bernabeu
Hi Gerard,
Thanks for taking the time to post a test case. However, I still can't
re-produce this. Using master and agent running CentOS 6.3 and Puppet 3.0.1
with the manifest you posted as the node definition in `site.pp`:
<pre>
[root@puppetagent vagrant]# yum -y remove puppetlabs-release; yum clean all; rm
-f /etc/yum.repos.d/puppet*; ls /etc/yum.repos.d/puppet*
Loaded plugins: fastestmirror, security
Setting up Remove Process
Resolving Dependencies
--> Running transaction check
---> Package puppetlabs-release.noarch 0:6-7 will be erased
--> Finished Dependency Resolution
Dependencies Resolved
==========================================================================================================================================================================
Package Arch
Version Repository
Size
==========================================================================================================================================================================
Removing:
puppetlabs-release noarch
6-7 installed
2.9 k
Transaction Summary
==========================================================================================================================================================================
Remove 1 Package(s)
Installed size: 2.9 k
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Erasing : puppetlabs-release-6-7.noarch
1/1
warning: /etc/yum.repos.d/puppetlabs.repo saved as
/etc/yum.repos.d/puppetlabs.repo.rpmsave
Verifying : puppetlabs-release-6-7.noarch
1/1
Removed:
puppetlabs-release.noarch 0:6-7
Complete!
Loaded plugins: fastestmirror, security
Cleaning repos: base epel extras updates
Cleaning up Everything
Cleaning up list of fastest mirrors
ls: cannot access /etc/yum.repos.d/puppet*: No such file or directory
[root@puppetagent vagrant]# puppet --version
3.0.1
[root@puppetagent vagrant]# puppet agent -t
Info: Retrieving plugin
Info: Caching catalog for puppetagent.boxnet
Info: Applying configuration version '1366669097'
/Stage[main]//Node[puppetagent.boxnet]/Package[puppetlabs-release]/ensure:
created
/Stage[main]//Node[puppetagent.boxnet]/Yumrepo[puppetlabs-deps]/enabled:
enabled changed '1' to '0'
/Stage[main]//Node[puppetagent.boxnet]/Yumrepo[puppetlabs-products]/enabled:
enabled changed '1' to '0'
Finished catalog run in 5.50 seconds
</pre>
I get only one repo definition in `/etc/yum.repos.d`:
<pre>
[root@puppetagent vagrant]# ls /etc/yum.repos.d/puppet*
/etc/yum.repos.d/puppetlabs.repo
</pre>
And everything has been disabled as expected:
<pre>
[root@puppetagent vagrant]# cat /etc/yum.repos.d/puppetlabs.repo
[puppetlabs-products]
name=Puppet Labs Products El 6 - $basearch
baseurl=http://yum.puppetlabs.com/el/6/products/$basearch
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
enabled=0
gpgcheck=1
[puppetlabs-deps]
name=Puppet Labs Dependencies El 6 - $basearch
baseurl=http://yum.puppetlabs.com/el/6/dependencies/$basearch
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
enabled=0
gpgcheck=1
...
</pre>
Which operating system and ruby version are you using?
----------------------------------------
Bug #1238: strange yumrepo/package interaction
https://projects.puppetlabs.com/issues/1238#change-89821
* 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.
