Upgrade to 5.3 proxy from 5.0 on rhel4 failed as well from CLI Testing package set / solving RPM inter-dependencies... There was a package dependency problem. The message was: Unresolvable chain of dependencies: rhn-apache 1.3.27-36.rhn.rhel4 conflicts with httpd rhn-modpython 2.7.11-1.rhel4 conflicts with mod_python rhn-modssl 2.8.12-8.rhn.10.rhel4 conflicts with mod_ssl rhns-auth-daemon-5.0.2-3.rhel4 requires rhns-proxy-broker >= 3.6.0 The following packages were added to your selection to satisfy dependencies: Package Required by ---------------------------------------------------------------------------- Installation of package spacewalk-proxy-management failed. Installation interrupted. API version: 5.3.0 RHN Proxy successfully deactivated.
I added Obsoletes/Provides so this packages are removed during install/upgrade. If monitoring enabled then these deps appeared too: Unresolvable chain of dependencies: Time-System 1.6.0-3.rhel4 requires np-config rhn-modperl 1.29-16.rhel4 conflicts with mod_perl I fixed these too. Only one problem was that if rhn-apache was present, then when upgraded to httpd, the rpm logic created rpmnew file. So apache failed to start after proxy restart. I detect such case and remove (move to backup) that httpd.conf just before upgrade of apache. Commit: f615f8bd43445d045a33f810c0c909db09cc47cf
getting the same exact error. I can only assume the correct packages have not been pushed. I have fully re-synced rhel4-as, tools and the proxy channel. Can some one comment on the upgraded packages I should be looking for. Thanks Package rhn-apache present - assuming upgrade: Force removal of /etc/httpd/conf/httpd.conf - backed up to /etc/httpd/conf/httpd.conf.rpmsave mv: cannot stat `/etc/httpd/conf/httpd.conf': No such file or directory Fetching Obsoletes list for channel: rhel-i386-as-4... ######################################## Fetching Obsoletes list for channel: redhat-rhn-proxy-5.3-as-i386-4... Fetching Obsoletes list for channel: rhn-tools-rhel-4-as-i386... Fetching rpm headers... ######################################## Name Version Rel Arch ---------------------------------------------------------------------------------------- spacewalk-proxy-management 0.5.7 8.el4sat noarch Testing package set / solving RPM inter-dependencies... There was a package dependency problem. The message was: Unresolvable chain of dependencies: rhn-apache 1.3.27-36.rhn.rhel4 conflicts with httpd rhn-modpython 2.7.11-1.rhel4 conflicts with mod_python rhn-modssl 2.8.12-8.rhn.10.rhel4 conflicts with mod_ssl rhns-auth-daemon-5.0.2-3.rhel4 requires rhns-proxy-broker >= 3.6.0 The following packages were added to your selection to satisfy dependencies: Package Required by ---------------------------------------------------------------------------- Installation of package spacewalk-proxy-management failed. Installation interrupted. API version: 5.3.0 RHN Proxy successfully deactivated. [root@dhcp77-160 ~]#
It should be fixed in spacewalk-proxy-monitoring-0.4.4-4-sat spacewalk-proxy-installer-0.5.25-18-sat spacewalk-proxy-0.5.7-9-sat Yeah on stage are old packages.
Denis please flip it to ON_QA once you push those packages to stage.
hmm. they should be on webqa. Wes did you test it from webqa content or stage content?
moving back to on_qa packages have landed.. upgrade from rhel4 proxy 500 -> rhel4 proxy 530(cmd line) works, monitoring packages were installed when they should *not* have been.
test includes: install old proxy, register a system to the proxy install a package, verify it hits the access.log on proxy upgrade old proxy install a package, verify it hits teh access.log on upgraded proxy rhel4 proxy 40 -> 530 proxy pass rhel5 proxy 52 -> 530 proxy pass
Can you elaborate on "monitoring packages were installed when they should *not* have been." ...
Ahh, I see. Reported as BZ 518064.
Verified scenario in comment# 11 for rhel5 proxy 52 -> 530 proxy. Moving to 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-1235.html