Bug 647096 - do not offer installation of spacewalk-proxy-monitoring if monitoring disabled
Summary: do not offer installation of spacewalk-proxy-monitoring if monitoring disabled
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite Proxy 5
Classification: Red Hat
Component: Installer
Version: 540
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On: 647099
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2010-10-27 08:07 UTC by Tomas Lestach
Modified: 2014-07-04 13:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-04 13:28:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Lestach 2010-10-27 08:07:06 UTC
Description of problem:
If monitoring is disabled on the satellite, proxy shall not offer (as default option/at all?) installation of spacewalk-proxy-monitoring

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

How reproducible:
always

Steps to Reproduce:
1. have a satellite with disabled monitoring
2. take client and try to configure it as proxy
  
Actual results:
- default option was to install spacewalk-proxy-monitoring ... 
- then at the end of the installation, when proxy services get restarted, there's an ugly NPBootstrap restart output (in additional info)
- obsoleted WebUI proxy installer didn't offer monitoring on proxy at all in these case

Expected results:
when monitoring isn't enabled on satellite, proxy installer shall not offer installation of spacewalk-proxy-monitoring as default option/at all (up to devel)

Additional info:
Starting MonitoringScout ...  
 Starting InstallSoftwareConfig ...  [ OK ]
 Starting NPBootstrap ...  2010-10-26 18:35:49 NPBootstrap:  !! ERROR FROM
SHELL COMMAND: 
2010-10-26 18:35:49 NPBootstrap:  !! STDOUT: <?xml version="1.0"?>
<sat_config id="512d506fcb75" version="1.1">
<step name="requestConfigData">
<status>fatalError</status>
<message>Request for configuration data from URL
'https://smqe-sat02.lab.eng.brq.redhat.com/satconfig/cgi-bin/configdata.cgi?satcluster=512d506fcb75'
failed: 
500 Server closed connection without sending any data back</message>
</step>
<status>error</status>
</sat_config>

2010-10-26 18:35:49 NPBootstrap:  !! STDERR: 
2010-10-26 18:35:49 NPBootstrap:  !! EXIT: 512
[ FAIL ]
2010-10-26 18:35:49 NPBootstrap: WARNING: STARTED BUT *NOT* RUNNING
2010-10-26 18:35:49 NPBootstrap: ERRORS ENCOUNTERED DURING LAST ACTION:
2010-10-26 18:35:49 NPBootstrap:  !! ERROR FROM SHELL COMMAND: 
2010-10-26 18:35:49 NPBootstrap:  !! STDOUT: <?xml version="1.0"?>
<sat_config id="512d506fcb75" version="1.1">
<step name="requestConfigData">
<status>fatalError</status>
<message>Request for configuration data from URL
'https://smqe-sat02.lab.eng.brq.redhat.com/satconfig/cgi-bin/configdata.cgi?satcluster=512d506fcb75'
failed: 
500 Server closed connection without sending any data back</message>
</step>
<status>error</status>
</sat_config>

2010-10-26 18:35:49 NPBootstrap:  !! STDERR: 
2010-10-26 18:35:49 NPBootstrap:  !! EXIT: 512
 Starting SputLite ...  [ OK ]
 Starting Dequeuer ...  [ OK ]
 Starting Dispatcher ...  [ OK ]
[ OK ]


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