Red Hat Bugzilla – Bug 535452
be able to disable the yum server in the platform plugin but still do rpm discovery
Last modified: 2014-11-09 17:49:26 EST
svn rev4074,4076,4077 are all related.. had to fix some itty-bitty things while testing
How do I test this? The yum server appears disabled by default. What is 'rpm discovery'?
"rpm discovery" is when the linux platform plugin scans what software is installed on the box (it does this by asking yum for a list of installed packages). If this rpm discovery is enabled, after a few minutes of starting up a new agent, you will see your platform's Content tab show all the software that is installed on the box.
I've separated this feature from the ability to perform yum updates through Jopr and our content source plugins. Now, you can do rpm discovery even if you don't want the linux plugin starting up an internal yum server (which is required to support yum updates).
There are two plugin configuration properties in the linux platform resources that are relevent here, they are in the "Content" configuration group. Go to inventory>connection subtab and see these (this is from the descriptor .xml):
<c:description>Settings to support content/package functionality</c:description>
description="If true, attempts will be made to discover installed packages on this platform">
description="If true, an internal yum server will be started in order to process yum content requests made on the local machine.">
If you set enableContentDiscovery=true and enableInternalYumServer=false, you will see be able to perform rpm discovery but you will not have a internal yum server running in the agent (you can test that you aren't by "netstat" and looking for something running on the "yumPort" (yumPort is another property in this Content group of plugin configuration - you will see it on this same UI page).
If you set enableInternalYumServer=true and enableContentDiscovery=false, the opposite will occur. netstat will show you something listening on the yumPort but you will not perform rpm discovery.
The two properties are in the connection props page. Enabling the Content Discovery doesn't do anything though, i suspect because this is a jopr build and it doesn't have the right plugins. Opened separate jopr jira JOPR-345 to cover that. rev4650
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2146