RHEL patches installed but sub-action reports failed

Usage and Config Patch
1

(imported topic written by SMcQueen)

Ok,

So I’m performing a baseline update with about 10 items in it to a client and the report back states that it “Failed”

When I review the Action log is says that some items were “Successful”, some were “Not Relevant”, and one reported as “Failed”

So I checked the the client log

Relevant - RHSA-2012:0324 - Libxml2 Security Update - Red Hat Enterprise 5.0 (x86_64) (fixlet:2919) ItemizedDownloadsAvailable: 

true (action id 2919) ActionLogMessage: (action 2919) Non-Distributed - DownloadsAvailable ActionLogMessage: (action 2919) Submitting download request ActionLogMessage: (action 2919) Download url: 
'http://software.bigfix.com/download/bes/dep/rhel/edr/RedHatEDRPlugin-x64-0.15' ActionLogMessage: (action 2919) Download url: 
'http://software.bigfix.com/download/bes/dep/pkgdeps/pkgdeps-x64-RHEL-2.0.17' ActionLogMessage: (action 2919) Download url: 
'http://software.bigfix.com/download/bes/dep/rhel/depgraphs/DEP_RHEL5_x64_Server/DEP_RHEL5_x64_Server.xml.20120323-2000.bz2' ItemizedDownloadsAvailable: 

true (action id 2919) ActionLogMessage: (action 2919) Non-Distributed - DownloadsAvailable ActionLogMessage: (action 2919) Submitting download request ActionLogMessage: (action 2919) Download url: 
'http://software.bigfix.com/download/bes/dep/rhel/edr/RedHatEDRPlugin-x64-0.15' ActionLogMessage: (action 2919) Download url: 
'http://software.bigfix.com/download/bes/dep/pkgdeps/pkgdeps-x64-RHEL-2.0.17' ActionLogMessage: (action 2919) Download url: 
'http://software.bigfix.com/download/bes/dep/rhel/depgraphs/DEP_RHEL5_x64_Server/DEP_RHEL5_x64_Server.xml.20120323-2000.bz2' ActionLogMessage: (action 2919) Download url: 
'RedHatProtocol://libxml2-python-2.6.26-2.1.15.el5_8.2.x86_64.rpm' ActionLogMessage: (action 2919) Download url: 
'RedHatProtocol://libxml2-2.6.26-2.1.15.el5_8.2.x86_64.rpm' ActionLogMessage: (action 2919) starting sub action Command succeeded parameter 
"depOS" = 
"DEP_RHEL5_x64_Server" (fixlet 2919) Command succeeded parameter 
"sitefolder" = 
"/var/opt/BESClient/__BESData/Patches for RHEL5 Dependency Resolution" (fixlet 2919) Command succeeded parameter 
"t0" = 
"" (fixlet 2919) Command succeeded parameter 
"t1" = 
"libxml2-2.6.26-2.1.15.el5_8.2.x86_64" (fixlet 2919) Command succeeded parameter 
"t2" = 
"" (fixlet 2919) Command succeeded parameter 
"t3" = 
"" (fixlet 2919) Command succeeded parameter 
"t4" = 
"libxml2-python-2.6.26-2.1.15.el5_8.2.x86_64" (fixlet 2919) Command succeeded parameter 
"args" = 
" libxml2-2.6.26-2.1.15.el5_8.2.x86_64   libxml2-python-2.6.26-2.1.15.el5_8.2.x86_64" (fixlet 2919) Command succeeded parameter 
"depfile" = 
"DEP_RHEL5_x64_Server.xml.bz2" (fixlet 2919) Command started - wait sh 
"/var/opt/BESClient/__BESData/Patches for RHEL5 Dependency Resolution/InstallPackages.sh" -f 2919 -c 
"rpm -U" -e 
"/var/opt/BESClient/__BESData/actionsite" -p 
"/var/opt/BESClient/__BESData/actionsite/__Download" -l 
"/var/opt/BESClient/__BESData/actionsite/../../EDRDeployData" libxml2-python-2.6.26-2.1.15.el5_8.2.x86_64.rpm libxml2-2.6.26-2.1.15.el5_8.2.x86_64.rpm (fixlet 2919) Command succeeded (Exit Code=0) wait sh 
"/var/opt/BESClient/__BESData/Patches for RHEL5 Dependency Resolution/InstallPackages.sh" -f 2919 -c 
"rpm -U" -e 
"/var/opt/BESClient/__BESData/actionsite" -p 
"/var/opt/BESClient/__BESData/actionsite/__Download" -l 
"/var/opt/BESClient/__BESData/actionsite/../../EDRDeployData" libxml2-python-2.6.26-2.1.15.el5_8.2.x86_64.rpm libxml2-2.6.26-2.1.15.el5_8.2.x86_64.rpm (fixlet 2919) ActionLogMessage: (action 2919) ending sub action

I have also confirmed that the proper version is installed via RPM

rpm -qa | grep libxml libxml2-2.6.26-2.1.15.el5_8.2 libxml2-python-2.6.26-2.1.15.el5_8.2

So, what am I missing? Why does it say failed?

TIA

2

(imported comment written by SystemAdmin)

One thing we noticed with Red Hat patching is that sometimes, things come back as “Failed” even though everything is patched properly. We do not know why this happens, but a temporarily solution is to clear the console cache and restart the console; the “Failed” Fixlet should now report back as “Fixed” or “Not Relevant”.

3

(imported comment written by SMcQueen)

Tried the Cache trick, no dice… Thanks for the suggestion.

I did pull the relevance statements out and ran it through the qna tools and it does comeback reporting false and the local log does report it coming back as “not relevant”

4

(imported comment written by SystemAdmin)

Is the Fixlet still relevant?

5

(imported comment written by SMcQueen)

Yes, It never seems to reset the relevance for the fixlet. however when I try the actual relevance statements using the QnA tool it should not be relevant.

6

(imported comment written by Neto_Partner-IT)

Hello,

I’m also having the same problem, any suggestions?

Thank’s

Fernando E.