Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1151386

Summary: Osa-dispatcher doesn't run with external database
Product: Red Hat Satellite 5 Reporter: Pavel Studeník <pstudeni>
Component: InstallerAssignee: Tomas Lestach <tlestach>
Status: CLOSED NOTABUG QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: high Docs Contact:
Priority: high    
Version: 570CC: cperry, daobrien, mkollar, tkasparek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-04 13:44:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1162131    

Description Pavel Studeník 2014-10-10 09:39:18 UTC
Description of problem:
I install satellite with external postgresql and I got error in install log file

# /var/log/rhn/rhn_installation.log
Waiting for tomcat to be ready ...
Starting httpd: [  OK  ]
Starting osa-dispatcher: Spacewalk 22134 2014/10/09 16:56:26 -04:00: ('Error caught:',)
Spacewalk 22134 2014/10/09 16:56:26 -04:00: ('Traceback (most recent call last):\n  File "/usr/share/rhn/osad/jabber_lib.py", line 118, in main\n    self.setup_config(config)\n  File "/usr/share/rhn/osad/osa_dispatcher.py", line 112, in setup_config\n    rhnSQL.initDB()\n  File "/usr/lib/python2.6/site-packages/spacewalk/server/rhnSQL/__init__.py", line 148, in initDB\n    del __DB2\nNameError: global name \'__DB2\' is not defined\n',)
[  OK  ]
Starting Monitoring ...  
[ OK ]
Starting MonitoringScout ...  


And I got AVC message, too. But I don't sure that it is connected with previous problem.

time->Thu Oct  9 16:56:26 2014
type=SYSCALL msg=audit(1412888186.344:164): arch=c000003e syscall=42 success=no exit=-13 a0=4 a1=22c4ef0 a2=10 a3=7fffacd5b1c4 items=0 ppid=22133 pid=22134 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="osa-dispatcher" exe="/usr/bin/python" subj=unconfined_u:system_r:osa_dispatcher_t:s0 key=(null)
type=AVC msg=audit(1412888186.344:164): avc:  denied  { name_connect } for  pid=22134 comm="osa-dispatcher" dest=5433 scontext=unconfined_u:system_r:osa_dispatcher_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket
Fail: AVC messages found.

Version-Release number of selected component (if applicable):
spacewalk-java-2.3.8-28.el6sat.noarch
spacewalk-setup-2.3.0-1.el6sat.noarch
osa-dispatcher-5.11.44-2.el6sat.noarch
osa-dispatcher-selinux-5.11.44-2.el6sat.noarch

How reproducible:
always

Steps to Reproduce:
1. install satellite with external postgresql (on other system)

Comment 1 Matej Kollar 2014-10-22 10:00:17 UTC
I seem to be unable to reproduce this with PostgreSQL 9.2

Comment 2 Matej Kollar 2014-10-24 12:35:44 UTC
Ok. Current findings:

Combination of multiple issues

  * Small issue in initialization of database connections
    that exhibits itself when connection to database fails.
  * Selinux issue is connected to this. Interesting part is,
    that is seems this shows itself only with external database
    installed on virtual machine (hosted on the same machine
    as satellite).
  * There already exists selinux boolean allow_ypbind
    that can fix this: setsebool allow_ypbind true

Comment 3 Matej Kollar 2014-10-24 12:45:15 UTC
Upstream work

Spacewalk.git: 69268d9bca54633ae9845ecdab99bac42e9c9705

Comment 4 Matej Kollar 2014-11-18 15:59:51 UTC
Mentioned commit is moved under bug #1165252 to allow separate verification.