This change in Proxy 5.2 installer need to be done in hosted too (see svn revision on the bottom): +++ This bug was initially created as a clone of Bug #450299 +++ Description of problem: When you have some conflicting packages on machine RHEL5, the installer will fail, becouse of unresolvable dependencies. Version-Release number of selected component (if applicable): 520 Steps to Reproduce: 1. install proxy on rhel5 2. deactivate (do not remove packages) 3. install again using webui Actual results: error: Failed dependencies: httpd is needed by (installed) rhns-proxy-html-5.2.0-5.el5.noarch libidn.so.11 is needed by (installed) jwhois-3.2.3-8.el5.i386 libidn.so.11 is needed by (installed) curl-7.15.5-2.el5.i386 libidn.so.11 is needed by (installed) gnupg-1.4.5-12.i386 perl(Apache2::Const) is needed by (installed) perl-Frontier-RPC-0.07-7.noarch perl(Apache2::ServerUtil) is needed by (installed) perl-Frontier-RPC-0.07-7.noarch mod_python is needed by (installed) rhns-proxy-common-5.2.0-4.el5.noarch mod_ssl is needed by (installed) rhns-proxy-common-5.2.0-4.el5.noarch rhns-proxy-broker >= 5.2.0 is needed by (installed) rhns-proxy-common-5.2.0-4.el5.noarch Expected results: no error -- Additional comment from msuchy on 2008-06-06 11:13 EST -- commited to trunk rev. 173634
So the change set from satellite does not apply (via patch, not conceptually) at all to hosted. The installer XML file in our code base doesn't have any of the checks for conflicting packages. Am I missing something?
Yes, we are missing fix of this bug: 424901. I swear I think you already copy this commits, but apparently not.
Okay, so the long and the short of this is that this bug is untestable right now. This is dependent on Proxy 5.2, which has not yet reached GA. Without having the proxy 5.2 rpms in our environment (which we don't) it's impossible to test. Furthermore, the bug this was cloned from is still only modified; so the patch that jbowes applied has not yet been tested by the satellite team. The combination of those two factors make me very uneasy about releasing this patch. We can discuss this at our next meeting, but we should consider what options we have.
The satellite part (BZ 235504, 235506) are verified and furthermore verified in stage. Proxy 5.2 are available in webqa. Yeah it is not available on stage.
To get around the "RPM not signed" error: edit /etc/yum/pluginconf.d/rhnplugin.conf; set gpgcheck = 0 Note: at this time the associated tools in rhn-tools have *not* been pushed into webqa. Install from BREW instead: http://porkchop.devel.redhat.com/brewroot/packages/rhns-certs-tools/5.2.0/3.el5/noarch/rhns-certs-tools-5.2.0-3.el5.noarch.rpm
Miroslav, I have not been able to recreate this bug in webqa. The proxy installer seems to know that the packages have already been installed and it does not schedule that step. Can you provide more guidance on how to re-create this? Thanks.
I'm not sure, I just followed Steps to Reproduce and I got the given error. Which step do you mean by "that step"?
By "that step" I mean the Event that installs the proxy packages. When I try to reactivate the proxy the installer recognizes (I assume) that the machine already has the packages installed and does not schedule that event. As a result, I do not get the conflicting packages error and the proxy reactivates successfully. And you say you can reproduce this error in RHN Hosted in webqa? Strange...
you can not reproduce this bug on webqa since on webqa is evidently not presented patch from BZ 424901, and this bug appear only if you have this feature.
verified in webdev As msuchy notes it's not possible to test this in an environment where 424901 has not been applied, and the fix that that bug was added to webdev at the same time as this one was. So I have not been able to reproduce the bug, but at least we know that the process is working properly with this fix in place.
verified in qa