From Bugzilla Helper: User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2 i686) After upgrading from a Wolverine install to Seawolf, whenever I try to use up2date I get: ERROR: Invalid Architecture and OS release combination INFO: N/A Reproducible: Always Steps to Reproduce: 1. On a wolverine install run up2date on all packages. 2. Using the install discs, upgrage to RH7.1 (Seawolf) 3. Rebuild the RPM database (rpm --rebuilddb) 4. Run rhn_register and register new install. 5. Run up2date. Actual Results: No update occurs and I get message: ERROR: Invalid Architecture and OS release combination INFO: N/A Expected Results: Either packages should have updated or I should have been told the machine is already fully updated. Packages installed at time of failure: up2date-gnome-2.5.2-1 up2date-2.5.2-1 rhn_register-gnome-1.3.1-1 rhn_register-1.3.1-1
I would check and make sure that both rhn_register and up2date are talking to live servers. So, run 'rhn_register --config' and make sure that serverURL is set to 'https://www.rhns.redhat.com/XMLRPC' and run 'up2date --config --nox' and make sure that serverURL is set to 'https://www.rhns.redhat.com/XMLRPC' Several of the betas went out with configs pointing to beta-tester machines and the such, and if you are still talking to those, they will give you that error, as they know nothing of 7.1.
rhn_register was finding the correct server, but up2date was still looking at the beta server. I changed the servers (http and https) and it works now. How is it that rhn_register knew what server to look for and up2date did not? Should the installer look for this situation and fix this automatically when upgrading from a beta to a release version?