![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1496790.1 : Exachk Failing At Software Profile Check Complaining On Missing ipmitool-1.8.10.3-3.rhel5.x86_64.rpm
In this Document
Created from <SR 3-6112969651> Applies to:Exalogic Elastic Cloud X3-2 Eighth Rack - Version All Versions to All Versions [Release All Releases]Oracle Exalogic Elastic Cloud Software - Version 1.0.0.0.0 and later Oracle Exalogic Elastic Cloud X2-2 Half Rack - Version All Versions to All Versions [Release All Releases] Exalogic Elastic Cloud X3-2 Full Rack - Version All Versions to All Versions [Release All Releases] Exalogic Elastic Cloud X3-2 Quarter Rack - Version All Versions to All Versions [Release All Releases] Linux x86-64 SymptomsAfter running Exachk health check tool on Exalogic and reviewing the generated HTML Exachk report, in few cases we see "FAIL" status for OS check with message saying that Software profile is not configured correctly as shown in below screenshot. Clicking on "View Details" in Exachk report we can observe that Software Profile check has failed during Exachk execution because of not finding ipmitool package "ipmitool-1.8.10.3-3.rhel5.x86_64.rpm" as shown in below screenshot. CauseThis issue of Exachk Software Profile check failing is caused because of installing OPS Center12c. After installing OPS Center12c, the ipmitool-1.8.10.3-3.rhel5.x86_64.rpm which comes as default with base image is replaced by the latest version. As part of Exachk execution Software Profile check script (/opt/exalogic.tools/tools/CheckSWProfile) checks for the older version of "ipmitool-1.8.10.3-3.rhel5.x86_64.rpm" package which comes as default as part of base image. As it doesn't exists anymore, the Software Profile check fails as shown in above screenshots during Exachk execution. SolutionWe can safely ignore Software Profile Check fail message in Exachk report caused because of missing "ipmitool-1.8.10.3-3.rhel5.x86_64.rpm" package. The other option to address this issue is to install the old ipmitool package "ipmitool-1.8.10.3-3.rhel5.x86_64.rpm" along side of latest ipmi package which is installed by OPS Center12c. This way when Exachk is executed it will not fail at Software Profile check as it finds ipmi package version "ipmitool-1.8.10.3-3.rhel5.x86_64.rpm" it is checking for. References<NOTE:1463157.1> - Exalogic Exachk Diagnostic Information and Suggested Actions@ <BUG:14646128> - FALSE POSITIVE ON CHECKSWPROFILE <NOTE:1449226.1> - Exachk Health-Check Tool for Exalogic <NOTE:1329262.1> - How to Perform a Healthcheck on Exalogic <NOTE:1478378.1> - Exalogic Exachk Health-Check Tool Known Issues Attachments This solution has no attachment |
||||||||||||||||||
|