Bug 1459121 - Prompt to install monitoring on proxy when monitoring is not enabled on satellite
Prompt to install monitoring on proxy when monitoring is not enabled on satel...
Product: Red Hat Satellite Proxy 5
Classification: Red Hat
Component: Installer (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tomáš Kašpárek
Red Hat Satellite QA List
Depends On:
Blocks: sat58-nth
  Show dependency treegraph
Reported: 2017-06-06 07:00 EDT by Pavel Studeník
Modified: 2018-04-10 04:45 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-04-10 04:45:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pavel Studeník 2017-06-06 07:00:43 EDT
Description of problem:
I install satellite 5.6/5.7 with disabled monitoring. I register systems and install new proxy to satellite and during installation I am prompted to install proxy monitoring. Monitoring doesn't work on this proxy because it is not enable on satellite. I suppose that installer can be clever (check port or call API isMonitoringEnabled)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. disable monitoring on satellite 5.6/5.7
2. install proxy on new system
3. prompt to install proxy monitoring
>> Will run 'yum install spacewalk-proxy-monitoring'. [Y/n]:

Actual results:
You do not have monitoring installed.
Do you want to install monitoring scout?
Will run 'yum install spacewalk-proxy-monitoring'. [Y/n]:

Expected results:
without prompt. Installer skips installation of proxy monitoring.
Comment 4 Tomas Lestach 2018-04-10 04:45:15 EDT
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED.

Note You need to log in before you can comment on or make changes to this bug.