[Puppet - Bug #2833] (Unreviewed) yum provider keeps re-purging package
red...@reductivelabs.com
Bug #2833: yum provider keeps re-purging package
- Author: Adrian Bridgett
- Status: Unreviewed
- Priority: Normal
- Assigned to:
- Category: package
- Target version:
- Affected version: 0.24.8
- Keywords:
- Branch:
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.
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://reductivelabs.com/redmine/my/account
red...@reductivelabs.com
- Target version set to Puppet - 0.25.3
Note that this is on 0.24.8, so first step is make sure it hasn't been fixed already.
- Author: Adrian Bridgett
- Status: Investigating
- Priority: Normal
- Assigned to: Jesse Wolfe
- Category: package
- Target version: 0.25.3
- Affected version: 0.24.8
- Keywords:
- Branch:
red...@reductivelabs.com
- Affected 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.
- Author: Adrian Bridgett
- Status: Investigating
- Priority: Normal
- Assigned to: Jesse Wolfe
- Category: package
- Target version: 0.25.3
- Affected version: 0.25.2rc2
- Keywords:
- Branch:
red...@reductivelabs.com
- Status changed from Investigating to Needs design 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.3
- Author: Adrian Bridgett
- Status: Needs design decision
- Priority: Normal
- Assigned to: Jesse Wolfe
- Category: package
- Target version: 0.25.3
- Affected version: 0.25.2rc2
- Keywords:
- Branch:
red...@reductivelabs.com
- Target version changed from Puppet - 0.25.3 to Puppet - 0.25.4
- Author: Adrian Bridgett
- Status: Needs design decision
- Priority: Normal
- Assigned to: Jesse Wolfe
- Category: package
- Target version: 0.25.4
- Affected version: 0.25.2rc2
- Keywords:
- Branch:
red...@reductivelabs.com
- Target version changed from Puppet - 0.25.4 to Puppet - 0.25.5
- Author: Adrian Bridgett
- Status: Needs design decision
- Priority: Normal
- Assigned to: Jesse Wolfe
- Category: package
- Target version: 0.25.5
- Affected version: 0.25.2rc2
- Keywords:
- Branch: