Puppet: System Administration Automated

Support

Ticket #1013 (closed defect: fixed)

Opened 10 months ago

Last modified 8 months ago

latest verion of Yum in Fedora Core 7 and 8 break puppet

Reported by: barrowkwan Assigned to: jamtur01
Priority: normal Milestone:
Component: client Version: 0.23.2
Severity: normal Keywords: yum fedora
Cc: Triage Stage: Needs more info
Attached Patches: None Complexity: Unknown

Description

I don't know whether this is Yum or Puppet issue but I think it is a yum but not likely they will make that changes.

the latest yum will give "No matching Packages to list" when run "/usr/bin/yum -d 0 -e 0 list available httpd" instead an empty string as before which totally break puppet

here is the log from puppet Thu Jan 17 18:09:31 -0800 2008 //basenode/sanfrancisco_basenode/sfmisc01/apache/Package[httpd] (err): Failed to retrieve current state of resource: Could not get latest version: Execution of '/usr/bin/yum -d 0 -e 0 list available httpd' returned 256: Error: No matching Packages to list

Change History

01/18/08 09:08:38 changed by jamtur01

  • keywords set to yum fedora.
  • owner changed from community to jamtur01.
  • status changed from new to assigned.
  • stage changed from Unreviewed to Accepted.

Version of yum?

01/22/08 21:53:04 changed by jamtur01

  • stage changed from Accepted to Needs more info.

From further analysis this looks like a Red Hat bug.

01/22/08 21:57:37 changed by fs

This Fedora bugzilla ticket is relevant:

https://bugzilla.redhat.com/show_bug.cgi?id=429597

In short, the 'yum list available' command was not intended to return results for packages that are already installed. One option might be to use the repoquery command instead, although I don't know if this is guaranteed to be installed alongside with yum.

Here's a manifest fragment that will display the problem if the httpd package is installed: 

package { "httpd":
 ensure => latest
}

Also, I've verified that the 0.24 branch, which has a completely rewritten yum provider, does not have the same problem.

04/08/08 17:45:11 changed by luke

  • status changed from assigned to closed.
  • resolution set to fixed.

If this is fixed in 0.24, then the problem is fixed. Yay. :)