On a fresh install of Wolverine, I'm also getting the infamous "Invalid Architecture and OS release combination" error. As far as I can tell, everything is accurate: [root@localhost /root]# cat /etc/redhat-release Red Hat Linux release 7.0.91 (Wolverine) [root@localhost /root]# [root@localhost /root]# cat /etc/sysconfig/rhn/systemid <?xml version="1.0"?> <params> <param> <value><struct> <member> <name>type</name> <value><string>ANONYMOUS</string></value> </member> <member> <name>checksum</name> <value><string>e46a14c411d9074a0ce559f5d087d0ef</string></value> </member> <member> <name>description</name> <value><string>Anonymous SERVER running 7.0.91 on a i686</string></value> </member> <member> <name>os_release</name> <value><string>7.0.91</string></value> </member> <member> <name>architecture</name> <value><string>i686</string></value> </member> <member> <name>system_id</name> <value><string>ANONYMOUS-SERVER</string></value> </member> <member> <name>operating_system</name> <value><string>Red Hat Linux</string></value> </member> <member> <name>profile_name</name> <value><string>A beta Anon Server</string></value> </member> <member> <name>fields</name> <value><array><data> <value><string>system_id</string></value> <value><string>os_release</string></value> <value><string>operating_system</string></value> <value><string>architecture</string></value> <value><string>profile_name</string></value> <value><string>username</string></value> <value><string>type</string></value> </data></array></value> </member> <member> <name>username</name> <value><string>anonymous</string></value> </member> </struct></value> </param> </params> [root@localhost /root]#
We do not have the packages for the beta on the up2date servers, so you really are presenting yourself with an invalid release, hence the error. Once we release the next release, then those packages will be uploaded to the up2date servers and you will be able to run up2date.
yes, this is a bug in the client code. It reads the wrong config file, and points at the wrong server, and returns the "invalid OS and arch combo" cp /etc/sysconfig/rhn/up2date /etc/sysconfig/rhn/rhn up2date -r up2date Been fixed internally for a while. If you could send me a copy of your /etc/sysconfig/rhn/up2date and /etc/sysconfig/rhn/rhn files, I'd like to take a look and verify this is indeed the same issue.
Created attachment 12904 [details] up2date
I just attached the up2date from this system. I don't even have an /etc/sysconfig/rhn/rhn file though. It's running qa0309 now + up2date*2.4.4-1
After following your suggestion and copying up2date to rhn and re-doing up2date -r, I still get "Invalid server or OS combination." Is this a bug, or is up2date just not supposed to work on qa0309?