Bug 490726
| Summary: | rhn-org-httpd-ssl-key cert and jabberd cert conflict at install time | ||
|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | wes hayutin <whayutin> |
| Component: | Installation | Assignee: | Miroslav Suchý <msuchy> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 0.5 | CC: | cperry, msuchy, nathanr, sgeschke, tlestach |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | na | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-08 08:41:29 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: | 653453 | ||
Hi I have exactly the same problem on RHEL 5.3/latest updates. Is there a workaround? (In reply to comment #1) > I have exactly the same problem on RHEL 5.3/latest updates. > Is there a workaround? I worked around it by excluding jabberd from the update: # yum update -x jabberd Not ideal, and it does mean my auto-updates don't work (I need to manually run the above command), but at least I can get my updates for my spacewalk server. (In reply to comment #1) > I have exactly the same problem on RHEL 5.3/latest updates. > Is there a workaround? Oh, I also added to the [main] section of /etc/yum.conf: exclude=jabberd Which will stop the autoupdate trying to update jabberd. This makes yum-updatesd continue running, but the Spacewalk webapp still reports the machine as having 1 outstanding update. Combined with my previous comment, that should work around the bug ok. Cool, I'll try that! :) Thanks a lot. Mass-moving to space13. Conflict removed ... # rpm -qpl ./ssl-build/hp-dx2200-01.rhts.eng.bos/rhn-org-httpd-ssl-key-pair-hp-dx2200-01.rhts.eng.bos-1.0-2.noarch.rpm | grep server.pem /etc/pki/spacewalk/jabberd/server.pem # rpm -ql jabberd | grep server.pem /etc/jabberd/server.pem Moving ON_QA ... This bug has been fixed in Spacewalk 1.3. |
Description of problem: latest spacewalk install epel-test mirsolav's space05 repo on rhel 5_u3 /root/ssl-build/dhcp231-158.rdu/rhn-org-httpd-ssl-key-pair-dhcp231-158.rdu-1.0-1.noarch.rpm The most current RHN Proxy Server installation process against RHN hosted requires the upload of an SSL tar archive that contains the CA SSL public certificate and the web server's key set. Generating the web server's SSL key set and CA SSL public certificate archive: /root/ssl-build/dhcp231-158.rdu/rhn-org-httpd-ssl-archive-dhcp231-158.rdu-1.0-1.tar Deploy the server's SSL key pair/set RPM: (NOTE: the RHN Satellite or Proxy installers may do this step for you.) The "noarch" RPM needs to be deployed to the machine working as a web server, or RHN Satellite, or RHN Proxy. Presumably 'dhcp231-158.rdu.redhat.com'. Preparing packages for installation... file /etc/jabberd/server.pem from install of rhn-org-httpd-ssl-key-pair-dhcp231-158.rdu-1.0-1.noarch conflicts with file from package jabberd-2.2.5-1.el5.i386 Could not install /root/ssl-build/dhcp231-158.rdu/rhn-org-httpd-ssl-key-pair-dhcp231-158.rdu-1.0-1.noarch.rpm at /usr/bin/rhn-install-ssl-cert.pl line 69. (END) dgilmore weshay_other: jabberd added recently its own cert dgilmore we should install our cert elsewhere weshay_other ah.. gotcha weshay_other thanks for explaining.. I'll look into that dgilmore weshay_other: we should probably put it in /etc/pki/spacewalk/jabberd