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

Bug 1458851

Summary: OSAD service will NOT start, missing i18n module
Product: [Community] Spacewalk Reporter: Chris <zilla62>
Component: InstallationAssignee: Michael Mráka <mmraka>
Status: CLOSED EOL QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.6CC: angystardust, bishop, jdostal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-21 13:26:13 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:

Description Chris 2017-06-05 15:59:50 UTC 
Description of problem:
I installed OSAD on my Spacewalk client that I've successfully registered to my Spacewalk server.

# yum info osad
Loaded plugins: fastestmirror, rhnplugin
This system is receiving updates from RHN Classic or Red Hat Satellite.
Loading mirror speeds from cached hostfile
Installed Packages
Name        : osad
Arch        : noarch
Version     : 5.11.74
Release     : 1.el7
Size        : 95 k
Repo        : installed
From repo   : spacewalk-repo-client-2.6
Summary     : Open Source Architecture Daemon
URL         : https://fedorahosted.org/spacewalk
License     : GPLv2
Description : OSAD agent receives commands over jabber protocol from Spacewalk
            : Server and commands are instantly executed.
            : 
            : This package effectively replaces the behavior of rhnsd/rhn_check
            : that only poll the Spacewalk Server from time to time.


Now when I try to start OSAD, I get

# systemctl start osad
Job for osad.service failed because the control process exited with error code. See "systemctl status osad.service" and "journalctl -xe" for details.

...and...

# systemctl status osad -l
● osad.service - OSAD daemon
   Loaded: loaded (/usr/lib/systemd/system/osad.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2017-06-05 15:46:26 UTC; 2min 17s ago
  Process: 13511 ExecStart=/usr/sbin/osad --pid-file /var/run/osad.pid (code=exited, status=1/FAILURE)

Jun 05 15:46:26 ip-10-22-2-27.ec2.internal systemd[1]: Starting OSAD daemon...
Jun 05 15:46:26 ip-10-22-2-27.ec2.internal osad[13511]: Unable to load module osad
Jun 05 15:46:26 ip-10-22-2-27.ec2.internal osad[13511]: No module named i18n
Jun 05 15:46:26 ip-10-22-2-27.ec2.internal systemd[1]: osad.service: control process exited, code=exited status=1
Jun 05 15:46:26 ip-10-22-2-27.ec2.internal systemd[1]: Failed to start OSAD daemon.
Jun 05 15:46:26 ip-10-22-2-27.ec2.internal systemd[1]: Unit osad.service entered failed state.
Jun 05 15:46:26 ip-10-22-2-27.ec2.internal systemd[1]: osad.service failed.


Version-Release number of selected component (if applicable):
OSAD v5.11.74

How reproducible:
100%

Steps to Reproduce:
1. Set up client and register to Spacewalk server
2. Disable ALL repos in /etc/yum.repos.d, e.g., set enabled=0
3. Install OSAD, i.e., yum install -y osad
4. Start OSAD

Actual results:
OSAD will NOT start b/c of missing i18n module

Expected results:
OSAD service is started

Additional info:
Note if I install rhnlib, which installs the i18n module, the Spacewalk registration gets corrupted, and now I can't see my Spacewalk repos anymore, that is, yum repolist returns 0 mirrors.
Comment 1 Chris 2017-06-05 16:00:32 UTC 
I just wanted to add CentOS version

# cat /etc/centos-release
CentOS Linux release 7.2.1511 (Core)
Comment 2 Jiří Dostál 2017-06-08 12:00:29 UTC 
Chris,

could you please mention from where did you get jabberpy package? Jabberpy is required by OSAD package, and is placed in the EPEL repository. You wrote to disable ALL repos, so that jabberpy is unavailable.
Comment 3 Bishop Clark 2017-11-23 23:01:50 UTC 
Jiri,

Make sure jabberpy is still in EPEL, too, after Bug 1314452 is resolved.
Comment 4 Angelo Lisco 2018-02-08 19:57:12 UTC 
Same issue on here but upgrading the rhn-client-tools package from spacewalk-clients repository fixed the problem.
Comment 5 Michael Mráka 2019-10-21 13:26:13 UTC 
Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.