Bug 509450
| Summary: | OSAD not connecting through RHN Proxy in x86_64 | ||
|---|---|---|---|
| Product: | Red Hat Satellite Proxy 5 | Reporter: | John Matthews <jmatthew> |
| Component: | Server | Assignee: | Miroslav Suchý <msuchy> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Lestach <tlestach> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 530 | CC: | bperkins, cperry, jpazdziora, mzazrivec, tlestach, whayutin |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | sat530 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-09-10 14:39:23 UTC | Type: | --- |
| 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: | 456999 | ||
|
Description
John Matthews
2009-07-02 20:26:01 UTC
[16:51] <msuchy> jmatthews: I think that the second scenario is not a bug. but I dunno how it is supposed to work :( [16:52] <jmatthews> msuchy, don't worry about 2nd scenario, it was just exploration and more info, I wasn't sure if it would be I'm reducing this bug to first scenario only. This bug happens on on our sputnik-stage too - that is 5.2 satellite. Therefore it is not regression. It happens even with jabberd-2.0s10-3.42.el5.x86_64.rpm from sat520 Adelton noticed that those 64bit proxy do not have jabber cert:
[root@xen68 jabberd]# grep pemfile c2s.xml
<pemfile>/etc/jabberd/server.pem</pemfile>
<pemfile>/etc/jabberd/server.pem</pemfile>
[root@xen68 jabberd]# ls -l /etc/jabberd/server.pem
ls: /etc/jabberd/server.pem: No such file or directory
I have this file on 32 bit proxy.
On 64bits however exist:
/etc/pki/spacewalk/jabberd/server.pem
It looked sane so I tried to copy it to /etc/jabberd/server.pem, but it doesnot help.
If I removed /etc/jabberd/server.pem on those 32bit proxy and restarted jabberd on proxy and osad on client I got that familiar output:
Starting osad: Server does not support TLS - <starttls /> not in <features /> stanza
I will try to find why the file is missing there.
Got it. The problem is not in architecture. WebUI correctly generate /etc/jabberd/server.pem, but command line installer not. Therefore if you run on i386 installed from webUI and even later upgraded using CLI - it runs. But if you install for the first time using CLI, jabberd ssl will not work. Hmm, situation is as follows:
i386 - webui - ok
x86_64 - webui - ok
i386 - cli - fail
- when run cp cp /etc/pki/spacewalk/jabberd/server.pem /etc/jabberd/server.pem - it works
x86_64 - cli - fail
- when I copy server.pem on propper place, fail too :(
Fixed by commit: ed7ca1abd6520909519d7a0b17a0081babc1f274 It works even on x86_64 and I tested update of jabberd from one 2.2.x to another 2.2.x and it works too. iso 20090714 moving ON_QA Following scenario#1 according to #Description. (According to Comment#11, the problem is not arch depended, but cli/webui installer depended, so testinf i386 proxy) ****************************************************************************************** * when using spacewalk-proxy-installer-0.5.25-15.el5sat: on client: # service osad restart Shutting down osad: [ OK ] Starting osad: Server does not support TLS - <starttls /> not in <features /> stanza [ OK ] [problem reproduced] ****************************************************************************************** * when using spacewalk-proxy-installer-0.5.25-16.el5sat: on client: # service osad restart Shutting down osad: [ OK ] Starting osad: [ OK ] on WEBUI: ----------------------------------------------------- OSA Status: online as of 7/20/09 9:58:43 AM EDT Last pinged: 7/20/09 9:58:44 AM EDT Ping System ----------------------------------------------------- [problem didn't show up] ****************************************************************************************** Verified with Satellite-5.3.0-RHEL5-re20090714.0! Verified in stage -> RELEASE_PENDING An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1433.html |