Operating system command returns wrong value

Content Authoring
1

(imported topic written by jrbast)

On Oracle Enterprise Linux verion 6.4 the TEM commands “operating system” and name of operating system" return wrong operating system value. What is TEM looking at to get the name of the operating system?

Q: name of operating system

A: Linux Red Hat Enterprise Server 6.4

T: 4927

Q: operating system

A: Linux Red Hat Enterprise Server 6.4 (2.6.32-358.el6.x86_64)

T: 59

So as a result of this condition, our hardware inventory shows all OEL 6.x hosts as Redhat, but they are NOT

Looks to be a bug request/enhancement request. Also the Managed properties value “OS” would need to interpet the change between operating system names as well for computer subscriptions.

The Oracle Linux Server release version is in the file /etc/oracle-release

root # cat /etc/oracle-release

Oracle Linux Server release 6.4

So we need the TEM command “operating system” and version of operating system" to return the value “Oracle Linux Server release 6.4” and NOT “Linux Red Hat Enterprise Server 6.4 (2.6.32-358.el6.x86_64)”

But on a OEL 5 system

Q: operating system

A: Linux Oracle Enterprise Server release 5.7 (2.6.18-274.el5)

T: 14765

2

(imported comment written by BrianPGreen)

Which version of TEM is this happening on?

3

(imported comment written by jrbast)

8.2.1079

4

(imported comment written by cstoneba)

same here, but I just thought that the reported OS should be Redhat because under the covers, that’s what Oracle Linux is. my agent is running v8.2.1364.0

Q: name of operating system

A: Linux Red Hat Enterprise Server 6.4

T: 3600

Q: operating system

A: Linux Red Hat Enterprise Server 6.4 (2.6.32-279.11.1.el6.x86_64)

T: 47

Q: lines of file “/etc/oracle-release”

A: Oracle Linux Server release 6.4

T: 7183

Are you able to patch your OL servers with TEM and work around Dependency Resolutions? just cuirous

5

(imported comment written by jrbast)

Yes we can patch, but we need to know from a inventory standpoint which are redhat and OEL. In the current situation we loose htis capability starting with OEL 6.x hosts. We have opened a case with IBM/TEM and reported as a bug. APAR IV43122 has been submitted to correct this and will be in next release of the TEM agent