Bug #2833

yum provider keeps re-purging package

Added by Adrian Bridgett over 2 years ago. Updated about 1 year ago.

Status:Duplicate Start date:11/18/2009
Priority:Normal Due date:
Assignee:Jesse Wolfe % Done:

0%
Category:package
Target version:-
Affected Puppet version: Branch:
Keywords:
Votes: 0

Description

With a manifest containing:

package { "nano": ensure => purged; }

Each time I run puppet I’m seeing this:

debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q nano --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}
'
debug: //Node[redhat]/default_class/packages::purge::basic/Package[nano]: Changing ensure
debug: //Node[redhat]/default_class/packages::purge::basic/Package[nano]: 1 change(s)
debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -y erase nano'
notice: //Node[redhat]/default_class/packages::purge::basic/Package[nano]/ensure: created

Even though the package isn’t installed. I can’t see anything in subsequent releases that suggest this may have changed. On Debian this seems to work just fine (no notices). This also means that related notifies keep being called even though the system state isn’t changing.

History

#1
Updated by Markus Roberts over 2 years ago

  • Status changed from Unreviewed to Investigating
  • Assignee set to Jesse Wolfe

#2
Updated by Adrian Bridgett over 2 years ago

I should have said this is on RHEL5.4

#3
Updated by Markus Roberts over 2 years ago

  • Target version set to 0.25.3

Note that this is on 0.24.8, so first step is make sure it hasn’t been fixed already.

#4
Updated by Dan Bode over 2 years ago

  • Affected Puppet version changed from 0.24.8 to 0.25.2rc2

I just investigated since it was reported in the forums:

I checked-out origin/0.25.x (which affected version should I label this as?)

[root@exporter puppet]# puppet -e'package{"testdisk-doc": ensure => installed}'[root@exporter puppet]# puppet -e'package{"testdisk-doc": ensure => purged}'
notice: //Package[testdisk-doc]/ensure: ensure changed '6.11-3.el5' to 'purged'
[root@exporter puppet]# puppet -e'package{"testdisk-doc": ensure => purged}'
notice: //Package[testdisk-doc]/ensure: created
[root@exporter puppet]# puppet -e'package{"testdisk-doc": ensure => purged}'
notice: //Package[testdisk-doc]/ensure: created

and recreated.

#5
Updated by Jesse Wolfe over 2 years ago

  • Status changed from Investigating to Needs Decision

It seems that yum doesn’t really have separate “purged” and “absent” states. Usually we’d disable “purged”, but I’m not certain if I want to introduce that as a breaking change for 0.25.2

#6
Updated by Markus Roberts over 2 years ago

  • Target version changed from 0.25.3 to 0.25.4

#7
Updated by James Turnbull over 2 years ago

  • Target version changed from 0.25.4 to 0.25.5

#8
Updated by James Turnbull about 2 years ago

  • Target version changed from 0.25.5 to 49

#9
Updated by Brian Rak almost 2 years ago

Please don’t disable purged. It’s the only way to work around #1935 .

Also, this seems like a duplicate of #3707 to me.

#10
Updated by James Turnbull over 1 year ago

  • Target version deleted (49)

#11
Updated by James Turnbull about 1 year ago

  • Status changed from Needs Decision to Duplicate
  • Affected Puppet version deleted (0.25.2rc2)

Duplicate of #3707 (closing in favour of that ticket)

Also available in: Atom PDF