Bug 1024224 - Satellite installer does not check whether the port it will communicate to external Oracle DB on will be allowed given the system's SELinux configuration
Satellite installer does not check whether the port it will communicate to ex...
Status: NEW
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Installer (Show other bugs)
560
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Milan Zázrivec
Red Hat Satellite QA List
:
Depends On:
Blocks: 462714
  Show dependency treegraph
 
Reported: 2013-10-29 03:28 EDT by Joe Thompson
Modified: 2015-10-08 00:49 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joe Thompson 2013-10-29 03:28:17 EDT
Description of problem: Installing Satellite with SELinux in Enforcing mode fails with a generic error if using an external Oracle database on a non-standard port that is not listed as allowed in oracle_port_t.


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


How reproducible: 100%


Steps to Reproduce:
1. Set up an external Oracle database instance on a non-standard port and configure it for Satellite use.
2. Set up a RHEL system to install Satellite on with SELinux in enforcing mode using a vanilla default SELinux "targeted" configuration.
3. Attempt to install Satellite on the system using a connection to the said database server.

Actual results: Install fails at testing the connection to the database with a generic error message.


Expected results: Installer should either warn the user before the test that the connection test will fail (based on the fact that the SELinux enforcement mode, oracle_port_t allowed port list and the external Oracle port number are all known or at least knowable at that point), or at a minimum should at least provide more informative info after the failure suggesting that as a highly likely cause.


Additional info:

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