iirc it looks in /etc/issue.net for oracle. was this server oel and you turned it into rhel or you rebuilt it as rhel ?
It was built as RHEL and issue.net has below entries
Red Hat Enterprise Linux Server release 6.10 (Santiago)
Kernel \r on an \m
The issue is fixed now.
rpm -qa was not working on the affected target server. Fixing that issue has populated the proper OS properties for the server
Not sure how this could have affected.
i'd have to dig around a bit but we check a few different things to figure out what distro it is. i think we run a rpm -q for 'enterprise-release' or 'redhat-release' and check some other files like /etc/issue.net, /etc/redhat-release, etc. so it's possible if rpm wasn't working that check failed and one of the others passed for oel since oel is a clone of rhel and still has a lot of bits that make it look like rhel.
On some debian/Ubuntu boxes /etc/issue and /etc/debian_version are kept blank due to security reason. To get the vendor and release of those machine, the alternative method is used where lsb_release command is executed to get necessary OS information.
Correct. I was checking lsb_release –d, uname, etc. commands. But, it turned out to be rpm –q issue. After fixing the rpm db issue on the server, it was fixed.