Updates still saying failed when they didn't

Submitted by arjones85 on Fri, 10/22/2010 - 14:27

Virtualmin updates are emailing me the following:

An update to glibc from 2.5-49.el5_5.5 to 2.5-49.el5_5.6 is needed.
This update has been successfully installed.

An update to glibc-common from 2.5-49.el5_5.5 to 2.5-49.el5_5.6 is needed.
However, this update could not be installed! Try the update manually
using the Package Updates module.

An update to glibc-devel from 2.5-49.el5_5.5 to 2.5-49.el5_5.6 is needed.
However, this update could not be installed! Try the update manually
using the Package Updates module.

An update to glibc-headers from 2.5-49.el5_5.5 to 2.5-49.el5_5.6 is needed.
However, this update could not be installed! Try the update manually
using the Package Updates module.

An update to nscd from 2.5-49.el5_5.5 to 2.5-49.el5_5.6 is needed.
However, this update could not be installed! Try the update manually
using the Package Updates module.

However when looking at yum.log, they were installed just fine:

Oct 22 00:41:17 Updated: glibc-common-2.5-49.el5_5.6.i386
Oct 22 00:41:34 Updated: glibc-2.5-49.el5_5.6.i686
Oct 22 00:41:36 Updated: nscd-2.5-49.el5_5.6.i386
Oct 22 00:41:38 Updated: glibc-headers-2.5-49.el5_5.6.i386
Oct 22 00:41:39 Updated: glibc-devel-2.5-49.el5_5.6.i386

=(

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Fri, 10/22/2010 - 18:06

Thanks, that's a bug - those packages that "failed" were actually already installed as dependencies of previous updates. I will fix this in the next release of the Virtualmin Package Updates module.

Submitted by Issues on Fri, 11/05/2010 - 20:21

Automatically closed -- issue fixed for 2 weeks with no activity.