Red Hat Bugzilla – Bug 501918
RFE - RHN Satellite probes assigned to registered clients
Last modified: 2015-05-29 16:11:46 EDT
Description of problem:
Every single created "RHN Satellite" probe is assigned to a registered client. But RHN Satellite probes get executed locally on the satellite itself, not on the registered clients. Actually they have nothing in common with registered clients.
Version-Release number of selected component (if applicable):
sat5.3, but I suppose, the problem lasts since RHN Satellite probes were introduced
Steps to Reproduce:
1. register a client to the satellite, enable monitoring
2. create any RHN Satellite probe (f.e. RHN Satellite: Process Counts), push scout
3. check the result of the probe
4. check number of processes manually on the satellite and on the client
5. compare 3)^ and 4)^
6. check the probe details and make sure, it's assigned to the registered client
The "RHN Satellite: Process Counts" probe returns number of processes on the satellite itself. All the RHN Satellite probes are executed on the satellite and not on the registered clients. And that is correct! But why are all the "RHN Satellite" probes assigned to any of the registered clients?
"RHN Satellite" probes are assigned to the local satellite itself.
Note, that if you have no client registered to the satellite at all, you're unable to create any RHN Satellite probe.
Hi Tomas, you are correct, your observations. This has always been like this for 'Satellite probes'. I do not want to address this within 530 cycles and moving this to triage for possible future inclusion in either 5.4 or 6.0 Sat.